Cloud SIG is willing to start building OpenStack packages for Flamingo on CS10, so we'd like to requests the required tags.
Below is the tags informations:
Build target: cloud10s-openstack-flamingo-el10s Buildroot: cloud10s-openstack-flamingo-el10s-build Buildroot inheritance: cloud10s-openstack-flamingo-el10s-build ├─buildsys10s-release └─cloud10s-openstack-flamingo-candidate └─cloud10s-openstack-flamingo-testing └─nfv10s-openvswitch-2-release
Destination tag: cloud10s-openstack-flamingo-candidate
Publishing tags: cloud10s-openstack-flamingo-testing cloud10s-openstack-flamingo-release
External repos: centos10s-baseos centos10s-appstream centos10s-crb centos10s-buildroot
Tags definition should be pretty similar to the equivalent epoxy ones.
Metadata Update from @arrfab: - Issue assigned to arrfab
Metadata Update from @arrfab: - Issue tagged with: cbs, high-gain, low-trouble
Should be created :
* Checking distribution el10s configuration... -> Checking cloud config... Using specific cloud/openstack options: ### BUILDROOT_DEFAULT="openstack-macros bash bzip2 coreutils cpio diffutils redhat-release findutils gawk gcc gcc-c++ grep gzip info make patch redhat-rpm-config rpm-build sed unzip util-linux-ng git which buildsys-tools xz" COMMON_INHERITANCE=false HA_REPO_ENABLED=true ### Creating tag : cloud10s-openstack-flamingo-candidate Creating tag : cloud10s-openstack-flamingo-testing Creating tag : cloud10s-openstack-flamingo-release -> creating cloud10s-openstack-flamingo-el10s Added external repo centos10s-baseos to tag cloud10s-openstack-flamingo-el10s-build (priority 5) Added external repo centos10s-appstream to tag cloud10s-openstack-flamingo-el10s-build (priority 10) Added external repo centos10s-crb to tag cloud10s-openstack-flamingo-el10s-build (priority 15) Added external repo centos10s-buildroot to tag cloud10s-openstack-flamingo-el10s-build (priority 20) Adding cloud10s-openstack-flamingo-testing inheritance Adding nfv10s-openvswitch-2-release inheritance
Metadata Update from @arrfab: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.