|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" 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.
Usecase: As mentioned in my second commant, we're using the plugin in combination with the pipeline view to build deployment pipelines, so we'd have deployment jobs (deploy_job1, deplob_job2, deplob_job2) that are chained by the trigger plugin (so job1 triggers job2 and so on).
If we want to deploy ONLY to platform 1 (deploy_job1), we need to disable the triggering of deploy_job2. In other words, we regularly need to interrupt a deployment pipeline. And that's where a disabled state would come in very handy.
It would be useful because we wouldn't have to delete and re-configer the trigger and we could avoid installing / using additional plugins like the ones recommended by you...