Related to the HipChat Datacenter documentation you will have to shut down your datacenter for software upgrades.
Shipping HipChat as a VM image is already breaking our automated pipeline. So an engineer needs to manually do the upgrade. But a full stop of the service will also interrupt our users.
That is not really DevOps like ;-)
Is there any plan to improve this?
Thanks for your comment.
Currently we recommend the full shutdown of Chat during upgrade to help mitigating any potential issues, alternatively, an option could be you systematically remove one node at a time from a cluster, upgrade it, and put it back on the layer. That should also work, unless the upgrade involves changing something in the structure or settings of the external data stores.
However, we understand this concern and we filed a suggestion for our development in this regard:
Please ensure you register and vote for it. Also, feel free to add any relevant information you judge it's relevant.
Regarding the topic you brought about HipChat as a VM image, we have checked with our development team and there is an ongoing initiative in this regard:
I hope that helped. Please let us know if you have any further questions.
...from the beginning. We have built up a lot of content in HipChat, with it being a core tool in our distributed company model. While it is true that we didn’t need to move to Slack immediately, we felt it...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs