We plan to upgrade the software factory deployment on 2021-03-15 from
14:00 to 16:00 UTC to the next 3.6 release(including Gerrit 3.2, Zuul
and Nodepool 4.0 and a new web-ui for the welcome page of
Service interruption is expected, including:
- Zuul CI not running jobs for pagure.io or src.fedoraproject.org.
- Change in provided zuul-jobs roles.
We expect that the interruption of services will be less than 2 hours.
Nicolas , on behalf of the Software Factory Operation Team
Zuul now does this for noarch packages:
check-for-arches : SUCCESS in 1m 06s
rpm-scratch-build : SUCCESS in 9m 07s
rpm-scratch-build-s390x : SKIPPED (non-voting)
rpm-scratch-build-ppc64le : SKIPPED (non-voting)
rpm-scratch-build-i686 : SKIPPED (non-voting)
rpm-scratch-build-armv7hl : SKIPPED (non-voting)
rpm-scratch-build-aarch64 : SKIPPED (non-voting)
Is there a way we can opt-in for arch-specific scratch-builds of our noarch
packages for the sake of running the %check section on all architectures?
For those who still haven't heard: tmt  is now fully supported
in Packit , Fedora CI  and the RHEL CI. This means it is
possible to use the same concise and consistent config to enable
tests across all of them, more easily open source tests, share
test coverage across releases and run tests as early as possible.
In the coming weeks we'll be sharing short, bite-sized examples
demonstrating the tmt usage so that new users can get quickly
started and existing users do not miss various interesting and
useful features hidden under the hood.
Here we go with the first set of examples showing how to quickly
enable a simple smoke test for your component, assuming you are in
your project git repository:
sudo dnf install -y tmt
tmt init --template mini
Adjust the example plan to run the desired command:
summary: Basic smoke test
script: foo --version
The very minimal config is really just two lines:
script: make test
Now submit the pull request and wait for the results:
git add .
git checkout -b smoke-test
git commit -m "Enable a simple smoke test"
git push fork -u smoke-test
Eager to learn more? Not patient enough to wait for the results
from the CI pipeline? Willing to safely execute tests from your
laptop right now? Check the rest of the first chapter of our brand
new guide to learn more .
P.S. Join the #tmt channel if you have any questions.
Reviewing our agenda for tomorrow, I don't see any issues currently
needing to be discussed in regards to Fedora CI this week. However, this
was also the case two weeks ago, so either things are running perfectly, or
we may have a timing conflict with another meeting for our members. =)
I'd like to keep our recurring meetings in-place, even if we have nothing
to discuss. But please reach out and let me know if a conflicting meeting
is keeping you from being able to attend. If so, I can seek out another day
and time that works for as many members as possible so we can bring our
attendance up once again and ensure operational and logical issues can be
discussed and addressed.
From my perspective, things have been quiet for awhile now, with no big
changes aside from the legacy cluster being decommissioned, which we moved
away from some time ago. As always, if you have any questions or issues you
would like to discuss, please update the agenda and we'll set aside time
to discuss. If no topics are on the agenda, then you can have your 30
minutes back. =)
my Fedora update
has one passed automated test fedora-ci.koji-build.tier0.functional
with link pointing to
However, access to that URL from Fedora 33's Firefox
firefox-84.0.2-1.fc33.x86_64 results in
Secure Connection Failed
An error occurred during a connection to
The page you are trying to view cannot be shown because
the authenticity of the received data could not be
Please contact the website owners to inform them of this problem.
Even accessing it via curl fails:
$ curl -k https://jenkins-continuous-infra.apps.ci.centos.org/blue/organizations/je...
curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to jenkins-continuous-infra.apps.ci.centos.org:443
Checking with openssl shows that there is not certificate / encryption
$ openssl s_client -connect jenkins-continuous-infra.apps.ci.centos.org:443
no peer certificate available
No client certificate CA names sent
SSL handshake has read 0 bytes and written 337 bytes
New, (NONE), Cipher is (NONE)
Secure Renegotiation IS NOT supported
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
Could the Jenkins instance used for Fedora CI have its certificates
fixed or have some frontend proxy in from of them so that access from
contemporary Fedora versions works?
Product Owner, Platform Security Readiness, Red Hat