|
||||||||
|
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.
David,
What I did:
1) Copied my current jenkins home out of the way ("old").
2) Installed fresh 1.503, and re-installed all plugins I knew of (current versions of plugins).
3) "meld"ed (a diff-merge tool for Linux) old and new configs to see things still missing in the 1.503 build. Manually installed as much as possible as far as system configuration went.
4) Manually merged global config.xml.
5) Copied over userContent/ from old.
6) Copied over the jobs from the old.
7) Iteratively kept starting and monitoring the jenkins log for exception, and tried to resolve all exception until everything was started.
8) Reset passwords because I believe the master key changes when you do this, and it breaks all your passwords. (We use ssh keys for most stuff, so, that was no big deal for us: basically slave passwords and the occasional ssh password.)
Things I ran into: views missing tree attribute, build.xml files were missing a git related element that I had to copy into all build.xml files that were missing them. I think that was about it.
If necessary, only copy over 1 job at a time until you discover most of the issues. I know the log rotation stuff also changed, which, going backward, will cause you to lose all your "keep builds..." settings. I highly recommend "Configuration Slicer" plugin for fixing those (works on 1.503, but not on newer versions.)
Hope this helps.