I feel dirty for saying this but Azure Pipelines is the service that is tempting to me because of the power of its file format (variable substitution, conditionals, template tasks and steps).
It's very "power user" in that it's easy to get lost amongst all the options, but nothing else I've tried has the same breadth of OSes and ability to have one job depend on another in intricate ways. And, 10 free parallel builds, including macOS!
I’m quite liking azure for now and most of my company’s foss projects run there. But. Reason for getting lost is abysmally bad documentation. Yeah, all that I need is there but it’s structured so so bad.
Also, hosted agents have small inconsistencies that make the pipeline to have ton of do this on Linux but not in OS X or windows and so forth...
No need to feel bad, it's a great product! I've been using Azure DevOps for a while now, and it's what I use for anything not OSS (I prefer GitHub for that, and TBH it's what others expect)
It's also interesting how much Open Source is moving to Pipelines for just build services, regardless of where their code is hosted. The Python setup on Pipelines is really cool to dig into if you get the chance. I believe Python has been using it as the primary CI for their GitHub repo for bit now, and from what I've heard they've looked into using Pipelines to support a test matrix nearly as robust as their older BuildBot config.
Curious if anyone has used Azure Pipelies with Rails projects and has a review.
(Yeah, I know, all these CI things are hypothetically platform agnostic, but then there's reality, different platforms-under-test have different sorts of problems which become priorities for the CI platform to smooth out and make just work, or don't).
I think that you want somebody who's unbiased to answer this from their perspective (I'm a PM for Azure DevOps, so I'm pretty biased). But I've built out Azure Pipelines for many platforms, including Ruby and RoR with a lot of success. Feel free to drop me an email (my HN username @microsoft.com) and I can point you to some pipelines.
Cool. The trick is, I don't want to "build out a pipeline", I just wanna write a handful of lines in a single config file and be up and going, which is what travis has given me.
Haha, yes, sorry for making it sound bigger than it is. If you just want to do some build & test validation, it should just be a single yaml file. Not identical to Travis but close. We even added some getting started documentation if you’re familiar with Travis. https://docs.microsoft.com/azure/devops/pipelines/migrate/fr...
