[twobyfour]

It's a well-populated space. If you're going to enter it, you need to be clear about differentiation.

We picked our CI solution because it was the only cloud offering we could find that supported Bitbucket and also allowed us to set up our own fully-custom environments to run against - without Docker.

Sadly, it took about a week's worth of research to figure that out. And I'm a bit concerned that in this crowded market they'll go out of business and leave us high and dry.

[rjbwork]

This sounds a lot like my requirements...can you tell me your CI provider?

[twobyfour]

https://buildkite.com

We migrated there from Bamboo Cloud when Atlassian discontinued it. It's nearly a direct drop-in replacement, and they even had docs specifically about Bamboo migrations. Their customer support during onboarding was also superb, and they've been responsive to feature requests. We've been using it for almost a year now, and overall we're pretty pleased.

What are you using currently?

[rjbwork]

I run an Azure VM hosted TeamCity/Octopus Deploy combo, with bitbucket for SCM.

[twobyfour]

Are you happy with that solution?

[rjbwork]

It's alright, I rarely have to touch it, but I'm no Sysadmin. If I had ops/sysadmin guys to shove onto, I would have no qualms using it long into the future.

I would, ideally, like a hosted build server, and a hosted Octopus - I really like it. Not the biggest fan of team city, but it works, and it's the only thing I know well.

[twobyfour]

Yeah, that's why we wanted a cloud solution - none of us really have significant sysadmin expertise, nor the time to devote to tending more boxes than we absolutely must. Only having to maintain the actual build environment has been a win.

We've had a couple occasions where we ran out of disk space (though not since we increased the disk size and added a cleanup job), and a few times a build agent has randomly stopped responding and needed to be restarted, but nothing we couldn't easily diagnose and fix.