Paul Cochrane 🇪🇺Mar 25, 2024

Trying to get an old #rakulang project up and running again led me down a deep rabbit hole. I ended up working out how to set up, build, and test #rakulang projects on #Windows with the #AppVeyor #CI platform. These notes are a guide to help anyone wanting to create an AppVeyor configuration in the future.

https://peateasea.de/building-and-testing-raku-in-appveyor/

Building and testing Raku in AppVeyor

Trying to get an old Raku project up and running again led me down a deep rabbit hole. I ended up working out how to set up, build, and test Raku projects on Windows with the AppVeyor CI platform. These notes are a guide to help anyone wanting to create an AppVeyor configuration in the future.

P.T.C.
Miha MarkičDec 1, 2023
#appveyor does not yet support .NET 8 build image AFAIK.
Show threadHugo van KemenadeOct 31, 2023

And the last two releases saw GHA/AP improve their lead:

2022: Python 3.11

🥇 a day: @github Actions ↔️
🥈 2 days: Azure Pipelines ↔️
🥉 14 days: AppVeyor ↔️
4️⃣ 28 days: Travis CI ↔️

2023: Python 3.12

🥇 13 hours: @github Actions ↔️
🥇 13 hours: Azure Pipelines ↔️
🥉 20 days: Travis CI ⬆️
4️⃣ 28 days: AppVeyor ⬇️

And GitHub Actions already has 3.13 alpha available!

#Python #CI #CImedals #medals #GitHubActions #AzurePipelines #TravisCI #AppVeyor #Python311 #Python312 #Python313

Show threadJustin DearingAug 17, 2023

@jsbarretto it's sort of the opposite for me. My "great benefits to society have probably been OSS contributions, but definitely stuff I only did because of the day job. Contributing to csv libraries, logging libraries, documenting something in #appveyor that the author didn't know, Microsoft documentation, etc. And a few stackoverflow questions and answers.

More people have been impacted by all that than all the things I did for fortune 500 companies

David Cantrell 🏏Feb 3, 2023
Just migrated 40-ish git repos to use #GithubActions for testing on Windows instead of #Appveyor. Each push will have triggered 20-ish builds. Oops. And on 50-ish repos I had to tweak the MacOS build. Again, each push will have triggered 20-ish builds. And now my builds are being rate-limited. Outrageous! I demand a refund!
Hugo van KemenadeNov 22, 2022

From release to support

2019: #Python 3.8

🥇 21 hours: #TravisCI
🥈 20 days: #GitHubActions
🥉 24 days: #AzurePipelines
4️⃣ 25 days: #AppVeyor

2020: Python 3.9

🥇 17 hours: GitHub Actions ⬆️
🥈 20 days: Travis CI ⬇️
🥉 21 days: AppVeyor ⬆️
4️⃣ 22 days: Azure Pipelines ⬇️

2021: Python 3.10

🥇 12 hours: GitHub Actions ↔️
🥈 17 days: Azure Pipelines ⬆️
🥉 28 days: AppVeyor ↔️
4️⃣ 106 days: Travis ⬇️

2022: Python 3.11

🥇 a day: GitHub Actions ↔️
🥈 2 days: Azure Pipelines ↔️
🥉 14 days: AppVeyor ↔️
4️⃣ 28 days: Travis ↔️

vtJun 7, 2019

Скачал вот эту срань поглядеть — appveyor.com
Закончилось тем, что на скриншоте. Удалил вирос этот сразу.

#говно #appveyor
Getting started with AppVeyor Server

#1 Continuous Delivery service for Windows

Romain TartièreJan 11, 2019

#TIL when you contribute to a project that use #Appveyor CI to test build on #Windows, the system sometimes build the code you have just pushed, but often a previous version of the code (in spite of what the commit hash say).

It can therefore be convenient to output canaries in the build script so that you can ensure success / failures are related to the last version of the code (by checking them visually in the log).

When it does not match:
git commit --amend
git push -f