Thanks Matthew, I'm not too bothered about failing the build, so observation only should be fine. I should have phrased my question slightly differently though, as the bit I'm really struggling with is how to set up a global build step. Any idea how this might be achieved?
-T On Thursday, 28 August 2014 16:26:14 UTC+1, Matthew Moore wrote: > > I'd bet you could build something with: > http://javadoc.jenkins-ci.org/hudson/model/BuildStepListener.html > > However, their intent is purely observation, so YMMV. > > > Not sure if there are any more suitable hooks that are intended for > mutation. I think there is definitely a use case for global *notifiers*, > e.g. email-ext / IRC for all jobs, less sure about recorders or mutations > since they seem like they would more often need context... > > (shrug), hope that helps. > -M > > > > On Thu, Aug 28, 2014 at 8:04 AM, scarytom <[email protected] <javascript:> > > wrote: > >> Is it possible to write a Jenkins plugin that enhances the "Configure >> System" screen to allow the user to define a global post-build step that >> runs after every single build and performs a simple check that could mark >> the build as a failure? I want to write something that allows me to check >> that no build has left certain services running. >> >> -- >> 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] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Matthew Moore > DI/Docker (aka Convoy) > Developer Infrastructure @ Google > -- 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/d/optout.
