I am alwats wondering why there are no UML diagram for these plugins? I mean - there is nothing better to describe plugin capabilities to java developers than UML diagram illustrating all entry points ; I/O , data- and other -flows. My opinion is that such topics are time wasting and human resource killers by definition and should be eliminated from the dev environment asap...
Umm ... yeah ... sorry to become too emotional. It is just that I develop in NSIS it is sooo freaking frustrationg to not have any diagram generation or doc generation support for this installer scripting platform ... so I am forced to slowly devrelop my own .. .bah :( Any - back to topic - isn't it smarter to not perform such on-demand actions but make sure you have queied excatly what you need? 90% CI issues is that admins have underestamted the poer of well-formed build infrastrukture that just fighting against the unwanted results. ;) 2012/6/29 Jesse Farinacci <jie...@gmail.com> > Greetings, > > On Fri, Jun 29, 2012 at 6:04 AM, MaxiTrompe <mtromp...@gmail.com> wrote: > > I am trying to implement a function that would be triggered when a build > is > > added to the queue. > > Check if either BuildWrapper or QueueDecisionHandler will work for you: > > http://javadoc.jenkins-ci.org/hudson/tasks/BuildWrapper.html > http://javadoc.jenkins-ci.org/hudson/model/Queue.QueueDecisionHandler.html > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. > -- A.C. Linards L.
