jenkinsci / jenkinsci/workflow-multibranch-plugin
[JENKINS-65900] Cloning multibranch pipeline job scans before changes can be made
- Dominant language
- Java
- Stars
- 87
- Forks
- 131
- PR merge metrics
- No merged PRs in 30d
Description
When a multibranch pipeline job is cloned it gets scanned immediately - even before the job configuration is saved. As a result builds may be kicked off that would of otherwise been ignored after the user had a chance to modify the git branch configuration such as changing the branch include filter.
Expected Behavior
New job is not scanned until after the configuration is applied/saved.
Actual Behavior
A scan is started and new builds are launched before the user has a chance to modify the job configuration.
Steps to Reproduce
- Create a multibranch pipeline job with some branches. Run a scan and let builds complete.
- Clone the job that was created above. Do not click save.
- In another tab look at the build queue and agent build executor status. Observe builds are being immediately launched.
---
Originally reported by mrichar2, imported from: Cloning multibranch pipeline job scans before changes can be made
Raw content of original issue
When a multibranch pipeline job is cloned it gets scanned immediately - even before the job configuration is saved. As a result builds may be kicked off that would of otherwise been ignored after the user had a chance to modify the git branch configuration such as changing the branch include filter.
Expected Behavior
New job is not scanned until after the configuration is applied/saved.Actual Behavior
A scan is started and new builds are launched before the user has a chance to modify the job configuration.Steps to Reproduce
- Create a multibranch pipeline job with some branches. Run a scan and let builds complete.
- Clone the job that was created above. Do not click save.
- In another tab look at the build queue and agent build executor status. Observe builds are being immediately launched.
environment
```
jenkins 2.277.3
workflow-multibranch 2.22
```
Contributor guide
Assessment
This issue has not been assessed yet.