Re: Any build-step type as batch task
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 follow. Wouldn't a post-build action work? Or do you need to be able to trigger the steps separately? Need to trigger separately. -- 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.
Re: Any build-step type as batch task
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 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: Help for feature: Batch tasks This feature allows you to associate shell scripts that perform some tasks on Hudson that are manually triggered occasionally (for example, performing a release, doing copyright header check, integrating newer versions of library jars to CVS, etc.) This allows your team to run lengthy and/or recurring tasks on Hudson asynchronously. It also allows people outside your team to trigger the tasks, thereby preventing the common we need to do XYZ but only Kohsuke knows how to do this and he's on vacation! problem. - but batch tasks doesn't seem to provide it. How could I do this. I *could* create another task whose definition is to grab the artefacts from the first project as a build step, and then publish, but it is an ugly solution. Sam -- 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.
Any build-step type as batch task
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: Help for feature: Batch tasks This feature allows you to associate shell scripts that perform some tasks on Hudson that are manually triggered occasionally (for example, performing a release, doing copyright header check, integrating newer versions of library jars to CVS, etc.) This allows your team to run lengthy and/or recurring tasks on Hudson asynchronously. It also allows people outside your team to trigger the tasks, thereby preventing the common we need to do XYZ but only Kohsuke knows how to do this and he's on vacation! problem. - but batch tasks doesn't seem to provide it. How could I do this. I *could* create another task whose definition is to grab the artefacts from the first project as a build step, and then publish, but it is an ugly solution. Sam -- 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.
publish using jenkins own credentials
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? Could the credentials store have a placeholder which evaluates to the logged in user? Could Groovy make it happen? Or have I missed something more simple. Thanks Sam -- 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.
