Microsoft’s Azure DevOps: An Unsatisfying Adventure

All the individual problems, such as incomplete Github integration (which they now own, by the way), to the way agents running builds randomly die, to the way it’s the year 2019 and they still don’t offer any form of build caching, combine to create a product that is disappointingly subpar in comparison to other tools such as GitLab, CircleCI, Travis, and others. My secondary hope is to reach someone at Microsoft who makes decisions and convince them to fix these problems ASAP —we are, after all, paying them money for this tool and also paying for every additional agent we [attempt to] use for CI. It’s extremely confusing to me that Microsoft, a company which owns their own cloud services, lacks caching in their CI implementation. Another interesting implementation issue with CI is the communication (or lack thereof) with Github.

Source: toxicbakery.github.io