Sorry, this was supposed to have gone to the list ...
----- Forwarded message from Bap <[email protected]> -----
Date: Wed, 27 Jun 2012 14:33:46 +0100
From: Bap <[email protected]>
Subject: Re: New extra run conditions plugin to fork to jenkinsci
To: cjo <[email protected]>
Quoting cjo <[email protected]>:
Hi,
Can someone with permission please fork
https://github.com/cjo9900/extra-run-conditions-plugin
Please also create Jira component for this.
My github and jenkins-ci username is cjo9900
This plugin will contain extra conditions for the run-condition plugin,
these are separate than the main plugin as suggested by Bap in
https://github.com/jenkinsci/run-condition-plugin/pull/6
Can this plugin be named for what it provides eg Build+Cause+Run+Condition ?
The reason is that if we just have one big bucket, then you can only
add all or none of the conditions.
This means that:
1. the list of conditions in the drop down will continue to grow into
an ever longer list containing everything that anyone might want to
switch on - which will become very painful if you only use a couple of
conditions
2. an admin cannot make a decision as to what is available on the
instance (eg. I do not want any generic scripting within a job
configuration ...)
The extension mechanism gives the admin the ability to choose what is
available in a jenkins instance, I'd rather not have to write code and
a configuration interface to disable extensions that I don't want
Cheers,
Bap.
Wiki page has been created for this at
https://wiki.jenkins-ci.org/display/JENKINS/Extra+Run+Conditions+Plugin
Thanks
Chris
----- End forwarded message -----
