[markcubed]

While I certainly have had a few annoying issues myself, full credit to the team behind DevOps (nee VSTS) for doing an amazing job over the last >12 months to overhaul and improve the product. I have been impressed at the pace things are improving.

I have not had the same issues with build machines disappearing into the ether (we use Windows hosts however) but definitely agree that the (lack of) caching is maddening. Our apps are not huge but the NuGet & npm restore times now account for 25-30% of our build time.

[avinium]

Yeah, this has been my experience.

I haven't had a build agent disappear, but lack of build caching is very frustrating. The hosted build agents are slow to begin with, let alone needing 5 minutes for every build to restore packages.

AFAIK there's no way to "only run changed tests" too.

EDIT: Forgot to add that, despite the above, I'm pretty happy with it. The whole VSTS experience (Wiki/code/PRs/etc) is pretty great, it's nice to have everything in a single place.

[taspeotis]

> AFAIK there's no way to "only run changed tests" too.

https://docs.microsoft.com/en-us/azure/devops/pipelines/test...

[avinium]

That looks great - must have overlooked that last time I checked.

[taspeotis]

I exchanged an email with the Product Manager of some Azure DevOps component that comprises the build pipelines. They’re well aware of the need for caching. Hopefully it comes soon!

[GordonS]

Unfortunately, they've been aware of this problem for years - I'm an Azure DevOps fan, but I really just don't understand why they didn't fix this an age ago :/

[ethomson]

Thanks for the kind words; I agree that caching is a problem. We're working on it now.

[cbHXBY1D]

Any idea on when it will land?

I'm on a team at building a C++ component and just installing boost can take over 20 minutes for a build.