On Thu, Jul 10, 2014 at 12:29 AM, Jeff 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 credenti
> I wouldn't call it "misusing". I'm simply working with what is there (that I
> knew about).
... for a problem 'what is there' was not designed to solve. Law of the
instrument ;-)
> Since I can't do SSH in post-build I am limited to what I can do, hence my
> frustration. With the emergence
jenkinsci-users@googlegroups.com
>>
>> [mailto:jenkinsci-users@googlegroups.com
>> ] *On
>> Behalf Of *Jeff
>> *Sent:* Thursday, July 10, 2014 10:09 AM
>> *To:* jenkinsci-users@googlegroups.com
>>
>> *Subject:* Re: Frustration with build-step/post-bui
glegroups.com [mailto:
> jenkinsci-users@googlegroups.com] *On Behalf Of *Jeff
> *Sent:* Thursday, July 10, 2014 10:09 AM
> *To:* jenkinsci-users@googlegroups.com
> *Subject:* Re: Frustration with build-step/post-build-action access...
>
>
>
> I wouldn't call it "
.
Regards,
Baskar.V
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jeff
Sent: Thursday, July 10, 2014 10:09 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: Frustration with build-step/post-build-action access...
I wouldn't call it "misus
I wouldn't call it "misusing". I'm simply working with what is there (that
I knew about). Since I can't do SSH in post-build I am limited to what I
can do, hence my frustration. With the emergence of Continuous
Delivery/Deployment, I wish a job could be defined more broadly and tasks
or steps wi
Your problem is that you're misusing the 'software build' concept and job type
for something that isn't strictly a software build, and its limitations become
obvious.
Post-build steps usually fall into one of the categories 'recorder' (e.g.
archive artifacts) and 'notifier' (email notifications
This is a bit of a rant, but I'm unclear why it matters which steps are
available as a build step vs. a post-build step.
I'm trying to create a simple job to grab debian packages archived from
various upstream "build" jobs and installing/configuring the debian
packages on a set of test servers as
