| It would be fantastic to somehow allow a single Jenkinsfile with the declarative pipeline model to have multiple pipelines in it (today this appears to work somewhat). This would mean you could define independent units of work in a single file and not rely on some external mechanism. This would also allow for separate sets of triggers for each section of the pipeline. This would mean scenarios like: 1) Run this pipeline nightly, but this pipeline daily
2) Trigger this scenario on X comment on GitHub, but this other scenario on Y Would be possible. We have huge matrices of testing and need to be able to select the workload |
