|
||||||||
|
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.

Workflow is not a substitute for Job DSL. They are more or less orthogonal.
This is something that could be supported as a “branch source” in the Multi-Branch API, I think. (For example, the Git implementation has support for pull requests, which are hosted in a distinct repository.) Someone needs to write that branch source but I think it is a relatively minor exercise—the API does not require in-depth Jenkins plugin expertise.
That is the point of the Multi-Branch API: the creation of the subprojects (and their “garbage collection”) is automated.
No, this is a valid bug report, I was just offering tangential suggestions based on your use case. I am not promising to implement it (assuming you are not a CloudBees support customer), but a pull request would be welcome.