[JIRA] [core] (JENKINS-14030) renaming a job does not preserve history
Craig Lawton-Devine commented on JENKINS-14030 renaming a job does not preserve history I renamed a job today and the history was not lost. No manual steps were required and the history was there instantly. The only issue I've had is that a downstream job that runs on promotion of the renamed job still referred to the old job name. 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/d/optout.
[JIRA] [core] (JENKINS-14030) renaming a job does not preserve history
Sarah Woodall commented on JENKINS-14030 renaming a job does not preserve history You only need to reload the configuration manually from disk after you have renamed a job, as far as I can see. After you have done that, your history is reinstated. So this bug is frightening, because it looks as though the history has been lost, but it turns out to be harmless. 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.
[JIRA] [core] (JENKINS-14030) renaming a job does not preserve history
Jessica Sarah commented on JENKINS-14030 renaming a job does not preserve history I have 1.514. After renaming jobs give it sometime to work out the disk files (in my case ~5 min), then click on "Manage Jenkins / Reload Configuration from Disk" and the history was reloaded OK. 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.
[JIRA] [core] (JENKINS-14030) renaming a job does not preserve history
Martin dAnjou commented on JENKINS-14030 renaming a job does not preserve history 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? 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.
[JIRA] [core] (JENKINS-14030) renaming a job does not preserve history
Derek Brown commented on JENKINS-14030 renaming a job does not preserve history The rename action does take care of updating jobs that use Copy Artifact and dependencies. 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.
[JIRA] [core] (JENKINS-14030) renaming a job does not preserve history
Derek Brown commented on JENKINS-14030 renaming a job does not preserve history This one bit us hard today. 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.
