6. Case #1 of 12 - Backup schmakups
• Upgraded with production server, no backups
• Canʼt start old version either
6
6
7. Case #1 of 12 - Backup schmakups
• Upgraded with production server, no backups
• Canʼt 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 checklist
Confluence JIRA
Layout and Menu Look and feel
Search Issue Navigator
Permissions Workflow transitions
Attachments Attachment links
Plugins Plugins
7
7
10. Case #2 of 12 – Murphyʼs Law at work
• Server crashed with sound backup strategy in place
8
8
11. Case #2 of 12 – Murphyʼs Law at work
• Server crashed with sound backup strategy in place
Restore?
8
8
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 Confluence upgrade
10
10
14. Case #3 of 12 –
• Remote operations fail to complete after Confluence upgrade
• Firewall?
10
10
15. Case #3 of 12 –
• Remote operations fail to complete after Confluence upgrade
• Firewall?
• Network?
10
10
16. Case #3 of 12 –
• Remote operations fail to complete after Confluence upgrade
• Firewall?
• Network?
• Virus scanner?
10
10
17. Case #3 of 12 –
• Remote operations fail to complete after Confluence upgrade
• Firewall?
• Network?
• Virus scanner?
• RPC plugin?
10
10
18. Case #3 of 12 –
• Remote operations fail to complete after Confluence upgrade
• Firewall?
• Network?
• Virus scanner?
• RPC plugin?
• CUSTOMIZIATION!
10
10
19. Pro Tip #3 of 12 - Track your changes
• Keep rolling log
• Confluence page
Inventory at upgrade time
• Modz_detector ( Administration -> System Info )
11
11
20. Pro Tip #3 of 12 - Track your changes
• Keep rolling log
• Confluence page
Inventory at upgrade time
• Modz_detector ( Administration -> System Info )
JIRA find . –newer views
Connie find . –newer users
11
11
22. Case #4 of 12 – Plugin safari
After upgrading in testing JIRA no longer starts
13
13
23. Case #4 of 12 – Plugin safari
After upgrading in testing JIRA no longer starts
2010-04-30 09:44:38,151 main FATAL [atlassian.jira.upgrade.ConsistencyLauncher]
An Error occurred during ConsistencyLauncher servlet context initialisation -
com.atlassian.plugin.DefaultModuleDescriptorFactory.
<init>(Lcom/atlassian/plugin/hostcontainer/HostContainer;)
java.lang.NoSuchMethodError: com.atlassian.plugin.DefaultModuleDescriptorFactory.
<init>(Lcom/atlassian/plugin/hostcontainer/HostContainer;)
13
13
25. Pro Tip #4 of 12 - Know your plugins
• System
• Canʼt mess with ʻem
• Bundled
• Can be upgraded independently, disabled
• Third-party
• Skyʼs the limit
15
15
26. Pro Tip #4.5 of 12 – Upgrade your plugins
• The old way…
16
16
27. Pro Tip #4.5 of 12 – Upgrade your plugins
• The old way…
17
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
19
19
30. Case #5 of 12 – Major upgrades
• Attachments not being converted as advertised
• XML not suitable for large restores
19
19
31. Case #5 of 12 – Major upgrades
• Attachments not being converted as advertised
• XML not suitable for large restores
Attachment change with 2.7.3
19
19
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 months
21
21
34. Case #6 of 12 – Little pestering flies…
• Preserving old-school navigation in JIRA 4.1+
22
22
35. Pro Tip #6 of 12 – Engage your users
• Involve in upgrade decision
• Invite them to perform QA ( in testing! )
23
23
36. Case #7 of 12 – Gadgets load slowly
• After upgrading to JIRA 4.0 gadgets take forever to load
24
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 config?
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 config?
• Profiling data looking good…
24
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 config?
• Profiling 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://confluence.atlassian.com/display/DOC/Confluence+Release+Summary
• http://confluence.atlassian.com/display/JIRA/JIRA+Release+Summary
Encourage key stakeholders to evaluate
25
25
44. Case #8 of 12 – The devil is in the details
• Setup new JIRA for upgrade, receiving “404 Not Found”
27
27
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
48. Case #9 of 12 – The complex upgrade
• Receiving 404 page after upgrading JIRA and Confluence
• New
• Hardware
• Windows XP -> Debian linux
• Standalone -> EAR/WAR
• Trouble with configuring
• LDAP
• SSL
• Days to resolve…
29
29
50. Pro Tip #9 of 12 –
• Deploy JIRA on new server, restore data
30
30
51. Pro Tip #9 of 12 –
• Deploy JIRA on new server, restore data
• Deploy Confluence, restore data
30
30
52. Pro Tip #9 of 12 –
• Deploy JIRA on new server, restore data
• Deploy Confluence, restore data
• KB article to fix class loading
30
30
53. Pro Tip #9 of 12 –
• Deploy JIRA on new server, restore data
• Deploy Confluence, restore data
• KB article to fix class loading
• Configure SSL
• Mail server
• LDAP server
• Tomcat
30
30
54. Pro Tip #9 of 12 –
• Deploy JIRA on new server, restore data
• Deploy Confluence, restore data
• KB article to fix class loading
• Configure SSL
• Mail server
• LDAP server
• Tomcat
• Configure LDAP
30
30
55. Case #10 of 12 –
Duplicate mail notifications
31
31
56. Case #10 of 12 –
Duplicate mail notifications
# Testing
• Production data
• Jelly scripts
• Workflow transitions
Forgot notification schemes
31
31
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 UI
32
32