Two popular CI services have just implemented Flowdock integrations: Semaphore & TravisCI. Flowdock goes great together with continuous integration apps. That way the whole team can take responsibility of the state of the build. Previously, Flowdock has CI integrations for CircleCI, Bamboo, CruiseControl and Jenkins.
Special thanks to Phil Cohen for implementing the Travis CI integration.
We have often been asked about how GitHub Issues content could be aggregated in Flowdock. This wasn’t really possible until a few weeks ago as GitHub added event hooks to pretty much everything.
Issues, pull requests, wiki updates, and comments are now pushed to Flowdock in addition to commits. We have been using them ourselves, and it has significantly reduced the time it takes to react to a pull request.
The configuration can be a bit of work until GitHub gets its revamped hooks admin out. If you have an existing Flowdock hook in your GitHub repo, you have to poke the GitHub API a bit.
Configuring new hooks don’t require anything special. Just follow the instructions from our help page and you’re done.
Hubot, Github‘s awesome chat bot was open-sourced a couple weeks ago. That’s when we jumped in and made it talk with Flowdock. Hubot has some pretty cool abilities. To get your very own Flowdock Hubot:
Among the built-in abilities are:
See the rest by saying “hubot help”. There’s tons more you can add yourself in the hubot-scripts repository.
These features also make use of our new link preview feature (currently works with images, YouTube, Google Maps and tweets).
Hubot can do much more than incite a laugh or two. For example, one of our users, Christopher Castle, has implemented a JIRA issue fetcher, which allows Hubot to list and search JIRA issues assigned to you.
Similar functionality for Pivotal Tracker has been implemented as well, get it here.
Flowdock functions as the center of your work conversation, so it makes sense to receive notifications of your work to Flowdock. If you are a software development team, it’s a no-brainer to want notifications from your version control to pop into your Flowdock flow. Flowdock is now fully integrated with Git and GitHub.
To receive notifications from your GitHub repository to your Flowdock flow, follow these simple steps:
button.
To test the integration, click Flowdock again from the hooks list on GitHub and click the now showing Test Hook button. Now you’re all set and receiving notifications from GitHub!
If you need several flows to be notified about commits in one repository, go to the Post-Receive URLs section of the Available Service Hooks list and add one entry for each flow in the following form:
https://api.flowdock.com/v1/git/YOURAPITOKENHERE_
We also support privately hosted Git repositories, but you’ll have to grab our post-receive hook.
curl -o hooks/post-receive https://github.com/nodeta/post-receive-http/raw/master/post-receive chmod +x hooks/post-receive git config httphook.url https://api.flowdock.com/v1/git git config httphook.token _YOUR_API_TOKEN_HERE_
That’s it, you’re all set with your git repos!
Check out more stuff about integrating your tools with Flowdock at our support section for agile software developers.
