Hi Ævar, On Fri, 17 Dec 2021, Ævar Arnfjörð Bjarmason wrote: > Remove various code required to support Azure CI. Recently in > 4a6e4b96026 (CI: remove Travis CI support, 2021-11-23) we removed the > Travis CI support, which was last used in June 2021. > > The supporting infrastructure for Azure CI was already partially > removed in 6081d3898fe (ci: retire the Azure Pipelines definition, > 2020-04-11). As that commit notes: > > We have GitHub Actions now. Running the same builds and tests in Azure > Pipelines would be redundant, and a waste of energy. > > This follow-up removes the relevant Azure Pipelines-only supporting > code. Most of it was added in commits merged as part of > 57cbc53d3e0 (Merge branch 'js/vsts-ci', 2019-02-06). It feels premature to remove the remnants of Azure Pipelines support already now. It would be better to hold off a little, as much fun as deleting and refactoring code may be for some of us. The reason is that there are still some things that Azure Pipelines can do that GitHub workflows cannot, for example: - present the logs of failed tests in an intuitive manner, - re-run _only_ failed jobs. At this stage, I am not convinced yet that we should bet completely on GitHub workflows. Ciao, Johannes
