-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
jenkins 2.277.3
workflow-multibranch 2.22
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.
- duplicates
-
JENKINS-21400 Provide more robust suppression of SCM polling for copied jobs
-
- Open
-
- relates to
-
JENKINS-2494 Copied jobs should be disabled by default
-
- Resolved
-
This bug is probably causing issues with our company's jenkins server.
When cloning Multibranch pipeline job, the build runs immediatelly with configuration from original project.
For our projects this requires manual deletion of unwanted artifacts that were created during the build.
Our current jenkins version is 2.289.3 and this happens in a few recent versions. It didn't happen a few months ago, but can't tell in which version introduced this bug.