On Monday, 7 April 2014 16:19:12 UTC+1, LesMikesell wrote:
On Mon, Apr 7, 2014 at 3:18 AM, Sam Liddicott
s...@liddicott.comjavascript:
wrote:
Instead of batch tasks, I'm using the build pipeline. it is better
suited to
my needs and provides better visibility of the tasks that may
Instead of batch tasks, I'm using the build pipeline. it is better suited
to my needs and provides better visibility of the tasks that may follow.
Sam
On Friday, 4 April 2014 09:20:50 UTC+1, Sam Liddicott wrote:
Batch tasks can only be shell commands.
I'd like to be able to run any build
Batch tasks can only be shell commands.
I'd like to be able to run any build step type as a batch command - e.g.
publish-over-cifs
This is something that would take place after a build has been verified and
so can't be another regular build step.
This purpose meets the aims of batch task:
I want to publish-over-cifs with the jenkins session credentials which in
this case are also the windows domain credentials.
There seems to be no form of place-holder in the credential-store or
anywhere that will cause the jenkins user's jenkins credentials to be used.
How shall this be done?
