|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
It looks like a duplicate, but more than one year has passed: JENKINS-18678
Manually reloading defeats the purpose of automated builds. Also, in my case, I cannot rely on "waiting 5 minutes": it has to be deterministic and it cannot be based on waiting "long enough".
If a rename requires a reload from disk, then it must do so autonomously without disturbing anything else (current builds, pending builds, etc.).
The next question that comes to mind is what about dependencies? What if the job I rename is used by another job, say by the Copy the Artifact? Does the rename action take care of updating that other job too?