* Update docs/submodules/releng from branch 'master'
- Merge changes from topic 'yardstick-docker-gambia'
* changes:
Enable yardstick-docker-build-arm-push-gambia job
Make Gambia stream available to ARM Docker builds
Enable yardstick-docker-build-push-gambia job
- Enable yardstick-docker-build-arm-push-gambia job
Similar to https://gerrit.opnfv.org/gerrit/63177 (done for x86_64).
It replaces the yardstick-docker-build-arm-push-fraser job, for the
same reasons.
Depends on https://gerrit.opnfv.org/gerrit/63179
Change-Id: I482bc05d4c6d1316bfde799a44360decacb60a5e
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
- Make Gambia stream available to ARM Docker builds
Similar to https://gerrit.opnfv.org/gerrit/63047 (done for x86_64).
Change-Id: Ie61a11c60ce0fd7c724f308ecfdcca982ebdf3ec
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
- Enable yardstick-docker-build-push-gambia job
It replaces the yardstick-docker-build-push-fraser job, because the
logic in jjb/releng/opnfv-docker.sh L106-L119 has limited options for
docker image tags:
- 'latest', for git commits on master branch
- tag-name, for git tags
- 'stable' otherwise, i.e. for git commits on *any* stable branch.
This means we can have only one (stable) job building and pushing
docker images, in order to prevent the 'stable'-tagged image from
switching between fraser and gambia contents, depending on the stable
branch where the most recent change was cherry-picked and committed.
Unfortunately, disabling the yardstick-docker-build-push-fraser job
also means that further git tags on the stable/fraser branch will not
result anymore in building and pushing new docker images with the
intended tag-name and contents.
Change-Id: Ieec1cdc6230e4c000c159cd743c587561c788fc3
Signed-off-by: Patrice Buriez <patrice.buriez@intel.com>
-Subproject commit f63d4bda4c6dd54d22991b7577df7f885a95f90f
+Subproject commit 76cfe3d847d74073feb735077790fa2c77574a79
Code Review / opnfvdocs.git / commitdiff