jira-importer
commented
12 years ago bap:
I have just released the Flexible Publish Plugin https://wiki.jenkins-ci.org/display/JENKINS/Flexible+Publish+Plugin which Uses Run Conditions https://wiki.jenkins-ci.org/display/JENKINS/Run+Condition+Plugin to decide whether to execute a build step.
The Run Condition is an Extension Point which will enable plugins to be created which can provide new Conditions.
I think this condition can be enabled in a simple plugin which provides a "Trigger type" Run Condition.
This afternoon I will upload an example Run Configuration plugin which you can clone and then implement your trigger logic.
Our teams use ftp publishing as a way to deploy ears to our development environment. This is a huge productivity gain over what we previously had. However, not all teams want the ear deployed from triggered builds. For example, we do poll scm each night, and on weekends, we do a timer trigger build. But some teams are saying they don't want the ear deployed on those triggered builds. (I can explain the reasons if you need me to)
Please add a feature something like a section that has checkboxes something like this
Publish on which of the following
And probably have all 3 selected by default since that's the backwards compatible behavior. Another real nice-to-have would be to configure these defaults in the master configuration so that when a job configures ftp publishing for the first time, the most commonly used of these checkboxes (for the organization) is already setup.
Note that I may look into implementing this for the FTP-Publisher Plugin, but I would strongly prefer it gets rolled into this plugin which is more comprehensive and active. Please let me know how likely it is that this feature will get implemented. Also, let me know if you'd like me to look into implementing it for you.
Originally reported by jacob_robertson, imported from: Choose build trigger types that will result in publishing