As a previously fairly (but not completely) satisfied user of Atlassian’s Bamboo Cloud product, I was upset (like many others) to find out that it was being sun-setted. But they’ve got a new product to replace it – BitBucket Pipelines, currently in beta. So I gave it a try.
For those who can’t be bothered to read below the fold: don’t bother checking it out.
Pipelines, as I’ll call it here, isn’t a Bamboo replacement. My understanding of this sort of thing is that it’s meant to be more streamlined than a standard build environment – it’s part of a “pipeline” into deployment. So I don’t expect it to be able to handle a complex build.
There are things I would like. I would like to get reports of failed tests without having to trawl through a Maven log. I would like to be able to have build artefacts that I can look at, and possibly reference from other builds. I would like to have an actual pipeline, where I could, say, build & validate, then deploy to a test environment, before promoting to production. But hey, maybe those are coming, or maybe they aren’t part of the newfangled continuous-delivery process Atlassian is pushing.
But… I can’t believe they don’t include notifications of failed builds. This is a bare minimum feature that they should never have entered Alpha, let alone Beta status, without. The very least a build system needs to do is let you know “Did it build okay?”. And they don’t have it.
Fancy notifications – Jabber/Twitter/HipChat/carrier pigeon – they don’t hurt to have (though the pigeons can make a bit of a mess), but they aren’t essential. But you can’t get away without offering email notifications of failed builds.
I personally doubt that this product will suit my needs when finished – I don’t think it’s intended to. But I can’t trust a product where the Goal Donors leave simple “failed build notifications” out of the system. Atlassian are obviously not dog-fooding this tool, which means it’s going to taste worse than dog-food.