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.
Configuration
Configuration is in 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, if the initialize option is set to True in the fedmsg.d/ config, then all open issues from all upstream repos will be scraped and added to Jira if they are absent.
If the testing option is set to True, then the script will perform a “dry run” and not actually add any new issues to Jira.
Caveats
Here are some things that this program does not do:
This program does not close Jira tickets when their corresponding ticket is closed upstream, although that would be cool.
This program does not attempt to copy comments from upstream tickets to their corresponding downstream tickets, although that would be cool.
If there is interest in having those things, please file an RFE or comment on an existing one here and we’ll see about prioritizing it.
Tests
We have decent test coverage.
Run the tests with:
$ sudo dnf install detox $ detox
1 maintainer
Release files for sync2jira 1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| sync2jira-1.7.tar.gz | 18.7 kB | Details |
Release files / sync2jira-1.7.tar.gz
| Download URL | sync2jira-1.7.tar.gz |
|---|---|
| Size | 18.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dfaa2da70efd1d27cb28941b6714cb6d0901a1e924da32cf6edc4115c3d64f40
|
|
BLAKE2b-256 checksum How to use checksums |
45188f5803e1527a71de58b2e28c11b5c2c947cba107466579a7cf75b872b4a1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
