Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing arbitrary YUM repos #113

Closed
mizdebsk opened this issue Sep 20, 2016 · 3 comments
Closed

Testing arbitrary YUM repos #113

mizdebsk opened this issue Sep 20, 2016 · 3 comments
Assignees

Comments

@mizdebsk
Copy link
Member

As it was already discussed briefly, it would be nice if Koschei could test contents of arbitrary repos specified by user before changes are included in Fedora proper.

Possible workflow:

  • User builds some packages somewhere and generates YUM repo (this can be easily done in Copr).
  • User asks Koschei to test his YUM repo against specified collection.
  • Koschei gets contents of user-provided YUM repo and checks which distro packages build-depend on changed packages and therefore should be tested (this may require repo resolution, but only against Koji)
  • Koschei creates new Copr project, adds user-provided YUM repo and Koji repo (with specific repo_id) as external repos, sets build group contents to match Koji build group and submits package rebuilds, using Koji SRPM URLs.
  • User can use Copr interface (web/CLI/API/fedmsg) to monitor build statuses.
@mizdebsk mizdebsk assigned mizdebsk and msimacek and unassigned mizdebsk Oct 4, 2016
@mizdebsk
Copy link
Member Author

mizdebsk commented Oct 5, 2016

Sharing some PoC Python code I have for creating Copr project and runing a build: https://gist.github.com/mizdebsk/a53208cf62aff5c327caacbac712a390

@mizdebsk
Copy link
Member Author

mizdebsk commented Oct 5, 2016

Note that "custom-1" chroots are currently only available at Copr development instance

@msimacek
Copy link
Contributor

Implemented in 1.9.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants