On Mon, Dec 12, 2022 at 10:27 AM <akashavkin@gmail.com> wrote:
I noticed that in quay.io in tripleotraincentos8, containers with the current-tripleo-rdo tag have not appeared for a long time. I took some time to look into how CI is set up, and found that the names of jobs with test scenarios in CI configuration, after which containers should be marked with this tag, do not match the available jobs in Zuul.

That is correct - we no longer move containers to the  current-tripleo-rdo tag - current-tripleo is the last tag we promote to now.

I was comparing the two files and realized that the job names here do not match:
1. https://github.com/rdo-infra/ci-config/blob/master/ci-scripts/dlrnapi_promoter/config_environments/rdo/CentOS-8/train.yaml#L54
2. https://github.com/rdo-infra/rdo-jobs/blob/master/zuul.d/jobs.yaml#L998

If you pay attention to the current-tripleo tag in the file https://github.com/rdo-infra/ci-config/blob/master/ci-scripts/dlrnapi_promoter/config_environments/rdo/CentOS-8/train.yaml#L15, the scenarios for this tag match the jobs in the rdo-jobs repository for Zuul.

I assume this is the reason for the long absence of this tag. But I do not exclude that the reason lies in something else. I would like to find out why containers with current-tripleo-rdo tag do not appear in qaya.io.
_______________________________________________
users mailing list -- users@lists.rdoproject.org
To unsubscribe send an email to users-leave@lists.rdoproject.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

To unsubscribe: %(_internal_name)s-unsubscribe@%(host_name)s