Pagure Dist Git Interactions With Monitor Gating
Monitor Gating is a set of scripts that is used to test if Fedora CI Gating is working as expected. It essentially follows a typical workflow of cloning a package from dist-git, rebuild it in koji, create a update in bodhi, then checks that the CI runs, and the build is gated appropriately.
Possible Interactions
The following are a set of documented interactions possible between Pagure Dist Git and Monitor Gating.
git and fedpkg CLI
- cloning a repo
Monitor Gating uses
fedpkg cloneto clone a repo from dist-git.- adding a remote
Monitor Gating uses
git remote addto add a fork on dist-git as a remote on a cloned dist-git repo.- switching branches
Monitor Gating uses
fedpkg switch-branchto switch branches on a dist-git cloned repo.- git pull, push, commit
Monitor Gating uses
git commit,git pull`, andgit pushto get and make changes to a dist-git repo.
dist-git (pagure) API
- CI status
Monitor gating currently gets the status of the CI run(s) on a pull request using the get PR flags endpoint (
api/0/<namespace>/<name>/pull-request/<pr-id>/flag).- open pull request
Monitor Gating opens new Pull Requests on dist-git using the pagure API (
api/0/<namespace>/<name>/pull-request/new)- merge pull request
Monitor Gating merges Pull Requests on dist-git using the pagure API (
api/0/<namespace>/<name>/pull-request/<pr-id>/merge)
Changes proposed
In order to switch out Pagure Dist Git for an alternative that provides a relatively compatible API pattern, the following changes must be made in the places mentioned below.
Necessary
The changes made to the Continuous Integration component with regards to the reporting of CI status need to be updated in monitor gating. Currently dist-git uses the pagure flags system.
Monitor Gating will need to be updated to support Opening and Merging pull requests on the new solution
Unnecessary
No changes should be needed for the basic git / fedpkg commands. (this is based on the assumption the new solution is based on git)