Braindump:
context:
We want a way to publish messages from different apps (bodhi/pagure) to ask the re-trigger of different tests (Atomic CI, one/more taskotron tests).
Question: How to do authentication/authorization accross multiple systems?
Sillabus:
Server: the application receiving the request and sending the fedmsg to trigger a re-run of a test App 1 and App 2: link to the service (so bodhi or pagure for examples) client: the consumer of the messages (taskotron, AtomicCI...)
Proposal: - App 1 makes a POST request to the server - Server retrieve the elements of the POST request: - target: the identifier - type: bodhi update, pagure commit, PR, koji build - test: the test to be retriggered - Server sends the user to authenticate against FAS with the element in the state argument of the OIDC request - Server checks if the user is allowed to make such request - Server checks if user didn't already do such request recently (like in the last 2 minutes – trying to prevent DDOS angle) - Server asks user to confirm wish to re-trigger the test - Server retrieve missing info (if needed) - Server sends fedmsg message asking the consumer to re-run a test
Metadata Update from @pingou: - Issue assigned to pingou
@adamwill if you want you can subscribe to this ticket, I'll try to update on my progress there (or just watch the project on pagure once it is created :))
I uploaded the preliminary work to https://pagure.io/rats
While still needed, it looks like this is not going to happen by this mean :(
Metadata Update from @pingou: - Issue close_status updated to: Invalid - Issue status updated to: Closed (was: Open)
uh, this is basically done already? the button in bodhi publishes koji-build-group.build.complete messages with a re-trigger key. CI and openQA both listen for and handle those messages. So you can hit the 're-trigger tests' button in Bodhi and have failed tests from CI and openQA retrigger.
koji-build-group.build.complete
re-trigger
I guess the missing part if anything is a similar button in Pagure for PR tests?
Log in to comment on this ticket.