Replacedocker-compose with docker compose as docker-compose will be unsupported at the end of June 2023 [link]
ubuntu-latest image comes standard with docker compose [link]
Remove the --parallel option from the docker compose build command as it is set in the docker compose command level (the official Docs says --parallel defaults to -1(unlimited) [link])
Change the set-output notation to use GITHUB_OUTPUT as set-output will cause an error after June 2023 [link] (but it's not accessed in subsequent processes, so may as well take it away)
Change to get UID and GID from the host image, since those numbers of GitHub Actions images are sometimes not 1000
Update the cache process for the Crux project specs to make it easier to work on it later
How to test
Fork this project
Raise the pull request from #14/chore/implement-ci to develop on the forked repository
Merge the pull request
Make a small change on the develop branch and commit it to the new branch
Raise the pull request from that new branch to develop
Open the Actions tab and check the CI works without any errors
Note for reviewers
I implemented the very basic cache features, but some problem still remains.
When the trigger is pull_request, a cache is attached to refs/pull/{pull_request_number}/merge, so the cache is valid for operations only on that pull request, not on the base branch or any other pull requests targeting that base branch [link]
Past caches are not deleted (the CI process triggered by the updates to the same pull request will successfully use the past cache, but a new cache will be created and do not overwrite the old one)
Running log for the 1st time
Running log for the 2nd time (successfully receive cache)
Issue URL
14
Change overview
docker-composewithdocker composeasdocker-composewill be unsupported at the end of June 2023 [link]ubuntu-latestimage comes standard withdocker compose[link]--paralleloption from thedocker compose buildcommand as it is set in thedocker composecommand level (the official Docs says--paralleldefaults to-1(unlimited) [link])set-outputnotation to useGITHUB_OUTPUTasset-outputwill cause an error after June 2023 [link] (but it's not accessed in subsequent processes, so may as well take it away)UIDandGIDfrom the host image, since those numbers of GitHub Actions images are sometimes not 1000How to test
#14/chore/implement-citodevelopon the forked repositorydevelopbranch and commit it to the new branchdevelopNote for reviewers
I implemented the very basic cache features, but some problem still remains.
pull_request, a cache is attached torefs/pull/{pull_request_number}/merge, so the cache is valid for operations only on that pull request, not on the base branch or any other pull requests targeting that base branch [link]