[kapilvt]

As a maintainer on an opensource project thats recently switched out to azure pipelines, I'm actually overall happy with azure pipelines, its considerably faster (hosted agent) for us in matrix builds then travis both on latency to start a build and actual compute power, and cheaper then self hosted drone. Hosted builds have been reliable for us, we notice a hiccup less than once a month on a single build (avg 20+ builds a day), minus a service incident yesterday.

That said I agree with a lot of the criticisms noted here (no retrigger on web hooks to update status, complicated web ui, log ux, lack build cache). It is possible to bring your own cache implementation, I just stuffed/restored things into object storage, also filed an issue for build cache https://github.com/Microsoft/azure-pipelines-tasks/issues/91... noting several other closed issues for the same.

It does feel like the platform is moving forward. All that said there's a lot of complexity and feature set in azure DevOps and pipelines that I haven't explored and try to ignore in the ui. At the moment its the only cloud provider build solution that actually even attempts to work well for opensource projects afaics.

[edglas]

Thanks @kapilvt, I'm on the Azure DevOps engineering team. Are there specific improvements you'd like to see in the logs UX?