-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
Jenkins 1.588
cloudbees-folder-plugin 4.7
After copying a Folder, I notice that none of the jobs within it can be launched (see "copied_folder_page.png" snapshot). Notice that we have a Test1 job, but there is no "Build Now" button to launch it.
As we can see in the snapshot "job_page.png", the project seems to be enabled (i.e. we still have a button to disable it), but, at the same time, the "Build Now" button in the left menu is gone.
The only workaround for this is disabling the job and enabling it again.
- duplicates
-
JENKINS-20003 Provide action to save all unsaved jobs in a folder after copy
-
- Open
-
[JENKINS-25595] After copying a Folder, all jobs within it are disabled
Aritz Bastida
created issue -
Aritz Bastida
made changes -
| Environment | Original: Jenkins 1.588 |
New:
Jenkins 1.588 cloudbees-folder-plugin 4.7 |
| Link | New: This issue duplicates JENKINS-20003 [ JENKINS-20003 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Aritz Bastida
added a comment - Thanks! It was confusing to me, but I understand now that it has been implemented this way to prevent accidental runs...
Aritz Bastida
added a comment - Thanks! It was confusing to me, but I understand now that it has been implemented this way to prevent accidental runs... Specifically to prevent scheduled triggers from running until after you have verified that the new version of the job is actually right.
| Labels | Original: folder plugin |
| Workflow | Original: JNJira [ 159569 ] | New: JNJira + In-Review [ 196128 ] |
Any job you copy is disabled (or rather, not buildable) by default. You usually don't recognize it because the form opens and you generally change things, and upon Saving the job becomes buildable.