summaryrefslogtreecommitdiffstats
path: root/.github/workflows
AgeCommit message (Collapse)Author
2019-11-28GitHub Actions: add branch name to docker image nameGravatar Dirk Hohndel
Unless we're on master. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-11-28GitHub Actions: better names for the docker workflowsGravatar Dirk Hohndel
This way it's much easier to see on the GitHub website which one is which. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-11-28GitHub Actions: set new version numbers for the docker imagesGravatar Dirk Hohndel
These are of course arbitrary. The Android container image for some reason based its version number on the Qt version. Which may or may not be a good idea. The other two had 0.x version numbers, so let's move them to 1.0 for the first release that gets pushed to the subsurface account on docker hub. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-11-28GitHub Actions: build stage 2 of MXE image for correct branchGravatar Dirk Hohndel
When triggered by a push event, the checkout action checks out the correct branch. But without this change, the stage 2 action would always run on master. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-11-28GitHub Actions: trigger docker builds on more pathsGravatar Dirk Hohndel
Not only a change to the docker file, also changes to the yaml files should trigger rebuilds. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-11-28GitHub Actions: push Linux and Android containers to docker hubGravatar Dirk Hohndel
For now simply using the existing version numbers. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-11-28GitHub Actions: add two stage MXE container buildGravatar Dirk Hohndel
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>
2019-11-28GitHub Actions: split the container build action into twoGravatar Dirk Hohndel
And remove the Windows/MXE one that doesn't work because of the 6h time limit. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-11-28GitHub Actions: let CI build docker imagesGravatar Anton Lundin
This create a GitHub Actions workflow to build the docker images we use in our CI workflows. Signed-off-by: Anton Lundin <glance@acc.umu.se>
2019-11-22GitHub Actions: don't add macOS artifacts to releaseGravatar Dirk Hohndel
We now get a working macOS DMG for each CICD release via the webhook - and the GitHub built .app.zip only worked on the latest macOS and was near-unusable there. We still make it available as an artifact of that macIS GitHub action in case there is some value, but we no longer push it into the GitHub release artifacts. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-11-18GitHub actions: fix macOS artifact uploadGravatar Dirk Hohndel
Previously this created a bogus Subsurface.app.zip.zip file and then failed to upload it to the release. The upload / download pair of default actions is happier with just the folder. And then the creation of the zip file needs the '-r' switch. Oops. Finally, the pull-request specific uploads as build artifact are completely redundant since we already do this to move the data from the macOS build to the container that runs our own publish action in the first place. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-27GitHub Actions: switch back to the GitHub artifacts for PRsGravatar Dirk Hohndel
transfer.sh has suddenly started to time out. And for the rather occasional need of having a binary to test from a PR, this should be good enough. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-26GitHub Actions: one more set of typos fixedGravatar Dirk Hohndel
I am at a loss for words. Especially as we didn't need those quotes in the first place. What was I thinking? Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-25GitHub Actions: fix several errors in previous commitsGravatar Dirk Hohndel
I have no excuse. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-25GitHub Actions: add apt-get update before installing curlGravatar Dirk Hohndel
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-25GitHub Actions: only build pushes into and PR against masterGravatar Dirk Hohndel
This should fix the odd double builds for people who create branches for pull requests in the main repository. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-25GitHub Actions: push to transfer.sh for PRs, post release for pushesGravatar Dirk Hohndel
This means that PRs from people using the main repo for their staging branches will get both transfer.sh and a release. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-25GitHub Actions: run them on pull requests as wellGravatar Dirk Hohndel
I wonder if this will cause issues where the actions sometimes run twice. But we'll deal with that rather than dealing with not having the tests on pull requests. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-23GitHub Actions: Add automatic coverity scanGravatar Anton Lundin
This adds a automatic coverity scan build based on linux-bionic-5.9.yml Signed-off-by: Anton Lundin <glance@acc.umu.se>
2019-10-19GitHub Action: add iOS buildGravatar Dirk Hohndel
This is incredibly brute force, downloading a 3+GB installer and installing all of the Qt/iOS binaries. This first attempt is mainly to get an idea how long this will take and if this will fit within the size constraints of the build VM. This commit doesn't even try to build, yet. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: add Linux Bionic / Qt 5.9 buildGravatar Dirk Hohndel
No artifacts from this build are preserved, this is just to make sure that we can still build the desktop version against Qt 5.9. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: add Android buildGravatar Dirk Hohndel
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: improve naming and location of filesGravatar Dirk Hohndel
Just to make things a little more consistent. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: post releasesGravatar Dirk Hohndel
This so far just works on push and hopefullt pull requests, not for tags and therefore actual releases. In order not to conflict with the binaries from Travis, I changed the name to "ci-release" instead of "continuous". Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-18GitHub Actions: build Windows binariesGravatar Dirk Hohndel
Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-16GitHub Actions: add Linux Qt 5.12 container buildGravatar Dirk Hohndel
The AppImage works - I just need to figure out how to post releases. For now it'a available on the Actions page as Artifact. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>
2019-10-14GitHub Actions: first CI/CD build for Mac based on GitHub ActionsGravatar Dirk Hohndel
This feature is in beta right now and might change without notice, but instead of dealing with the broken Travis Mac builds, this does seem progress. The build artifact seems to work, but it's a bit more painful to get to. Go to https://github.com/Subsurface-divelog/subsurface/actions and click on the corresponding run - it's then in the top right corner under Artifacts. The one oddity is that after unzipping the file you need to manually make Contents/MacOS/Subsurface executable. Signed-off-by: Dirk Hohndel <dirk@hohndel.org>