summaryrefslogtreecommitdiffstats
path: root/scripts/get-version
diff options
context:
space:
mode:
authorGravatar Dirk Hohndel <dirk@hohndel.org>2019-11-24 13:35:09 -0800
committerGravatar Dirk Hohndel <dirk@hohndel.org>2019-11-28 11:12:59 -0800
commit8c641402207dcee2f17de6f18c463a40b6434847 (patch)
tree9bc8bbe2256b3dceea0a9706ebce0beec5e2718e /scripts/get-version
parent311eb9a2e3e4959eb53a2a7bcebd46aaa03e8829 (diff)
downloadsubsurface-8c641402207dcee2f17de6f18c463a40b6434847.tar.gz
GitHub Actions: add two stage MXE container build
Based on ideas from Anton - both the basic building of containers in the first place as well as the workaround for the 6h build limit. Because GitHub Actions are limited to 6 hours we split the creation of the MXE container into two steps and push the intermediary container after stage 1 to docker hub. Right now each of the steps takes about 3.5 hours, so hopefully even with changes in the future this will continue to work. This commit also introduces use of docker hub instead of GitHub's own registry (since strangely right now GitHub actions cannot run containers from GitHub's private registry). In order for this to work, we need to have the docker credentials in secrets in GitHub. As a result, only people who can create branches in our repository can easily test changes to the container images. Others can modify the code to use a different docker hub account and provide those secrets in their own GitHub account. Not ideal, but of course we cannot allow every pull request to potentially overwrite docker images in our "official" docker hub account. Suggested-by: Anton Lundin <glance@acc.umu.se> Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
Diffstat (limited to 'scripts/get-version')
0 files changed, 0 insertions, 0 deletions