I would like to submit the idea of running flag build-o-matic in our infrastructure.
It's a simple fedmsg-based service listening for fedmsg messages from koji and build ending and flag the corresponding commits in the corresponding project in dist-git.
To run it we would need: - a place to run it (a cloud box as we do for simple-koji-ci is likely the easiest) - a project-less API token to it can flag any and all PRs in dist-git (I can take care of this)
Thoughts?
Tagging this for a security audit (should be straight forward)
Metadata Update from @pingou: - Issue tagged with: request-for-resources, security
Looks good to me from a security POV. Audit ack at checksum 9c6f981a758b4d622041bce6f09dcb27e37134b7.
9c6f981a758b4d622041bce6f09dcb27e37134b7
Metadata Update from @puiterwijk: - Issue untagged with: security
Can you describe a bit about what we intend to use this for?
Is it actually doing the tags in git? or just the pagure over dist-git db?
It flags the commits in pagure when they are successfully built in koji
For example: https://src.fedoraproject.org/rpms/perl-IO-HTML/c/69a460858b8c1f47bb6320faa6f310dab6808184
The idea is to then expose those flags via the API and see if we can get something like "badges" or "shield" to show up in the front page on dist-git
There is a wish to have test results from the allpackages CI pipeline to be reported back to pagure, I was thinking to piggy back on fbom since the core functionality is the same (flagging commit), I'd just need to add support for another set of messages published.
Does that sound reasonable?
Metadata Update from @kevin: - Issue assigned to pingou - Issue priority set to: Waiting on Asignee
This has now been pushed and is running via loopabull, so no more RFR needed :)
Metadata Update from @pingou: - Issue close_status updated to: Fixed
Login to comment on this ticket.