Re: Pre-Checkout actions?
I don't think it will work for Hudson as it was created after the split and uses features added after that point. I cannot add any more than this as I have not used any version of Hudson after the split, or looked for the code. Chris On Monday, 18 February 2013 23:45:29 UTC, zw wrote: > > Hi Chris > > Would your plugin work for Hudson too ? > We tried and it didnt work. > > Thanks > > On Monday, April 30, 2012 5:55:16 AM UTC-7, cjo wrote: >> >> >> If you just want to remove the junction points between triggering a build >> and the checkout from SCM, >> You can use the pre-scm-buildstep plugin[1] which allows you to run most >> build steps at this point, including windows batch scripts. >> >> >> You could also use the post-build step, which should always run >> regardless of the result of the build, >> for more freedom at this point consider using the flexible publish plugin >> (use the always condition) and anybuildstep plugins to allow buildsteps to >> be run at this point. >> >> [1] https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep >> [2] https://wiki.jenkins-ci.org/display/JENKINS/Post+build+task >> [3] https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin >> [4] https://wiki.jenkins-ci.org/display/JENKINS/Any+Build+Step+Plugin >> >> Chris >> >> -- 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/groups/opt_out.
Re: Pre-Checkout actions?
Hi Chris Would your plugin work for Hudson too ? We tried and it didnt work. Thanks On Monday, April 30, 2012 5:55:16 AM UTC-7, cjo wrote: > > > If you just want to remove the junction points between triggering a build > and the checkout from SCM, > You can use the pre-scm-buildstep plugin[1] which allows you to run most > build steps at this point, including windows batch scripts. > > > You could also use the post-build step, which should always run regardless > of the result of the build, > for more freedom at this point consider using the flexible publish plugin > (use the always condition) and anybuildstep plugins to allow buildsteps to > be run at this point. > > [1] https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep > [2] https://wiki.jenkins-ci.org/display/JENKINS/Post+build+task > [3] https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin > [4] https://wiki.jenkins-ci.org/display/JENKINS/Any+Build+Step+Plugin > > Chris > > -- 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/groups/opt_out.
Re: Pre-Checkout actions?
pre-scm-buildstep plugin? YAY! Never heard of that nor seen it before but you have just made my life pretty much easier :) Thanks Chris! Take care Jan Am Montag, 30. April 2012 14:55:16 UTC+2 schrieb cjo: > > > If you just want to remove the junction points between triggering a build > and the checkout from SCM, > You can use the pre-scm-buildstep plugin[1] which allows you to run most > build steps at this point, including windows batch scripts. > > > You could also use the post-build step, which should always run regardless > of the result of the build, > for more freedom at this point consider using the flexible publish plugin > (use the always condition) and anybuildstep plugins to allow buildsteps to > be run at this point. > > [1] https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep > [2] https://wiki.jenkins-ci.org/display/JENKINS/Post+build+task > [3] https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin > [4] https://wiki.jenkins-ci.org/display/JENKINS/Any+Build+Step+Plugin > > Chris > >
Re: Pre-Checkout actions?
If you just want to remove the junction points between triggering a build and the checkout from SCM, You can use the pre-scm-buildstep plugin[1] which allows you to run most build steps at this point, including windows batch scripts. You could also use the post-build step, which should always run regardless of the result of the build, for more freedom at this point consider using the flexible publish plugin (use the always condition) and anybuildstep plugins to allow buildsteps to be run at this point. [1] https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep [2] https://wiki.jenkins-ci.org/display/JENKINS/Post+build+task [3] https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin [4] https://wiki.jenkins-ci.org/display/JENKINS/Any+Build+Step+Plugin Chris
Re: Pre-Checkout actions?
Hi Søren, what about the join plugin and workspace cleaner plugin? You could with join spawn a job that executes "junction -d %1" and then on return to the upstream job configure woekspace cleaner to cleanup the workspace when the job is done. I doubt it but you may eventually have to create a second downstream job to clean the workspace. I don't know if the WS cleaner evaluates a job as done if the join plugin spwans the junction removal as downstream but I assume it should work straight away as the original job is still in the build queue but on hold. Take care Jan Am Freitag, 27. April 2012 14:04:21 UTC+2 schrieb Søren Pingel Dalsgaard: > > mikeguz gmail.com> writes: > > So ideally, there would be an unconditional pre-build step that I could > > configure to remove any "junction" points before invoking any workspace > > cleanup steps. > > Did you ever solve this problem? We have a similar problem on our build > server. Simply cleaning up ALL junctions using "junction -d %1" before > deleting the files would be great! > > Thanks in advance, > Søren > >
Re: Pre-Checkout actions?
mikeguz gmail.com> writes: > So ideally, there would be an unconditional pre-build step that I could > configure to remove any "junction" points before invoking any workspace > cleanup steps. Did you ever solve this problem? We have a similar problem on our build server. Simply cleaning up ALL junctions using "junction -d %1" before deleting the files would be great! Thanks in advance, Søren
