Skip to content

Add CI GitHub Actions workflow#1859

Draft
theseanything wants to merge 3 commits intomainfrom
theseanything/parallelise-ci
Draft

Add CI GitHub Actions workflow#1859
theseanything wants to merge 3 commits intomainfrom
theseanything/parallelise-ci

Conversation

@theseanything
Copy link
Contributor

@theseanything theseanything commented Jan 23, 2026

Replace the build_and_test and docker_build workflows with a single ci workflow. Each CI process now runs as an independent job, so checks execute in parallel and report failures individually in PR status checks.

This improves developer feedback by showing all failing CI areas at once (instead of masking later failures when an earlier step fails), and should reduce total CI runtime.

@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@theseanything theseanything force-pushed the theseanything/parallelise-ci branch 9 times, most recently from 77e87db to 13dc9f4 Compare January 23, 2026 14:19
@sonarqubecloud
Copy link

@theseanything theseanything force-pushed the theseanything/parallelise-ci branch 4 times, most recently from 6227db5 to e2febab Compare February 26, 2026 13:48
This allows these commands to be executed seperately, needed if we want
to run these task as seperate job in GitHub Actions.
As part of parallelising CI into multiple jobs, abstracts these
multistep proccesses into into a single step, making them easier to
reuse.
Replace the `build_and_test` and `docker_build` workflows with a single
`ci` workflow.  Each CI process now runs as an independent job, so
checks execute in parallel and report failures individually in PR status
checks.

This improves developer feedback by showing all failing CI areas at once
(instead of masking later failures when an earlier step fails), and
should reduce total CI runtime.
@theseanything theseanything force-pushed the theseanything/parallelise-ci branch from ac63ce8 to 088d2c1 Compare February 26, 2026 14:08
@sonarqubecloud
Copy link

@theseanything theseanything changed the title [WIP] Test parallelise CI Add CI GitHub Actions workflow Feb 26, 2026
@github-actions
Copy link
Contributor

🎉 A review copy of this PR has been deployed! It is made of up two components

  1. A review copy of forms-runner
  2. A production copy of forms-admin

Important

Not all of the functionality of forms-runner is present in review apps.
Functionality such as sending emails, file upload, and S3 submission types are
deliberately disabled for the sake of simplifying review apps.

You should use the full dev environment to test the functionality which is disabled here.

It may take 5 minutes or so for the application to be fully deployed and working. If it still isn't ready
after 5 minutes, there may be something wrong with the ECS task. You will need to go to the integration AWS account
to debug, or otherwise ask an infrastructure person.

For the sign in details and more information, see the review apps wiki page.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant