HipChat for devops
January 17, 2018

HipChat for devops

Hugo Romani Cortes | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with HipChat

HipChat has been selected as a product from Atlassian's suite. Because we already used Bitbucket and because we were looking for a persistent chat room, HipChat was chosen. This product was not only used by our devops teams in order to discuss and receive notifications but also by software craftsmanship in order to debate technologies and help each other.
  • Persistent chat room. HipChat stores the communication and allows you to follow a discussion without being involved from the beginning.
  • Multi tenant rooms. We can create as many discussion rooms as we want.
  • Third-party integration. HipChat exposes an API that can be used by third-party applications (i.e. Prometheus for monitoring, Jenkins for CI/CD, etc).
  • Research should be enhanced
  • Possibility to integrate a chat bot
I used HipChat in a company which was pro "open source" and another one which is pro Atlassian.
For the "open source" company I was not involved in the decision of selecting HipChat but I know that the integration with Jenkins and other internal tools were drivers for selecting HipChat.

For the other company, we have HipChat and Microsoft Teams. Unfortunately, HipChat is not the "default" chat room and we are using Microsoft Teams more which integrates very well with Microsoft products.
HipChat is very suitable in a devops team:
- allows persistent communication between team members
- can receive notifications from Jenkins or Prometheus
- allows multi tenant rooms

Nevertheless, HipChat can be a new way of working for some people that require training. The learning curve of HipChat is very simple, but for a company which is not familiar with these new tools (chat rooms), it might be a bit disturbing.

HipChat (discontinued) Feature Ratings

Search
5
Chat
8
Notifications
7
Discussions
8
Access control
6
Advanced security features
6