Cloud SIG is about to start building OpenStack packages for Antelope on CS9, so we'd like to requests the required tags.
Below is the tags informations:
Build target: cloud9s-openstack-antelope-el9s Buildroot: cloud9s-openstack-antelope-el9s-build Buildroot inheritance: cloud9s-openstack-antelope-el9s-build ├─buildsys9s-release └─cloud9s-openstack-antelope-candidate └─cloud9s-openstack-antelope-testing └─nfv9s-openvswitch-2-release
Destination tag: cloud9s-openstack-antelope-candidate
Publishing tags: cloud9s-openstack-antelope-testing cloud9s-openstack-antelope-release
External repos: centos9s-baseos centos9s-appstream centos9s-crb centos9s-buildroot
Metadata Update from @arrfab: - Issue assigned to arrfab - Issue tagged with: Business-As-Usual, cbs, high-gain, low-trouble
Done and inheritance/repositories are all set :
cbs taginfo cloud9s-openstack-antelope-el9s-build Tag: cloud9s-openstack-antelope-el9s-build [2657] Arches: x86_64 aarch64 ppc64le Groups: build, srpm-build Tag options: mock.new_chroot : 0 mock.package_manager : 'dnf' mock.yum.module_hotfixes : 1 This tag is a buildroot for one or more targets Current repo: repo#959767: 2022-09-08 09:24:22.985954+00:00 Targets that build from this tag: cloud9s-openstack-antelope-el9s External repos: 5 centos9s-baseos (http://mirror.stream.centos.org/9-stream/BaseOS/$arch/os/, merge mode: bare), arches: inherited from tag 10 centos9s-appstream (http://mirror.stream.centos.org/9-stream/AppStream/$arch/os/, merge mode: bare), arches: inherited from tag 15 centos9s-crb (http://mirror.stream.centos.org/9-stream/CRB/$arch/os/, merge mode: bare), arches: inherited from tag 20 centos9s-buildroot (https://kojihub.stream.centos.org/kojifiles/repos/c9s-build/latest/$arch/, merge mode: bare), arches: inherited from tag Inheritance: 0 .... cloud9s-openstack-antelope-testing [2655] 5 .... buildsys9s-release [2363] 10 .... cloud9s-openstack-antelope-candidate [2654] 25 .... nfv9s-openvswitch-2-release [2430]
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
I double checked, it's all good :thumbsup: Thanks @arrfab
Log in to comment on this ticket.