Hello,
Cloud SIG is about to start building OpenStack packages for Bobcat on CS9, so we'd like to requests the required tags.
Below is the tags information:
Build target: cloud9s-openstack-bobcat-el9s Buildroot: cloud9s-openstack-bobcat-el9s-build Buildroot inheritance: cloud9s-openstack-bobcat-el9s-build ├─buildsys9s-release └─cloud9s-openstack-bobcat-candidate └─cloud9s-openstack-bobcat-testing └─nfv9s-openvswitch-2-release
Destination tag: cloud9s-openstack-bobcat-candidate
Publishing tags: cloud9s-openstack-bobcat-testing cloud9s-openstack-bobcat-release
External repos: centos9s-baseos centos9s-appstream centos9s-crb centos9s-buildroot
Thank you, Joel
Should be done :
cbs taginfo cloud9s-openstack-bobcat-el9s-build Tag: cloud9s-openstack-bobcat-el9s-build [2737] Arches: x86_64 ppc64le aarch64 Groups: build, srpm-build Tag options: mock.new_chroot : 0 mock.package_manager : 'dnf' mock.yum.module_hotfixes : 1 rpm.macro.vendor : 'CentOS Cloud SIG' This tag is a buildroot for one or more targets Current repo: no active repo Targets that build from this tag: cloud9s-openstack-bobcat-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: 5 .... buildsys9s-release [2363] 10 .... cloud9s-openstack-bobcat-candidate [2734] 25 .... nfv9s-openvswitch-2-release [2430]
Can you confirm and then close ticket ?
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: cbs, high-gain, low-trouble
it seems cloud9s-openstack-bobcat-testing is not in the inheritance list of cloud9s-openstack-bobcat-el9s-build
Added, but can you explain why you need this ? really curious about the workflow : all builds are first done and tagged in -candidate (which is available in -build tag) and then you promote/tag-build to -testing and then -release so your builds are already available. Or maybe you're sometimes untagging from -candidate and so such builds are only available in -testing ? (trying to understand)
still waiting on feedback about why that inheritance but closing as task was completed one week ago
why
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Our workflow is:
1.- Build and tag into -candidate 2.a For runtime requirements we promote from -candidate to -testing and remove from candidate 2.b For buildtime only reuirements we promote from -candidat to -el9s-build and remove from candidate 3. We promote from -testing to -release only what we want to ship and buildtime only deps remain in el9s-build
Log in to comment on this ticket.