Ran locally, libabigail was triggered on builds from critpath. Make sure that critpath_filepath contains https://admin.fedoraproject.org/pkgdb/api/critpath?format=json.
Details
- Reviewers
tflink - Maniphest Tasks
- T791: Add support for task-libabigail for tasktron-trigger
- Commits
- rTRGRfa15c711b538: Add support for triggering libabigail
Diff Detail
- Repository
- rTRGR taskotron-trigger
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Overall it looks pretty good to me. I think this is driving home the increasing need to rework trigger instead of using duct tape like this but that's a different issue :)
My only potential concern is the whitelist file. Is that something we want to include with the taskotron-trigger package or is the idea to leave that up to the deployer? If the latter, did you test it with the whitelist path pointing at an non-exsiting file?
Agreed :)
My only potential concern is the whitelist file. Is that something we want to include with the taskotron-trigger package or is the idea to leave that up to the deployer? If the latter, did you test it with the whitelist path pointing at an non-exsiting file?
I did test it with non-existing whitelist path. I intentionally left it to throw IOError so libabigail is not triggered and so it pollutes log with an error so we/deployer know something is not right. Also, I'd like to download the critpath in cronjob regularly so it's up to date and I think we should left that for deployer. Thoughts?
<snip>
My only potential concern is the whitelist file. Is that something we want to include with the taskotron-trigger package or is the idea to leave that up to the deployer? If the latter, did you test it with the whitelist path pointing at an non-exsiting file?
I did test it with non-existing whitelist path. I intentionally left it to throw IOError so libabigail is not triggered and so it pollutes log with an error so we/deployer know something is not right. Also, I'd like to download the critpath in cronjob regularly so it's up to date and I think we should left that for deployer. Thoughts?
That sounds good to me, just wanted to be sure it was tested :)