Hi all,
After some tests and some feedback from some SIGs , we're happy to announce that we'll go live this wednesday with the new signing process (also covering c8)
Per discussion/feedback with some SIGs (or lack of feedback), we locked the following CBS tags :
paas7-openshift-origin311-release paas7-openshift-origin-release paas7-openshift-origin13-release paas7-openshift-origin14-release paas7-openshift-origin15-release paas7-openshift-origin36-release paas7-openshift-origin37-release paas7-openshift-origin38-release paas7-openshift-origin39-release paas7-openshift-origin310-release paas7-openshift-common-release nfv7-vpp-1801-release nfv7-vpp-1804-release nfv7-vpp-1807-release nfv7-common-release virt7-ovirt-42-release virt7-ovirt-44-release virt7-kubernetes-19-release virt7-kubernetes-110-release opstools7-perfmon-common-release opstools7-common-release opstools7-sensu-common-release opstools7-sensu-027-release opstools7-sensu-110-release opstools7-fluentd-012-release
If you have questions, Thomas and myself will be answering in #centos-devel, should any issue arise.
PS : for Trimmed content/EOL, each SIG should start considering announcing content that will go away (to vault and not available to mirror network)
On 23/03/2020 11:47, Fabian Arrotin wrote:
Hi all,
After some tests and some feedback from some SIGs , we're happy to announce that we'll go live this wednesday with the new signing process (also covering c8)
<snip>
If you have questions, Thomas and myself will be answering in #centos-devel, should any issue arise.
Just to let you know that at 9am UTC we switched to new process and we kicked 'manually' the process for some tags that had some pending updates :
* storage7-gluster-7-release * storage6-gluster-7-release * opstools8-collectd-5-release * cloud7-openstack-train-release * cloud7-openstack-stein-release * cloud7-openstack-rocky-release As some SIG active members were in #centos-devel and confirmed that process was working fine, we have fully enabled the automatic notification from cbs.centos.org to trigger the sign+push process after a "tag-build" koji operation.
In other words : "We're now live !" :-)
On Wed, Mar 25, 2020 at 11:04 AM Fabian Arrotin arrfab@centos.org wrote:
On 23/03/2020 11:47, Fabian Arrotin wrote:
Hi all,
After some tests and some feedback from some SIGs , we're happy to announce that we'll go live this wednesday with the new signing process (also covering c8)
<snip> > > If you have questions, Thomas and myself will be answering in > #centos-devel, should any issue arise. >
Just to let you know that at 9am UTC we switched to new process and we kicked 'manually' the process for some tags that had some pending updates :
- storage7-gluster-7-release
- storage6-gluster-7-release
- opstools8-collectd-5-release
- cloud7-openstack-train-release
- cloud7-openstack-stein-release
- cloud7-openstack-rocky-release
As some SIG active members were in #centos-devel and confirmed that process was working fine, we have fully enabled the automatic notification from cbs.centos.org to trigger the sign+push process after a "tag-build" koji operation.
In other words : "We're now live !" :-)
Thanks to all the involved team!
I think this is a great achievement that will help CentOS community in one of the usual pain points in the last times.
Great work!
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi,
I have problem accessing https://cbs.centos.org/repos/storage8-gluster-7-testing/ is it related to this new process?
Thanks
On Wed, Mar 25, 2020 at 12:55 PM Alfredo Moralejo Alonso < amoralej@redhat.com> wrote:
On Wed, Mar 25, 2020 at 11:04 AM Fabian Arrotin arrfab@centos.org wrote:
On 23/03/2020 11:47, Fabian Arrotin wrote:
Hi all,
After some tests and some feedback from some SIGs , we're happy to announce that we'll go live this wednesday with the new signing process (also covering c8)
<snip> > > If you have questions, Thomas and myself will be answering in > #centos-devel, should any issue arise. >
Just to let you know that at 9am UTC we switched to new process and we kicked 'manually' the process for some tags that had some pending updates :
- storage7-gluster-7-release
- storage6-gluster-7-release
- opstools8-collectd-5-release
- cloud7-openstack-train-release
- cloud7-openstack-stein-release
- cloud7-openstack-rocky-release
As some SIG active members were in #centos-devel and confirmed that process was working fine, we have fully enabled the automatic notification from cbs.centos.org to trigger the sign+push process after a "tag-build" koji operation.
In other words : "We're now live !" :-)
Thanks to all the involved team!
I think this is a great achievement that will help CentOS community in one of the usual pain points in the last times.
Great work!
-- Fabian Arrotin The CentOS Project | https://www.centos.org gpg key: 17F3B7A1 | twitter: @arrfab
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 25/03/2020 13:56, Galit Rosenthal wrote:
Hi,
I have problem accessing https://cbs.centos.org/repos/storage8-gluster-7-testing/ is it related to this new process?
It's related in a sense that, as announced, mash doesn't run anymore and *nobody* was ever supposed to consume pkgs straight from cbs.centos.org ;-) (see mail thread in the last days)
Tagged pkgs for -testing automatically land here : https://buildlogs.centos.org/centos/8/storage/x86_64/gluster-7/ (replace x86_64 with other available arches, in this case ppc64le and aarch64 too)
BTW : that's also reason why Kaleb worked on the centos-release-gluster pkgs that has also the -testing repository pointing to buildlogs.centos.org ;-)
-
Alfredo Moralejo Alonso -
Fabian Arrotin -
Galit Rosenthal