To this point our bulk_data tests have been run on a self-hosted instance of Jenkins. To replace this we have added a self-hosted Github Actions runner on dev03. The runner uses a popular image and a docker-compose.yml to create a container that is only connected to the pdp repo. The container uses an access token from the repo to ensure action requests are coming from the correct source. There are some warnings about using self-hosted runners in public repos. Upon doing some digging I have found the reason for the warning. Based on the comment from the Github associate I believe we are safe from the vulnerability given that none of our actions (in this repo) rely on PRs to trigger them. The docker-compose we use mounts the data volumes needed to run the full test suite. There was only one test that had to be removed which you will see below (any suggestions to reintroduce it are welcome). The only relevant changes in the README are at the top, the rest are whitespace fixes made by atom automatically (sorry about the mess).
To this point our
bulk_datatests have been run on a self-hosted instance ofJenkins. To replace this we have added a self-hosted Github Actions runner ondev03. The runner uses a popular image and adocker-compose.ymlto create a container that is only connected to thepdprepo. The container uses an access token from the repo to ensure action requests are coming from the correct source. There are some warnings about using self-hosted runners in public repos. Upon doing some digging I have found the reason for the warning. Based on the comment from the Github associate I believe we are safe from the vulnerability given that none of our actions (in this repo) rely on PRs to trigger them. Thedocker-composewe use mounts the data volumes needed to run the full test suite. There was only one test that had to be removed which you will see below (any suggestions to reintroduce it are welcome). The only relevant changes in theREADMEare at the top, the rest are whitespace fixes made byatomautomatically (sorry about the mess).Resolves #205.