Posts about Hipchat
We’re quickly approaching the final days of Stride and Hipchat Cloud - these products will be discontinued on February 15, 2019. All Stride and Hipchat Cloud APIs, developer support, and Marketplace support tickets will remain available through Feb 15, 2019; Stride and Hipchat Cloud services will shut down after this date.
Today, we're announcing a new strategic partnership between Atlassian and Slack.
Learn how to theme your HipChat add-ons Sidebar based on the user selected theme.
Have you ever wanted to try out a full serverless architecture? Or write a HipChat plugin? The new open source boilerplate from GorillaStack, announced at this year's AtlasCamp, enables developers to easily deploy the back-ends for their plugins to Amazon Web Services' serverless products in Lambda, API Gateway, DynamoDB, and S3.
I've built many add-ons on top of Atlassian products over the last five years. In that time, the most satisfying add-ons I've built were also the simplest. Since HipChat Connect launched in beta last November, I've been experimenting with new ways to bring tighter integrations with apps like Uber, Facebook and Twitter, into HipChat. Today, I'm sharing how I built my most powerful, yet simplest add-on using the Adobe Creative SDK.
Set up the HipChat JSON Schema in Visual Studio Code to make creating atlassian-connect.json files easier by using type ahead to suggest the keys available.
Here at Atlassian, we are big fans of Uber. So, a fewweeks ago, we took a crack at building an Uber integration inside HipChat.The best part...it only took us a few days to build!
Last month the HipChat Connect platform was announced at Summit. During the most recent ShipIt at Atlassian, a small team of us created a HipChat Connect add-on to bring customer NPS feedback into HipChat. Read on to see how simple it can be.
Have you heard about ChatOps? I had the pleasure of hosting a panel discussion on ChatOps during Atlassian Summit 2015. To learn from real-world examples, I interviewed Stevan Arychuk from New Relic, David Hayes from PagerDuty, and Raymond Chan from Twitter. The discussion covered how ChatOps grew up in the 3 organizations, the benefits and costs, and thoughts about the future of ChatOps. Read on for my summary observations from the panel.
At AtlasCamp 2015 we announced we were working on Atlassian Connect for HipChat. During a recent hackathon week in San Francisco we gave early access to 25 developers from awesome companies - including New Relic, PagerDuty, StatusPage.io, Tempo, Wittified, Meekan, Notify, and Zendesk - and the result was quite impressive!
If you are a Go programmer you know how easy it is to whip up an application
that speaks HTTP. Go was born for the task. So it will come as no surprise that
it's possible to create an Atlassian Connect for HipChat add-on with less than two hundred
lines of commented code. What will this code accomplish? A new custom command
/test_hook, installable on any channel you are administrator of:
Video conferencing systems are complex. They have evolved over the decades, along with hardware and software, to be much more accessible and affordable. But they are still complex and will remain to be so. In this post we will introduce our approach to one of the important problems – that of scaling the number of participants – and show how our solution also helps us to provide a better user experience.
We are proud to announce that the HipChat UI is now extensible for add-on developers. Powered by Atlassian Connect, you can now customise your HipChat experience by surfacing arbitrary HTML in modal dialogs.
In today's software markets it's increasingly important to be agile and have the ability to release fast and often. The recent release of the new HipChat web client shows us why in a neat example. In a recent blog post from our HipChat web engineers they detail the issues they saw when they brought their new architecture online for the first time at scale.
We love gifs on the HipChat team. We love them so much that we were temporarily misled by their sirens' call. Here's how we plugged our ears and continued on to the fabled land of SVG, optimizing our loading screen and reducing its size by 95%.
I got a request from an internal team to get notified when a new post on this blog goes live. It seemed like something one should be able to do without too much effort. So I set aside about an hour to figure something out and now I want to share what I came up with to solve this problem. This same method could be used to integrate almost any services easily, quickly, and without investments in infrastructure.