New Workflows
Updates all current workflows to be aligned closer to boreholes' DevOps suite.
CodeQL remains as is.
Code Quality runs whenever a Pull Request is created or changed. It ensures that the code within the PR is up to standard and fully operational.
Publish Edge runs whenever develop is pushed to. It builds a new Docker image for both app and api and tags it with edge. It also generates a development version tag based formatted like X.X.X-devX, which ensures that the image is addressable even if edge is moved to a newer image.
Publish Release Candidate runs whenever main is pushed to. It adds the release-candidate tag to the current edge images.
Relase has to be run manually. It builds release versions of the current release-candidate images, and tags it with a new release version formatted like X.X.X. It also adds the tags edge, release-candidate and latest to these images. It then removes any now-outdated tags and images.
Publish Edge and Publish Release Candidate may also be started manually. This allows for more fine-grained releases, which can be helpful for hotfixes and cross-version jumps.
Version in Images
The images built by the workflows now contain the APP_VERSION, which holds the application's version number (e.g. 1.2.3-dev4).
Please add the label 1.0.0 to the current main branch before merging this.
The workflows require a previous version to be present in order to be able to generate the new one.
Resolves #123. Depends on #137.
New Workflows Updates all current workflows to be aligned closer to boreholes' DevOps suite.
CodeQLremains as is.Code Qualityruns whenever a Pull Request is created or changed. It ensures that the code within the PR is up to standard and fully operational.Publish Edgeruns wheneverdevelopis pushed to. It builds a new Docker image for bothappandapiand tags it withedge. It also generates a development version tag based formatted likeX.X.X-devX, which ensures that the image is addressable even ifedgeis moved to a newer image.Publish Release Candidateruns whenevermainis pushed to. It adds therelease-candidatetag to the currentedgeimages.Relasehas to be run manually. It builds release versions of the currentrelease-candidateimages, and tags it with a new release version formatted likeX.X.X. It also adds the tagsedge,release-candidateandlatestto these images. It then removes any now-outdated tags and images.Publish EdgeandPublish Release Candidatemay also be started manually. This allows for more fine-grained releases, which can be helpful for hotfixes and cross-version jumps.Version in Images The images built by the workflows now contain the
APP_VERSION, which holds the application's version number (e.g.1.2.3-dev4).Please add the label
1.0.0to the currentmainbranch before merging this.The workflows require a previous version to be present in order to be able to generate the new one.