Upgrade Dos and Don'ts for JIRA and Confluence - Atlassian Summit 2010

  • Published on
    11-May-2015

  • View
    3.989

  • Download
    0

Embed Size (px)

DESCRIPTION

Upgrade Dos and Don'ts for JIRA and Confluence Jeff Curry, Atlassian

Transcript

  • 1.1 1

2. Upgrade Dos and Don'ts for JIRA + Conuence Jeff Curry, Technical Support, Atlassian22 3. JIRA Master!33 4. Agenda Case review Best practices Prevention Watch out!Questions? 44 5. Best Practices - No Cowboys Allowed 5 5 6. Case #1 of 12 - Backup schmakups Upgraded with production server, no backups Cant start old version either 6 6 7. Case #1 of 12 - Backup schmakups Upgraded with production server, no backups Cant start old version either 6 6 8. Pro Tip #1 of 12 Backup, cowboy! Backup: Application directory, data directory, database Create an upgrade checklist 7 7 9. Pro Tip #1 of 12 Backup, cowboy! Backup: Application directory, data directory, database Create an upgrade checklistConfluenceJIRALayout and Menu Look and feelSearch Issue NavigatorPermissionsWorkflow transitionsAttachmentsAttachment linksPluginsPlugins 7 7 10. Case #2 of 12 Murphys Law at work Server crashed with sound backup strategy in place88 11. Case #2 of 12 Murphys Law at work Server crashed with sound backup strategy in placeRestore? 88 12. Pro Tip #2 of 12 - Practice restores Preferably not when production is down 9 9 13. Case #3 of 12 Remote operations fail to complete after Conuence upgrade10 10 14. Case #3 of 12 Remote operations fail to complete after Conuence upgrade Firewall?10 10 15. Case #3 of 12 Remote operations fail to complete after Conuence upgrade Firewall? Network?10 10 16. Case #3 of 12 Remote operations fail to complete after Conuence upgrade Firewall? Network? Virus scanner?10 10 17. Case #3 of 12 Remote operations fail to complete after Conuence upgrade Firewall? Network? Virus scanner? RPC plugin?10 10 18. Case #3 of 12 Remote operations fail to complete after Conuence upgrade Firewall? Network? Virus scanner? RPC plugin? CUSTOMIZIATION! 10 10 19. Pro Tip #3 of 12 - Track your changes Keep rolling log Conuence pageInventory at upgrade time Modz_detector ( Administration -> System Info )11 11 20. Pro Tip #3 of 12 - Track your changes Keep rolling log Conuence pageInventory at upgrade time Modz_detector ( Administration -> System Info ) JIRA find . newer views Connie find . newer users11 11 21. Prevention Better safe than sorry 1212 22. Case #4 of 12 Plugin safari After upgrading in testing JIRA no longer starts13 13 23. Case #4 of 12 Plugin safari After upgrading in testing JIRA no longer starts2010-04-30 09:44:38,151 main FATAL [atlassian.jira.upgrade.ConsistencyLauncher] An Error occurred during ConsistencyLauncher servlet context initialisation - com.atlassian.plugin.DefaultModuleDescriptorFactory. (Lcom/atlassian/plugin/hostcontainer/HostContainer;) java.lang.NoSuchMethodError: com.atlassian.plugin.DefaultModuleDescriptorFactory. (Lcom/atlassian/plugin/hostcontainer/HostContainer;) 1313 24. Case #4 of 12 Plugin safari assign-from-customfield-plugin-1[1].3.jar jira-dashboard-sharing-1[1].1-JIRA3.11.jar atlassian-configurableobjects-0.9.jar jira-fisheye-plugin-2.2.4.jar atl-jira-subversion-plugin-0.10.4.1.jar jira-greenhopper-plugin-4.3.1.jar atlassian-plugins-0.23.2.jarjira-misc-workflow-extensions-1[1].3.jar atlassian-tagutil-0.1.jar jira-toolkit-0.7.30.jar dwr-2.0.5.jar jregex-1.2_01.jar javamail-1.3.3.jarlanguage_default.jar jira-bamboo-plugin-2.3.1.jarldapsdk-4.1.jar jira-calendar-plugin-1.9.jarmkk-jira-plugin-1[1].4.0-Jira-3.10.jar jira-charting-plugin-1.4.1.jartdt-easyadmin-plugin-1.1.jar14 14 25. Pro Tip #4 of 12 - Know your plugins System Cant mess with em Bundled Can be upgraded independently, disabled Third-party Skys the limit1515 26. Pro Tip #4.5 of 12 Upgrade your plugins The old way16 16 27. Pro Tip #4.5 of 12 Upgrade your plugins The old way17 17 28. Pro Tip #4.5 of 12 Upgrade your plugins The new way!18 18 29. Case #5 of 12 Major upgrades Attachments not being converted as advertised 1919 30. Case #5 of 12 Major upgrades Attachments not being converted as advertised XML not suitable for large restores 1919 31. Case #5 of 12 Major upgrades Attachments not being converted as advertised XML not suitable for large restoresAttachment change with 2.7.3 1919 32. Universal Pro Tip - RTFM Consult documentation Release notes Upgrade guide [ This half intentionally left blank ]20 20 33. Pro Tip #5 of 12 - Communicate with stake holders Evaluate milestone releases New release cycle- 3-4 months21 21 34. Case #6 of 12 Little pestering ies Preserving old-school navigation in JIRA 4.1+ 2222 35. Pro Tip #6 of 12 Engage your users Involve in upgrade decision Invite them to perform QA ( in testing! ) 2323 36. Case #7 of 12 Gadgets load slowly After upgrading to JIRA 4.0 gadgets take forever to load24 24 37. Case #7 of 12 Gadgets load slowly After upgrading to JIRA 4.0 gadgets take forever to load Reverse-proxy?24 24 38. Case #7 of 12 Gadgets load slowly After upgrading to JIRA 4.0 gadgets take forever to load Reverse-proxy? Server resources?24 24 39. Case #7 of 12 Gadgets load slowly After upgrading to JIRA 4.0 gadgets take forever to load Reverse-proxy? Server resources? Client cong?24 24 40. Case #7 of 12 Gadgets load slowly After upgrading to JIRA 4.0 gadgets take forever to load Reverse-proxy? Server resources? Client cong? Proling data looking good24 24 41. Case #7 of 12 Gadgets load slowly After upgrading to JIRA 4.0 gadgets take forever to load Reverse-proxy? Server resources? Client cong? Proling data looking good 1/5 second 1 second page load time 24 24 42. Pro Tip #7 of 12 Test new features Review release summary pages http://conuence.atlassian.com/display/DOC/Conuence+Release+Summary http://conuence.atlassian.com/display/JIRA/JIRA+Release+SummaryEncourage key stakeholders to evaluate 2525 43. Watch out!26 26 44. Case #8 of 12 The devil is in the details Setup new JIRA for upgrade, receiving 404 Not Found 2727 45. Case #8 of 12 The devil is in the details Setup new JIRA for upgrade, receiving 404 Not Found 2010-04-20 16:07:38,561 main ERROR[jira.appconsistency.db.DatabaseConsistencyCheck]There was a SQL exception checking for database driver correctness. Skipping.org.apache.tomcat.dbcp.dbcp.SQLNestedException:Cannot create JDBC driver of class 'com.mysqljdbc.Driver' for connect URL'jdbc:mysql:localhost/jiradb?autoReconnect=true&useUnicode=true&characterEncoding=UTF8'27 27 46. Pro Tip #8 of 12 - Use the GUI! 2828 47. Case #9 of 12 The complex upgrade 2929 48. Case #9 of 12 The complex upgrade Receiving 404 page after upgrading JIRA and Conuence New Hardware Windows XP -> Debian linux Standalone -> EAR/WAR Trouble with conguring LDAP SSLDays to resolve 2929 49. Pro Tip #9 of 12 30 30 50. Pro Tip #9 of 12 Deploy JIRA on new server, restore data 3030 51. Pro Tip #9 of 12 Deploy JIRA on new server, restore data Deploy Conuence, restore data 3030 52. Pro Tip #9 of 12 Deploy JIRA on new server, restore data Deploy Conuence, restore data KB article to x class loading 3030 53. Pro Tip #9 of 12 Deploy JIRA on new server, restore data Deploy Conuence, restore data KB article to x class loading Congure SSL Mail server LDAP server Tomcat 3030 54. Pro Tip #9 of 12 Deploy JIRA on new server, restore data Deploy Conuence, restore data KB article to x class loading Congure SSL Mail server LDAP server Tomcat Congure LDAP3030 55. Case #10 of 12 Duplicate mail notications 3131 56. Case #10 of 12 Duplicate mail notications # Testing Production data Jelly scripts Workow transitionsForgot notication schemes 3131 57. Pro Tip #10 of 12 bin/setenv.sh: #DISABLE_NOTIFICATIONS="-Datlassian.mail.senddisabled=true-Datlassian.mail.fetchdisabled=true-Datlassian.mail.popdisabled=true Remove mail server in admin UI32 32 58. Conuence support #1 headache 3333 59. Case #11 of 12 Cutting corners34 34 60. Case #11 of 12 Cutting corners Step 1 Upgrade Conuence 3434 61. Case #11 of 12 Cutting corners Step 1 Upgrade Conuence Step 2 Old DB -> New Conuence34 34 62. Case #11 of 12 Cutting corners Step 1 Upgrade Conuence Step 2 Old DB -> New Conuence Step 3 Works good enough34 34 63. Case #11 of 12 Cutting corners Step 1 Upgrade Conuence Step 2 Old DB -> New Conuence Step 3 Works good enough 34 34 64. Case #11 of 12 Cutting corners Step 1 Upgrade Conuence Step 2 Old DB -> New Conuence Step 3 Works good enough # Step 4 Hmmm attachments missing34 34 65. Case #11 of 12 Cutting corners Step 1 Upgrade Conuence Step 2 Old DB -> New Conuence Step 3 Works good enough # Step 4 Hmmm attachments missing Step 5 Contact support, failing to mention this for awhile 34 34 66. Case #11 of 12 Cutting corners Step 1 Upgrade Conuence Step 2 Old DB -> New Conuence Step 3 Works good enough # Step 4 Hmmm attachments missing Step 5 Contact support, failing to mention this for awhile Step 6 ??? 34 34 67. Pro Tip #11 of 12 - Dont cut corners!Dont make assumptionsFreeze data for upgrade process Perfect practice makes perfect 3535 68. Case #12 of 12 $*#&$! Gadget loopback! Created internal checklist and tested, tested, tested!36 36 69. Case #12 of 12 $*#&$! Gadget loopback! Created internal checklist and tested, tested, tested!36 36 70. Pro Tip #12 of 12 3737 71. Pro Tip #12 of 12 Reverse-proxy Load-balancer More? Exit strategy 3737 72. SummaryBest Practices Prevention Watch out!38 38 73. Summary Best Practices Prevention Watch out!Go home, upgrade JIRA to 4.1 and Conuence to 3.2 3838 74. Resources 3939 75. Resources forums.atlassian.com conuence.atlassian.com conuence.atlassian.com/display/JIRAKB/JIRA+Knowledge+Base+Home conuence.atlassian.com/display/CONFKB/Conuence+Knowledge+Base+Home jira.atlassian.com support.atlassian.com Pssst Freenode IRC #atlassian, #atlassiandev 3939

Recommended

View more >