-
Task
-
Resolution: Won't Do
-
Normal
-
None
-
None
Until now, we haven't had a concrete tag to point at for releases to developer environments.
Since we have now fully tagged and released 1.0.1 and 1.0.2, we can now point at these official tags.
- For each image, we must set up an automated build if it is not already automated.
- master -> "latest"
- new tag -> new tag
- new tag -> "stable"
- For each spec, we must point add the new version tag, and/or the "stable" tag.
- For each Dockerfile, we must point at the latest "stable" release.
NOTE: This will require setting up a slightly different pattern for auto-builds that will push new tags to a "stable" image tag on Docker Hub.
This ticket is complete when the developer environment images can no longer change between builds and/or pod runs.
- is related to
-
NDS-457 Set up build cascades on Docker Hub for automated builds
-
- Resolved
-