Following pingou's advice adding ci(a)fedoraproject.org
On Wed, Oct 30, 2019 at 10:03 PM Ben Cotton <bcotton(a)redhat.com> wrote:
> Note - I do not know *how* to add a run of the annocheck program to
> the Bodhi process. This change request is about asking that such a
> thing be added.
In this form I think it doesn't qualify as Fedora Change, so let's see
how we can rework it.
> * Proposal owners:
> In theory there is very little that I can do personally. I do not
> have the knowledge to change the Bodhi process myself, so I will have
> to rely upon someone else to do that. I am familiar with the annobin
> package however, so any changes that are needed to it I will be happy
> to make.
We have a similar check coming to Fedora Rawhide gating. It is called
rpminspect . Check also the talk from Flock 2019 .
Tim Flink and David Cantrell are driving it, and afaik it is close to
being done: the Jenkins job is already up and running and we are
hooking it into the gating framework.
If I understand correctly, the setup for annocheck should be very
similar, so we can reuse most of the work done for rpminspect, with
only the content of the test being different.
There are several work items related to that: setup of a Jenkins job,
update of a Jenkins which is needed to migrate to a new Fedora
We can coordinate of that via Fedora CI SIG , next meeting is on
November 4th  by the way.
Maybe we can make it a joint effort and file one change for both
rpminspect and annocheck?
With a couple of qe & devel guys who are involved in the CI
effort we've started work on creating tmt, a tool for testing.
Why? We've got a bunch of dreams  and we would like to:
* run, debug and develop tests in much more comfortable way 
* open source more tests and run them closer to the upstream
* make creating and enabling tests in the CI more user friendly
We've put together the first proof-of-concept which outlines the
command line syntax. We would like to ask for early feedback and
invite anybody who would like to collaborate on this to join us:
The easiest way how to start experimenting with the latest bits is
to install the tool directly from the git repo as it contains also
a set of real life tests/plans/stories for instant experimenting:
mkvirtualenv tmt # use  to install virtualenvwrapper
git clone https://github.com/psss/tmt
pip install -e .
tmt test ls
tmt plan show
tmt story show create
tmt story coverage --implemented
By creating the tool we aim to implement the L1 and L2 metadata
specification  and cover user stories  which we've gathered
so far. Feel free to review existing stories and provide feedback
or create new stories which are not covered yet.
Also note, that the repository has enabled Packit / Testing Farm
integration  which shows how you can automatically get test
results on copr builds directly in your pull requests, e.g. .
We are looking for any feedback.
 dnf install -y python3-virtualenvwrapper && bash