this was discussed during the ci community call just now. question raised by weshay is basically do we care that containers are not being tagged with 'tripleo-ci-testing'
Since https://review.openstack.org/641348 the containers pushed to rdo registry with the periodic containers build job are tagged correctly with the tripleo-ci-testing delorean repo hash.
So the question is, do we care that containers are not being pushed with 'tripleo-ci-testing' tag. If all the periodics/singlenode/multinode/ovb are using the tripleo-ci-testing repo delorean hash (and not 'tripleo-ci-testing' itself as a tag).
Removing the promotion blocker and will rework https://review.openstack.org/642662 to instead remove the tagging altogether, unless someone tells us we really need to tag with 'tripleo-ci-testing'
this was discussed during the ci community call just now. question raised by weshay is basically do we care that containers are not being tagged with 'tripleo- ci-testing'
Since https:/ /review. openstack. org/641348 the containers pushed to rdo registry with the periodic containers build job are tagged correctly with the tripleo-ci-testing delorean repo hash.
So the question is, do we care that containers are not being pushed with 'tripleo- ci-testing' tag. If all the periodics/ singlenode/ multinode/ ovb are using the tripleo-ci-testing repo delorean hash (and not 'tripleo- ci-testing' itself as a tag).
Removing the promotion blocker and will rework https:/ /review. openstack. org/642662 to instead remove the tagging altogether, unless someone tells us we really need to tag with 'tripleo- ci-testing'