mirror of
https://github.com/jupyter/docker-stacks.git
synced 2025-10-15 22:12:57 +00:00
Notes, fixes from releasing a new stack
First time we've added a stack under the new versioning scheme (c) Copyright IBM Corp. 2016
This commit is contained in:
6
Makefile
6
Makefile
@@ -41,7 +41,8 @@ push/%:
|
||||
docker push $(OWNER)/$(notdir $@):$(GIT_MASTER_HEAD_SHA)
|
||||
|
||||
refresh/%:
|
||||
docker pull $(OWNER)/$(notdir $@):latest
|
||||
# skip if error: a stack might not be on dockerhub yet
|
||||
-docker pull $(OWNER)/$(notdir $@):latest
|
||||
|
||||
release-all: environment-check \
|
||||
$(patsubst %,refresh/%, $(ALL_STACKS)) \
|
||||
@@ -50,4 +51,5 @@ release-all: environment-check \
|
||||
$(patsubst %,push/%, $(ALL_STACKS))
|
||||
|
||||
tag/%:
|
||||
docker tag $(OWNER)/$(notdir $@):latest $(OWNER)/$(notdir $@):$(GIT_MASTER_HEAD_SHA)
|
||||
# always tag the latest build with the git sha
|
||||
docker tag -f $(OWNER)/$(notdir $@):latest $(OWNER)/$(notdir $@):$(GIT_MASTER_HEAD_SHA)
|
||||
|
@@ -64,3 +64,9 @@ make release-all DARGS=--no-cache
|
||||
```
|
||||
|
||||
This will take time as the entire set of stacks will rebuild.
|
||||
|
||||
When there's a new stack, do the following **before** trying to `make release-all`:
|
||||
|
||||
1. Create a new repo in the `jupyter` org on Docker Hub named after the stack folder in the git repo.
|
||||
2. Grant the `stacks` team permission to write to the repo.
|
||||
3. Copy/paste the short and long descriptions from one of the other docker-stacks repos on Docker Hub. Modify the appropriate values.
|
Reference in New Issue
Block a user