Hello,
I am interested in using Fedora CI to automate running integration tests for the package I maintain https://github.com/Scribery/tlog in Fedora. Currently, I am running all our integration tests manually/locally.
I understand that gating and tests can be run automatically when pull requests are pushed to the fedora dist-git repositories src.fedoraproject.org, but I was wondering if there is a way to trigger the Fedora CI test run from the creation of a github Pull Request. Is it possible to automatically sync a Github repository with a Fedora dist-git repository to handle this?
This leads to another question that might help contextualize what i'm looking for. Is Fedora CI intended to be used to test individual commits(like in a single Github PR), or only multiple changes contained in a Fedora-built package?
If this workflow automation is not possible, i'd like to know if package maintainers are using a more efficient workflow than the following:
1) Submit PR to Github with new code changes 2) Build new SRPM with aforementioned changes 3) Submit PR to fedora CI dist-git repository to trigger tests
Thanks in advance.
-Justin
Hi Justin,
On Tue, Jul 2, 2019 at 5:12 PM Justin Stephenson jstephen@redhat.com wrote:
Hello,
I am interested in using Fedora CI to automate running integration tests for the package I maintain https://github.com/Scribery/tlog in Fedora. Currently, I am running all our integration tests manually/locally.
Agreed.
I understand that gating and tests can be run automatically when pull requests are pushed to the fedora dist-git repositories src.fedoraproject.org, but I was wondering if there is a way to trigger the Fedora CI test run from the creation of a github Pull Request. Is it possible to automatically sync a Github repository with a Fedora dist-git repository to handle this?
We are planning a demo about a similar use case together with packit team: https://pagure.io/flock/issue/170 (feel free to thumbs up :)
The idea is that you onboard your package to packit service [1], which takes care of building the rpm in copr, you configure tests to run in packit's configuration. Tests will be possible to defined via a simple yaml like format (like travis ci).
[1] https://github.com/packit-service/packit
HTH, /M
This leads to another question that might help contextualize what i'm looking for. Is Fedora CI intended to be used to test individual commits(like in a single Github PR), or only multiple changes contained in a Fedora-built package?
If this workflow automation is not possible, i'd like to know if package maintainers are using a more efficient workflow than the following:
- Submit PR to Github with new code changes
- Build new SRPM with aforementioned changes
- Submit PR to fedora CI dist-git repository to trigger tests
Thanks in advance.
-Justin _______________________________________________ CI mailing list -- ci@lists.fedoraproject.org To unsubscribe send an email to ci-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/ci@lists.fedoraproject.org
ci@lists.stg.fedoraproject.org