cleaning up and improving the CI/CD pipeline #1122
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've cleaned up the CD pipeline a little.
The docker build is now a two-step build. The label passing might need some more testing though.
The CI runs on all pushes. If the tag starts with
v
it's a new version - and by that definition a new release. Note: Until now the version numbers were just numbers0.2019.413
. It would be good if we could switch to thev
prefix. So a new release could be for examplev0.2021.001
.The tag will create a new github release, which in turn trigger all the release distribution workflows.
For now that's npm and dockerhub. It's easy to add more.