FBR for disabling branched composes
by Mohan Boddu
As we already have Gold RC compose, its time to disable nightlies.
diff --git a/roles/releng/files/branched b/roles/releng/files/branched
index 270a6a1..e8f3f58 100644
--- a/roles/releng/files/branched
+++ b/roles/releng/files/branched
@@ -1,4 +1,4 @@
# branched compose
-MAILTO=releng-cron(a)lists.fedoraproject.org
-15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XXXXXX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f27 && LANG=en_US.UTF-8 ./nightly.sh && sudo -u ftpsync /usr/local/bin/update-fullfiletimelist -l /pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora fedora-secondary
-15 1,14 * * * root TMPDIR=`mktemp -d /tmp/branched-modular.XXXXXX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f27 && LANG=en_US.UTF-8 ./nightly-modular.sh
+#MAILTO=releng-cron(a)lists.fedoraproject.org
+#15 7 * * * root TMPDIR=`mktemp -d /tmp/branched.XXXXXX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f27 && LANG=en_US.UTF-8 ./nightly.sh && sudo -u ftpsync /usr/local/bin/update-fullfiletimelist -l /pub/fedora-secondary/update-fullfiletimelist.lock -t /pub fedora fedora-secondary
+#15 1,14 * * * root TMPDIR=`mktemp -d /tmp/branched-modular.XXXXXX` && cd $TMPDIR && git clone https://pagure.io/pungi-fedora.git && cd pungi-fedora && git checkout f27 && LANG=en_US.UTF-8 ./nightly-modular.sh
5 years, 4 months
FBR for 0-day release actions
by Mohan Boddu
As per 0-day Release Actions under https://infrastructure.fedoraproject.org/infra/docs/docs/sysadmin-guide/s... SOP, I made the following changes:
diff --git a/roles/bodhi2/backend/templates/atomic-config.py.j2 b/roles/bodhi2/backend/templates/atomic-config.py.j2
index d75269c..c355e96 100644
--- a/roles/bodhi2/backend/templates/atomic-config.py.j2
+++ b/roles/bodhi2/backend/templates/atomic-config.py.j2
@@ -6,6 +6,60 @@ rhel6 = dist[0] == 'redhat' and int(float(dist[1])) == 6
config = dict(
releases={
+ 'f27-updates': {
+ 'name': 'f27-updates',
+ 'repo': 'updates',
+ 'version': '27',
+ 'arch': 'x86_64',
+
+ # OSTree treefile configuration
+ # https://github.com/projectatomic/rpm-ostree/blob/master/doc/treefile.md
+ 'tree': 'docker-host',
+ 'treefile': {
+ 'include': 'fedora-atomic-host.json',
+ 'ref': 'fedora/27/x86_64/updates/atomic-host',
+ 'repos': ['fedora-27', 'fedora-27-updates', 'updates'],
+ 'packages': [],
+ },
+
+ # The name of the mock container to build and maintain
+ 'mock': 'fedora-27-updates-x86_64',
+
+ # The git branch to use in the `git_repo` for the parent
+ # treefile & repo configurations
+ 'git_branch': 'f27',
+
+ # Add or overwrite yum repository name:urls. This lets you
+ # compose trees against your own repositories.
+ 'repos': {},
+ },
+ 'f27-updates-testing': {
+ 'name': 'f27-updates-testing',
+ 'repo': 'updates-testing',
+ 'version': '27',
+ 'arch': 'x86_64',
+
+ # OSTree treefile configuration
+ # https://github.com/projectatomic/rpm-ostree/blob/master/doc/treefile.md
+ 'tree': 'docker-host',
+ 'treefile': {
+ 'include': 'fedora-atomic-host.json',
+ 'ref': 'fedora/27/x86_64/testing/atomic-host',
+ 'repos': ['fedora-27', 'fedora-27-updates', 'updates-testing'],
+ 'packages': [],
+ },
+
+ # The name of the mock container to build and maintain
+ 'mock': 'fedora-27-updates-testing-x86_64',
+
+ # The git branch to use in the `git_repo` for the parent
+ # treefile & repo configurations
+ 'git_branch': 'f27',
+
+ # Add or overwrite yum repository name:urls. This lets you
+ # compose trees against your own repositories.
+ 'repos': {},
+ },
'f26-updates': {
'name': 'f26-updates',
'repo': 'updates',
diff --git a/roles/bodhi2/base/templates/production.ini.j2 b/roles/bodhi2/base/templates/production.ini.j2
index 1629e2d..5b22659 100644
--- a/roles/bodhi2/base/templates/production.ini.j2
+++ b/roles/bodhi2/base/templates/production.ini.j2
@@ -10,7 +10,7 @@ filter-with = proxy-prefix
# Release status
# pre-beta enforces the 'Pre Beta' policy defined here:
# https://fedoraproject.org/wiki/Updates_Policy
-f27.status = pre_beta
+f27.status = post_beta
f27.post_beta.mandatory_days_in_testing = 7
f27.post_beta.critpath.num_admin_approvals = 0
Once the patch is approved, I will commit the changes and push it to the ansible and some one should run the bodhi playbook as I dont have the permissions.
Once thats done I will run
bodhi-manage-releases edit --name F27 --state current --username mohanboddu
to change the F27 state from pending to current.
5 years, 4 months
Fedora Infrastructure Meeting 2017-11-09 1800 UTC
by Stephen John Smoogen
REMINDER THE MEETING TIME IS SET WITH UTC SO DST ending moves it back one hour
The infrastructure team will be having it's weekly meeting tomorrow,
2017-11-09 at 18:00 UTC in #fedora-meeting on the freenode network.
We have a gobby document
(see: https://fedoraproject.org/wiki/Gobby )
fedora-infrastructure-meeting-next is the document.
This shared document is for the next fedora infrastructure meeting.
= Introduction =
We will use it over the week before the meeting to gather status and info and
discussion items and so forth, then use it in the irc meeting to transfer
information to the meetbot logs.
= Meeting start stuff =
#startmeeting Infrastructure (2017-11-09)
#meetingname infrastructure
#topic aloha
#chair smooge relrod nirik dgilmore threebean pingou puiterwijk
pbrobinson maxamillion
= Let new people say hello =
#topic New folks introductions
#info This is a place where people who are interested in Fedora
Infrastructure can introduce themselves
= Status / Information / Trivia / Announcements =
(We put things here we want others on the team to know, but don't need
to discuss)
(Please use #info <the thing> - your name)
#topic announcements and information
#info PHX2 Colo Trip, Dec 4th - 9th
#info Final freeze has started. PLEASE TEST ANY RCs.
#info new notifs in staging, please test!
#info
= Things we should discuss =
We use this section to bring up discussion topics. Things we want to talk about
as a group and come up with some consensus /suor decision or just brainstorm a
problem or issue. If there are none of these we skip this section.
(Use #topic your discussion topic - your username)
#topic Ticket cleanup
#info none this week.
#topic Apprentice work day - 2017-11-29 - kevin
#topic What to do about Meetbot redux - kevin
#topic How to monitor bastion mail queue - kevin
https://pagure.io/fedora-infrastructure/issue/5908
#topic
= Apprentice office hours =
#topic Apprentice Open office hours
Here we will discuss any apprentice questions, try and match up people looking
for things to do with things to do, progress, testing anything like that.
= Learn about some application or setup in infrastructure =
(This section, each week we get 1 person to talk about an application or setup
that we have. Just going over what it is, how to contribute, ideas for
improvement,
etc. Whoever would like to do this, just add the i/nfo in this section. In the
event we don't find someone to teach about something, we skip this section
and just move on to open floor.)
#topic Learn about:
#info none this week
= Meeting end stuff =
#topic Open Floor
#endmeeting
--
Stephen J Smoogen.
5 years, 4 months
Server space for Fedora users?
by Jun Aruga
I want to build Mongo DB server somewhere in Fedora servers as my
experiment for effective Fedora packaging.
Because I want to research a correlation between the build error and how to
be fixed by machine learning approach to automate RPM packaging.
I do not want to pay my money for my private AWS server for that. :)
Is it possible to a server space?
For example,
A RPM package's repository has
Time line: Commit A => Commit B
- Commit hash A that has a build error.
- Commit hash B that the error is fixed on.
The record may be like this.
Input data:
- Fedora package name
- The RPM spec file content at commit hash A.
- root.log and build.log at the commit hash A.
Output data:
- Commit hash B: How to be fixed for commit hash A's error.
Jun
5 years, 4 months
