Take a look at http://javadoc.jenkins-ci.org/?hudson/LauncherDecorator.html
I guess most SCMs uses the launcher to do their work. Robert Sandell Software Tools Engineer - SW Environment and Product Configuration Sony Mobile Communications From: [email protected] [mailto:[email protected]] On Behalf Of Arvid E.P. Sent: den 29 maj 2013 12:32 To: [email protected] Subject: chroot buildwrapper heya, i'm trying to implement a buildwrapper plugin that executes the job inside a chroot that is the workspace. Any idea how i could overload all the executing classes to go through the chroot? I suppose the answer is that you cannot, which is why my fallback is to implement only a single "execute shellscript in chroot" plugin, however, the SCM plugins assume that the workspace is the root of the source, while in this case the workspace would be the chroot. Is there any way to tell all subsequent plugins that the workspace has moved to workspace +"/something/else" ? -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
