-
Improvement
-
Resolution: Fixed
-
Major
-
None
-
Platform: All, OS: All
When you copy a job it should be disabled by default so that any modifications
can be made to it before it tries to run.
- is duplicated by
-
JENKINS-5975 New job starts running before I have a chance to configure the job
-
- Closed
-
-
JENKINS-2503 create a job from existing job start build to quickly
-
- Closed
-
- is related to
-
JENKINS-21400 Provide more robust suppression of SCM polling for copied jobs
-
- Open
-
-
JENKINS-20003 Provide action to save all unsaved jobs in a folder after copy
-
- Open
-
- relates to
-
JENKINS-65900 Cloning multibranch pipeline job scans before changes can be made
-
- Open
-
I am currently working on the fix for this which follows the same approach as slaves, i.e. the cloned job will be in a temporary disabled state until the initial save. Unlike the initial patch in comment 1, the actual enabled/disabled status will be carried over from the job being cloned.
Once this has been completed and tested internally (Yahoo!), I will look into merging upstream.