11# container-images
2- Dockerfiles for building docker images
32
4- There is 1 subdirectory for every image to build.
3+ Dockerfiles and build contexts for building docker images
4+
5+ There is 1 subdirectory for every image to build. Dockerfiles and build
6+ contexts are generated from jinja2 templates in tpls directory. The images.py
7+ script generates the files, and can also be used to build docker images and to
8+ test them. To see more info do:
9+
10+ python images.py --help
511
612## testing
713
@@ -17,22 +23,26 @@ Will build every image. Look at the test for example command lines.
1723
1824## Publishing a new release
1925
20- * Change release name in images.py, and add it to tpls/tpl.README.md
21- * Update the READMEs and Dockerfiles for the individual images
26+ If we are publishing 2017.0.0 build number 2, then the docker image will have 3
27+ tags: 2017.0.0-2, 2017.0.0, latest. An automated build on docker hub is
28+ triggered by pushing a tag to this repo. The tag has the form 2017.0.0-2.
29+
30+ * Change update_number & build_number in images.py, and add it to tpls/tpl.README.md
31+ * Regenerate the READMEs and Dockerfiles for the individual images
2232
2333 python images.py --gen all
2434
2535* Commit changes
2636* Tag with the release name
2737
28- git tag -a 2017.0.0 -m 'new release'
38+ git tag -a 2017.0.0-2 -m '2017.0.0-2 release'
2939
3040* Push changes, this will trigger testing on travis-ci
3141
3242 git push
3343
3444* When travis-ci testing completes, push the tag
3545
36- git push origin 2017.0.0
46+ git push origin 2017.0.0-2
3747
3848* Check later that all builds have completed on docker hub
0 commit comments