This is a process that listens to activity on upstream repos on pagure and github via fedmsg, and syncs new issues there to a Jira instance elsewhere.
Documentation is hosted on readthedocs.io and can be found here
We have set up a quick-start here
Configuration is in folder fedmsg.d.
You can maintain a mapping there that allows you to match one upstream repo (say, 'pungi' on pagure) to a downstream project/component pair in Jira (say, 'COMPOSE', and 'Pungi').
On startup, in the fedmsg.d/sync2jira.py config map,
- if the initialize option is set to
Truethen all open issues from all upstream repos will be scraped and added to Jira if they are absent. - if the
testingoption is set toTrue, then the script will perform a "dry run" and not actually add any new issues to Jira.
Please look at our documentation here for a full list of what can be synced and how to set it up.
We will maintain three branches
master- This will be where our main code and most up to date code livesstage- This will be our staging configuration. PR's will merge through stage to masteropenshift-build- This branch will maintain OpenShift-Build related information