This is the first stage of migrating CI to GitHub Actions. The goal for the CI overall is to compile scala via the update script and run the test script upon merge to develop. Eventually this will integrate with a GitFlow release process.
The server script, when run on its own, will run indefinitely within CI if not ran as a background process. Simply running the script with an & appended at the end will still produce output, which prevents it from running as a background process: instead, it would be a suspended background process. Redirecting output and error to an output file (>gh_output.txt 2>&1) allows for it to correctly run as a background process but then raises the issue of not providing insights into possible failures. Line 9 of the citest script can be uncommented in order to review the output/errors of running the server script.
As AWS login is needed for the server script to run successfully, repository secrets for AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, and AWS_REGION have been created within the repo. These correspond to the AWS access key and secret access key for the github-actions AWS user. This information is stored in 1Password under the DataHub GitHub User Access entry.
CHANGELOG.md will be updated when ready to merge in order to prevent possible merge conflicts.
Testing Instructions
[x] Create a test/* branch off of this branch and push up to GitHub; confirm GHA runs and completes successfully.
[x] Create a initials/* branch off this branch and push up to GitHub; confirm GHA does NOT run.
Overview
This is the first stage of migrating CI to GitHub Actions. The goal for the CI overall is to compile scala via the update script and run the test script upon merge to develop. Eventually this will integrate with a GitFlow release process.
Connects #97
Demo
Notes
serverscript, when run on its own, will run indefinitely within CI if not ran as a background process. Simply running the script with an&appended at the end will still produce output, which prevents it from running as a background process: instead, it would be a suspended background process. Redirecting output and error to an output file (>gh_output.txt 2>&1) allows for it to correctly run as a background process but then raises the issue of not providing insights into possible failures. Line 9 of thecitestscript can be uncommented in order to review the output/errors of running theserverscript.serverscript to run successfully, repository secrets forAWS_ACCESS_KEY_ID,AWS_SECRET_ACCESS_KEY, andAWS_REGIONhave been created within the repo. These correspond to the AWS access key and secret access key for thegithub-actionsAWS user. This information is stored in 1Password under theDataHub GitHub User Accessentry.CHANGELOG.mdwill be updated when ready to merge in order to prevent possible merge conflicts.Testing Instructions
test/*branch off of this branch and push up to GitHub; confirm GHA runs and completes successfully.initials/*branch off this branch and push up to GitHub; confirm GHA does NOT run.