Please can some one look at this, as it has been around a while
On Tuesday, May 22, 2012 11:54:20 PM UTC+1, cjo wrote: > > Hi all, > > Can someone look at and test out, > https://github.com/jenkinsci/parameterized-trigger-plugin/pull/17 > > This adds the runcondition plugin in place of the default Build status > behaviour, this fixes outstanding two issues, when using the latest version > of the runcondition. > > This is basically the plugin interface as commented by Kohsuke in > https://github.com/jenkinsci/parameterized-trigger-plugin/pull/13#issuecomment-3898808 > on > pull 13 for issue > JENKINS-8009<https://issues.jenkins-ci.org/browse/JENKINS-8009> > . > > This also make the config a lot more flexible as I was having to alter the > build status via the text finder plugin to go down different path, which > means that you are limited to only three possible paths. > > > Issues Corrected > JENKINS-9209 <https://issues.jenkins-ci.org/browse/JENKINS-9209> Condition > to demand a parameter to exist - User can set a boolean, string or > expression condition to check for this. > JENKINS-4585 <https://issues.jenkins-ci.org/browse/JENKINS-4585> Batch > condition - shell script need to implement a shell script condition in run > condition plugin. > > > Can be used to fix > JENKINS-8009 <https://issues.jenkins-ci.org/browse/JENKINS-8009> Groovy > script to add conditions to the parameterized trigger - if a groovy > condition is added to the groovy plugin. > > Thanks for reading > Chris > >
