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 C
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]
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
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
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 s
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 ju
