Build with GHA

[Georges-GNM]

What does this change?

Adopts GitHub Actions for CI, replacing TeamCity, and using actions riff raff instead of sbt riffraff artifact.

As workflow-frontend relied on a buildInfo provided by sbt riffraff artifact for prout's checks, this PR also adapts some of the logic used for this, following the example in this implementation,

How to test

This branch has been built through GHA and successfully deployed to the code stage, which seems to be working as normal.

How can we measure success/mitigate risks?

Prod gets deployed successfully and workflow continues working. Any issues with the deployment should end up getting rolled back automatically.

Rollout

• Pause the TeamCity build
• Merge this PR
• Adjust branch protection rules, requiring the GHA build to pass before merge
• Ensure all open PRs are rebased against main to ensure their build runs

[twrichards]

LGTM - couple of suggestions though

Just to confirm, does BuildInfo automatically pick-up the environment variable BUILD_NUMBER (whereas it was explicitly passed before)?

[twrichards]

not for this PR, but looking forward to when we move to devx-logs (https://trello.com/c/P8JrJLHR/1345-use-devx-logs-for-workflow-frontend)

[Georges-GNM]

LGTM - couple of suggestions though

Just to confirm, does BuildInfo automatically pick-up the environment variable BUILD_NUMBER (whereas it was explicitly passed before)?

Thanks - have revisited the build steps and clarified/split them up a bit.

In terms of the buildinfo stuff - as I understand it, this is so that Prout can check the commitId which gets surfaced in a couple of html files. With this implementation, that should still be happening - the build should get a gitCommitId from the github_sha here. It won't look at the specific number of the build, but prout should still be happy (based on a similar implementation here)

Edit: huh, don't think I've seen a review get "dismissed" from a push before...

[prout-bot]

Seen on WORKFLOW_PROD (merged by @Georges-GNM 7 minutes and 36 seconds ago) Please check your changes!