@@ -23,35 +23,30 @@ Will build every image. Look at the test for example command lines.
2323* See images.py for directions on adding a new configuration
2424* create a new automated build on docker hub, copying build setting of existing image
2525
26- ## Publishing a new release
26+ ## Publishing a new release (Internal Use Only)
27+
28+ Disclaimer: Do NOT do this unless all packages for upcoming release have been
29+ uploaded to Intel channel on Anaconda Cloud. Best time to do this is right before
30+ FCS when all packages have automatically been uploaded and validated.
2731
2832If we are publishing 2017.0.0 build number 2, then the docker image will have 3
29- tags: 2017.0.0-2, 2017.0.0, latest. An automated build on docker hub is
30- triggered by pushing a tag to this repo. The tag has the form 2017.0.0-2.
33+ tags: 2017.0.0-2, 2017.0.0, latest. Github Actions will create a Docker image
34+ after a PR is merged. The following steps are all that is needed to update our
35+ Dockerhub with our latest IntelPython.
3136
32- * Change update_number & build_number in images.py, and add it to tpls/tpl.README.md. Build number is the third argument in all_confs
33- * Regenerate the READMEs and Dockerfiles for the individual images
37+ * Change update_number & build_number in images.py. Most of the time, the build number
38+ remains the same (#0 ) and the minor version is incremented (e.g. 2021.1.0 -> 2021.2.0)
39+ * Regenerate the READMEs and Dockerfiles for the individual images by running the following
40+ command
3441
3542 python images.py --gen all
3643
37- * Commit changes
44+ * Create branch and commit changes
3845* Tag with the release name
3946
40- git tag -a 2017.0.0-2 -m '2017.0.0-2 release'
41- git push
42- git push origin 2017.0.0-2
43-
44- * Check later that all builds have completed on docker hub
45-
46- ## dockerhub config
47-
48- We use the dockerhub autotesting to test every pull request. When you
49- push a tag, it will build, test, and publish a new container with a
50- corresponding tag.
51-
52- Dockerhub build rule:
47+ git tag -a 2022.0.0-0 -m '2022.0.0-0 release'
48+ git push origin update/2022.0.0-0
49+ git push origin 2022.0.0-0
5350
54- source type: tag
55- source: /.* /
56- docker tag {sourceref}
57- dockerfile location: configs/intelpython2_core
51+ * Create PR, check that tests pass, and then merge PR. Github actions has been setup to
52+ automatically build the Docker image and push it to Dockerhub afterwards.
0 commit comments