On Thu, Jul 10, 2014 at 12:29 AM, Jeff <predato...@gmail.com> wrote:
> Thanks...that's what I am trying to do. I have successfully copied the
> artifacts. Now I need to SCP them to the server BEFORE I run a remote SSH
> script to install them.
>
> Using the SCP plugin would help me not have to manually manage credentials
> in the job or risk exposing them in the logs (am going to investigate other
> ways per Daniel's comment) but the SCP plugin step is currently only
> available in a post-build action so I am unable to use it to copy the files
> before attempting to install them.
>
> I could (and may still) write a local SSH script that simply calls SCP but
> I'm unsure how to manage credentials securely and still use them in scripts
> (again, still investigating).
Not sure I understand the point of copying things twice if the jenkins
node doesn't actually do anything to the files. Can't your target
server script just grab the archived artifacts directly from the
jenkins web interface itself? In any case, if the point is just to
run some arbitrary stuff via ssh from a node with strategic firewall
access, why not use the ssh-agent plugin and do whatever you need in
one or more build scripts that can be embedded in the job or pulled
from an scm? A side benefit is that you can use rsync over ssh
instead of scp which can sometimes be helpful.
--
Les Mikesell
lesmikes...@gmail.com
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
