search

guardian / membership-frontend

Guardian events and masterclasses
https://membership.theguardian.com/
33 stars 19 forks source link

Migrate membership-frontend from TeamCity to Github Actions. #2489

Closed LAKSHMIRPILLAI closed 1 year ago

LAKSHMIRPILLAI commented 1 year ago

Why are you doing this?

Migrate membership-frontend from TeamCity to Github Actions.

Trello card: Here

DevX is planning to retire TeamCity by the end of September 2023. All workflows will need to be migrated to Github Actions

The TeamCity agent count will be continually decreasing from June onwards, reaching 0 by the end of September. So the build queues and therefore the time it takes to be able to deploy might increase, if the job count does not decrease. ‌ You should not use TeamCity for any new applications from now on. Our main build service is now GitHub Actions. GitHub Actions documentation - GitHub Docs

We will all benefit from this move by being able to keep our CI builds as code, version controlled alongside its codebase, and having a reduced number of tools and access, all bundled under one vendor, with better analytics through CloudQuery and Grafana. ‌ Furthermore, this change will help improve our resilience to supply chain threats particularly in the build process. ‌ More detailed reasoning can be found in this proposal Using GitHub Actions for CI

prout-bot commented 1 year ago

Seen on PROD (merged by @LAKSHMIRPILLAI 8 minutes and 43 seconds ago) Please check your changes!

Sentry Release: membership, membership-client-side