I'd like to verify my package is still installable. I have come up with:
- hosts: localhost
- role: standard-test-basic
This should be enough to get the new package installed or the CI job fails.
Is that assumption correct?
Hello CIistas (I've just invented this term, probably not good, sorry).
Do we have something like encrypted secrets  for the Fedora CI?
I'd like to add CI tests for twine  that would:
- create a Python package named fedora-ci-canary, versioned as 0+<uuid>
- upload the package to Test PyPI 
- verify it is there
For this however, we would need to store credentials for a Test PyPI account.
I don't mind if the credentials are compromised via malicious Pull Request (they
are to a test environment only), but I don't feel comfortable to store them in
git in plaintext (or obfuscated).
Thanks for hints.
Hello CI folks!
Suppose I have this in my tests.yml:
- repo: "https://src.fedoraproject.org/rpms/pyproject-rpm-macros.git"
This is currently always cloned on the default branch (master).
How do I clone it on a different branch or switch to it? In particular, I need
it to be the same branch we are on -- aka if the tests runs on a f32 Pull
Request, the branch should be f32.
We currently keep rpms/pyproject-rpm-macros identical across braches, but if we
ever stop doing that, I need the approprioate tests to be executed, not rawhide
I figured I would start a new thread instead of continuing on with the
The Jenkins instance running rpminspect has crapped itself for the
second time in less than a week and it's currently not processing the
rpminspect runs it should be.
There are also reports of missing rpminspect runs which likely stem
from the Jenkins issues.
I'm working on it and will send updates as things are fixed and skipped
runs are re-scheduled.