The only docker images that can be built today by project committers through CI are:
* images off tip of master with docker tag “latest” * images off tip of stable branches with docker tag “stable” Currently, there is no way for a project committer to build and push to DockerHub container images: 1. Based on project specific version tags off master branch. 2. Based on opnfv release tags off any stable branch As discussed with Trevor at the plugfest, would it be possible to have a CI trigger to allow a project committer to do (a) and (b) above? Ideally a git tag push on the master branch (which should only be allowed for committers) with a tag following the semver syntax (e.g. 1.3.8) should trigger the build from the tag hash and result in a container that has the same tag, and should push the container to DockerHub. Optionally, the trigger could also push the image with the “latest” docker tag *iff* the tag triggering the build is at tip of master. Example: git tag: 1.3.8 resulting docker tag: 1.3.8 and latest (if 1.3.8 is tip of master) I think it might make sense to follow the same mechanism and allow stable branch images to be built and pushed when a tag with the right syntax is applied to the stable branch. git tag: opnfv-5.1.0 resulting docker image tag: opnfv-5.1.0 and “stable” if that tag is at top of stable branch Not clear yet how a specific container image (with given tag) can be triggered through CI (open to any suggestion) Thanks Alec
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
