You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Is there any performance improvements in updating Crowd to 3.X? My test environments are connected to the Production version of CROWD and i would not be able to back out of the update. unless someone has a suggestion on how to rollback a production update of crowd. So I want to be sure there is value in the effort.
The Crowd upgrade process for us has been very reliable - have been using Crowd for 5-6 years and can’t think of one time the upgrade has failed (disclaimer: personal experience only, your mileage may vary etc etc).
backing up crowd before an upgrade is pretty straight forward either using the XML option Ann mentioned, or a DB and file system backup. Rolling back is then pretty painless.
in terms of benefits of 3.x over 2.x, it’s always good to keep relatively up to date as the more distance between upgrades the riskier they can get, security updates (unsure if there’s any CVEs in the version you’re on), but in terms of features a recent version now has a great audit log functionality (with a much more useful audit log search than Jira and Confluence) and a big help for us (but possibly not even noticed by some), whenever a drop down list of directories is displayed, they’re now sorted alphabetically! With 15 directories, this is a big help for us. There was a change (possibly between 2.x and 3.x) where the UI no longer uses the REST API for its own calls instead using its own background access which for us has given a nice speed improvement for administration.
In summary, I’d vote yes.
There have been a lot of changes between Crowd 2.11 and 3.2. Please check out all the Crowd 3.x bug fixes and features on the Crowd 3.0 Release Notes.
More changes are documented here: Crowd 3.0 Upgrade Notes
You can roll back an upgrade by installing the old version and then importing an XML backup from your pre-upgrade instance. However, I recommend that you stand up a Crowd 2.11 to connect your test environment to, in order to test the upgrade safely and avoid surprises in Production. Crowd 2.11 does not reach end of life until Jan 12, 2019 so you have some time.
Options for upgrading Crowd are described in Upgrading Crowd.