I found a work-around for this. I had a few gating tests for https://bodhi.fedoraproject.org/updates/FEDORA-2019-b83bd6b46c that I needed to retrigger, so I just submitted scratch builds using the same dist-git commit and when those passed, the update was no longer gated.

The only issue is that the test results aren't listed under the package name, but instead get listed under 'undefined' on the 'Automated Tetsts' tab.

Hmm, that seems like a bug :)

According to @bgoncalv the new messaging format and ci-results-updater changes will fix this bad behaviour, even if it for now workarounds the retrigger (I thought that functionality already landed in bodhi) ...

For reference: https://pagure.io/ci-resultsdb-listener/pull-request/13

@mvadkert @bgoncalv I know we have more ways to trigger now, but are we covering this one yet? If not, is the fix to get FAS ID login support (and permissions) into the fedora jenkins instance?

@jimbair I don't think we have at moment any other way to retrigger. I think bodhi was suppose to allow this in the future, but I don't know what is the current status...

@bgoncalv if we added FAS logins, we would need to add a group of some kind into Jenkins to allow Jenkins restarts, unless there's another way to start a retrigger...

@jimbair Right, with FAS login I think we could add a group like Fedora Packager.

It looks like that bodhi updates trigger-tests <update id> can be used to retrigger the tests.
Bodhi will send the CI message again and all CI systems trigger on it will rerun the tests.

We still should provide a way to retrigger an specific test though.

Also one can now use jenkins to rebuild the job for the new Fedora CI, so I believe we can close this.