Change CI to use the version names in Docker images #57
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.
This, along with PR #49, completes issue #50.
Images are automatically built for any tag or branch with version names, e.g.,
0.3.0
or0.3.0-rc1
. In addition, all commits pushed to thedevel
branch with trigger an image build that will be published using versionlatest
.In both cases, two images are built:
alpha-automl:{version}
, which is a Jupyter notebook server that includes the examples from the repository.alpha-automl:{version}-jupyterhub
, which can be used as part of a custom JupyterHub deployment as documented in https://github.com/VIDA-NYU/alpha-automl/blob/devel/kubernetes/README.md.As an example branch
0.3.0-dockerbuild
creates the images:ghcr.io/vida-nyu/alpha-automl:0.3.0-dockerbuild
ghcr.io/vida-nyu/alpha-automl:0.3.0-dockerbuild-jupyterhub