Update GitHub Action workflow for CI #2970
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
theseanything
force-pushed
the
bulk/add-github-actions-ci
branch
from
2d2cc59 to
4c49bd7
Compare
theseanything
changed the title
marcpomfret
approved these changes
Jan 3, 2023
This updates the initial workflow to enable CI using GitHub Actions. It makes use of reusable workflows and composite actions defined in govuk-infrastructure. The CI workflow is initially only used to support deployments to the new EKS infrastructure and not to immediately replace the CI workflow in Jenkins. The CI workflow makes use of individual jobs to run each testing and linting tool. This allows the processes to run concurrently and improves the visibility of status in the GitHub UI. Most jobs make use of reusable workflows as they are consistent across the majority of our repositories - this allows us to easily maintain them in a single place. However, the test-ruby job (and/or integration-tests) is defined per repo as backing services and other dependencies vary greatly between repos. Backing services (such as databases) are created using a composite action instead of a job service. This is because they contain a lot of shared config and makes it easier for us to maintain.
theseanything
force-pushed
the
bulk/add-github-actions-ci
branch
from
4c49bd7 to
f0dfff2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This updates the initial workflow to enable CI using GitHub Actions. It makes use of
reusable workflows and composite actions defined in govuk-infrastructure. The
CI workflow is initially only used to support deployments to the new EKS
infrastructure and not to immediately replace the CI workflow in Jenkins.
The CI workflow makes use of individual jobs to run each testing and linting
tool. This allows the processes to run concurrently and improves the visibility
of status in the GitHub UI.
Most jobs make use of reusable workflows as they are consistent across the
majority of our repositories - this allows us to easily maintain them in a
single place. However, the test-ruby job (and/or integration-tests) is defined
per repo as backing services and other dependencies vary greatly between repos.
Backing services (such as databases) are created using a composite action
instead of a job service. This is because they contain a lot of shared config
and makes it easier for us to maintain.