I'd like to announce a Fedora Special Interest Group dedicated to the
topics of Continuous Integration, Continuous Delivery, Gating and
I've created a wiki page with the initial data:
Please join, add yourself to member list, bring your ideas and work items.
I'd like to also setup a bi-weekly IRC meeting, so please think about what
time would work best for you. Let's have a separate discussion on that next
Feedback is welcome.
Quote from the wiki:
== Goal ==
The goal of the SIG is to bring together CI enthusiasts interested in
developing tools, best practices, standards, and workflows to implement
Continuous Integration at a larger scale.
While CI is well-known and used by many software projects, it is usually
applied at an individual component level. Scaling it up is a challenge from
both technical and organizational points of view. Here in Fedora, we have
an opportunity to explore and develop the CI/CD topic beyond simple
== Topics ==
* CI for Fedora
* Containerized CI
* CI on bare-metal
* Gating at scale
* Packaging and CI
* CI and Upstream
* CI engines, Artifact storages, Test analytics
== Benefit to Fedora ==
CI is rarely associated with packaged Linux distributions even though it is
nowadays used in most of them. We’d like to change this perception, to show
that packaging and CI can and should be used together.
We also would like to establish Fedora as a perfect CI platform.
Virtualization, containerization and many other tools available in Fedora
provide a good foundation to build flexible, open and modern CI solutions
and CI architectures on top of it. Let's make use of them.
bookwar on IRC
I am trying to get a wrapped test script to work for squashfs-tools and
the artifacts don't appear to be properly saved. I think I might be
misunderstanding the wrapper example. Is the idea really that the test
should run ansible with the basic role referring to the wrapper? I
have been trying to run the wrapper as the test and it runs the shell
script, but the test results don't end up where the CI can find them
and the test fails.
I also don't see a way for the wrapper to ask for extra packages other
than to run dnf in the script.
There is stuff to look at in the pipeline pages if you want to see what I
tried to do.
test mailing list -- test(a)lists.fedoraproject.org
To unsubscribe send an email to test-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://email@example.com
Currently the Standard Test Interface does not define how to
distinguish test failure from an infrastructure error. When
ansible playbook is run it usually does some environment
preparation and only then executes tests. Upon a problem
encountered during provisioning or configuration of the test
environment ansible returns non-zero exit code but there is not an
easy way how to detect such error from a successful test execution
of test which failed (returns non-zero exit code as well).
Let's make this part of the specification more clear so that tools
can detect infrastructure errors and report them as such to the
end user. This will help to direct problems (errors versus
failures) to the right audience (infrastructure staff versus
See the following ticket for proposed solution and share your