By default, Jenkins does not allow building jobs that have just been copied until they are re-saved. This is to prevent accidentally scheduled builds before the user is able to customize a newly cloned job (JENKINS-2494).
Jobs copied from the CLI don't need the same protection after copying. In fact, as there is no simple way to save a job without changing anything about its configuration using the CLI, it needs to behave differently.
- is related to
-
JENKINS-21087 Don't hold off building until saved for jobs copied and updated from REST API
-
- Open
-
[JENKINS-20744] Don't hold off building until saved for jobs copied from CLI
Description |
Original:
By default, Jenkins does not allow building jobs that have just been copied until they are re-saved. This is to prevent accidentally scheduled builds before the user is able to customize a newly cloned job ( Jobs copied from the API don't need the same protection after copying. In fact, as there is no simple way to save a job without changing anything about its configuration using the CLI, it needs to behave differently. |
New:
By default, Jenkins does not allow building jobs that have just been copied until they are re-saved. This is to prevent accidentally scheduled builds before the user is able to customize a newly cloned job ( Jobs copied from the CLI don't need the same protection after copying. In fact, as there is no simple way to save a job without changing anything about its configuration using the CLI, it needs to behave differently. |
Summary | Original: Don't hold off building until saved for jobs copied from API | New: Don't hold off building until saved for jobs copied from CLI |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Resolution | Original: Fixed [ 1 ] | |
Status | Original: Resolved [ 5 ] | New: Reopened [ 4 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Reopened [ 4 ] | New: Resolved [ 5 ] |
https://github.com/jenkinsci/jenkins/pull/1034