- fix bodhi_utils and bodhi directives to work again (rely on update ids where possible)
- enable bodhi2 comments, this time without the decision whether to send emails
- replace 'bodhi_server' in config with 'bodhi_staging'
- fix and add some unit tests
Details
- Reviewers
lbrabec tflink jskladan - Maniphest Tasks
- T583: Fix posting Bodhi comments
- Commits
- rLTRN8dd0fa47a234: enable Bodhi2 comments again, adjust Bodhi configuration
test suite works, I tested manually adding a comment to both stg and prod Bodhi, that also worked
Diff Detail
- Repository
- rLTRN libtaskotron
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
- requirements.txt: require exact version of python-fedora
Most of the fixes were already pushed into python-fedora, we can require specific version again.
Although I'd rather kill the code alltogether (especially since Bodhi does show the test results), I understand the need to notify the developer.
Yeah, I'd rather get rid of it as well but until the fedmsg bits are ready, this is punishment for not having those bits ready in time, I guess.
Looks good to me
requirements.txt | ||
---|---|---|
19 | I'm wondering if this should match the >= of the specfile. I'm not sure if the changes in python-fedora are done for a while or not |
requirements.txt | ||
---|---|---|
19 | Since there were lots of compatibility issues with python-fedora, I'd rather request an exact version and bump it once we test it with (and adjust the code for) some newer version. But I don't have a strong opinion here, if you prefer >=, I'll put it back there. I simply assumed the major bodhi2 fix rush was over now. |
I'm wondering if this should match the >= of the specfile. I'm not sure if the changes in python-fedora are done for a while or not