PATCH: Setup for coreos-pool and coreos-release tags
by Mohan Boddu
CoreOS needs coreos-pool and coreos-release tags to build backported builds
and tag the builds that go into the release.
More info: https://pagure.io/releng/issue/8294
Please review the following patch and let me know if it needs any changes.
diff --git a/roles/koji_hub/templates/hub.conf.j2
b/roles/koji_hub/templates/hub.conf.j2
index 0bf00ce..db8df35 100644
--- a/roles/koji_hub/templates/hub.conf.j2
+++ b/roles/koji_hub/templates/hub.conf.j2
@@ -97,6 +97,8 @@ tag =
fromtag *infra* :: deny
# CoreOS continuous builds, https://pagure.io/releng/issue/8165
tag f{{FedoraRawhideNumber}}-coreos-continuous
f{{FedoraBranchedNumber}}-coreos-continuous
f{{FedoraCycleNumber}}-coreos-continu
+ # CoreOS coreos-pool and coreos-release tags,
https://pagure.io/releng/issue/8294
+ tag coreos-pool coreos-release && has_perm coreos-continuous :: allow
all :: allow
channel =
@@ -149,5 +151,7 @@ package_list =
tag *infra* && has_perm infra && match action add unblock block ::
allow
# CoreOS continuous builds, https://pagure.io/releng/issue/8165
tag f{{FedoraRawhideNumber}}-coreos-continuous
f{{FedoraBranchedNumber}}-coreos-continuous
f{{FedoraCycleNumber}}-coreos-continu
+ # CoreOS coreos-pool and coreos-release tags,
https://pagure.io/releng/issue/8294
+ tag coreos-pool coreos-release && has_perm coreos-continuous && match
action add unblock block :: allow
# Catch-all rule.
all :: deny
diff --git a/roles/robosignatory/files/robosignatory.production.py
b/roles/robosignatory/files/robosignatory.production.py
index 196243a..e2a6b23 100644
--- a/roles/robosignatory/files/robosignatory.production.py
+++ b/roles/robosignatory/files/robosignatory.production.py
@@ -111,6 +111,14 @@ config = {
"keyid": "47dd8ef9"
},
+ # Gated coreos-pool tag
+ {
+ "from": "f30-coreos-signing-pending",
+ "to": "coreos-pool",
+ "key": "fedora-30",
+ "keyid": "cfc659b9"
+ },
+
# Gated rawhide and branched
{
"from": "f31-pending",
5 years
Deployment of plume in Fedora Infrastructure
by Sayan Chowdhury
Hi all,
Over the last few months, I was working on integrating Fedora as a
sub-system to plume. This is to migrate from fedimg to plume, and
finally deprecating plume.
The work on plume has been completed and over the next few days, I
prepare for the deployment of plume. I've prepared a spec document for
the same[1]. I plan to move this to Fedora wiki in some time but if
someone wants to do a review can have a look at it and post comments.
[1] https://hackmd.io/fpDWrtuJT7-jt8jy2yJC1Q?view
--
Sayan Chowdhury <https://words.yudocaa.in/>
GPG Fingerprint : 0F16 E841 E517 225C 7D13 AB3C B023 9931 9CD0 5C8B
5 years
Fedora 30 Final Freeze now in effect!
by Kevin Fenzi
Greetings.
we are now in the infrastructure freeze leading up to the Fedora 30
Final release. This is a final release freeze.
We do this to ensure that our infrastructure is stable and ready to
release the Fedora 30 when it's available.
You can see a list of hosts that do not freeze by checking out the
ansible repo and running the freezelist script:
git clone
https://infrastructure.fedoraproject.org/infra/ansible.git
ansible/scripts/freezelist -i inventory
Any hosts listed as freezes is frozen until 2019-04-30 (or later if
release slips). Frozen hosts should have no changes made to them without
a sign-off on the change from at least 2 sysadmin-main or rel-eng
members, along with (in most cases) a patch of the exact change to be
made to this list.
Thanks,
kevin
5 years
