Five New Supported Tools for Ship
Early Access support in Ship for CircleCI, Netlify, AWS CodePipeline, Azure DevOps Pipelines, and Semaphore CI, providing cross-tool build monitoring
A couple of months ago I wrote about Ship - a new app that we’re building with some colleagues. I use Ship daily to keep track of activity in various projects. Instead of having a noisy set of Slack channels, I have one small app that gathers together all the status and updates of the builds and pipelines that I’m involved in. I know I’m biased, but I find Ship incredibly useful!
Ship initially just supported GitHub Actions, but we knew that many people were using other tools.
So today I’m happy to announce Early Access support in Ship for many more automation tools:
- AWS CodePipeline
- Azure DevOps Pipelines
We’re calling this support “early access” since the setup process requires a manual step on our side, and also because we’d like to get some feedback from folks on how we could improve these integrations. That said they are all in active use, either by us, or by some friends of ours.
How these new integrations help you
All of these automation tools out-of-the-box provide visibility and notification features. Some of them do this fairly well, but none of them provide what we think is a complete story when it comes to build monitoring.
Here are some reasons why I think Ship’s new integrations will help your organizations.
Firstly you get all the good stuff that we already had for GitHub Actions:
- Realtime desktop notifications
- Filterable cross-project activity monitoring
- At-a-glance status from the menu bar
- Team co-ordination for workflow failures
- Broadcast announcements
- Discussion-oriented Slack integration (not just a firehose of announcements)
What you also now get with Ship is a cross-tool unified monitor across all of your builds and pipelines.
For example, for developing Ship itself we use Netlify for deploying our website, and GitHub Actions for our CD automation. Now I get notifications and status for both tools piped to my desktop, rather than having to go to each tool’s website in turn.
That’s already useful for me as an engineer. However I know from my previous experience as a manager & CTO that being able to see all status in one place, even including those few projects using a very old tool, or a brand new one, is very valuable.
Instructions for all of these integrations are available at the following links:
If have questions, just drop us a line - we’d love to hear what’s on your mind.