Over the course of the past two quarters, we have slowly moved ETS projects from using Travis CI and Appveyor CI to also using GitHub Actions CI. The end goal here was to move away from Travis CI but because GitHub Actions CI also makes it possible to test on Windows, we should be able to move away from Appveyor CI as well.
Some ETS projects have already moved away from both Travis and Appveyor CI but in some cases, Appveyor CI is still used. This needs to be audited and rectified.
Over the course of the past two quarters, we have slowly moved ETS projects from using Travis CI and Appveyor CI to also using GitHub Actions CI. The end goal here was to move away from Travis CI but because GitHub Actions CI also makes it possible to test on Windows, we should be able to move away from Appveyor CI as well.
Some ETS projects have already moved away from both Travis and Appveyor CI but in some cases, Appveyor CI is still used. This needs to be audited and rectified.