[releng] Issue #6756: "ActionNotAllowed" when attempting "koji untag-build
f27"
by Mat Booth
mbooth reported a new issue against the project: `releng` that you are following:
``
I used to be able to untag rawhide builds I'd just built, but when I tried today I get:
"ActionNotAllowed: tag requires autosign permission"
The command I attempted was:
"koji untag-build f27 eclipse-ecf-3.13.3-3.fc27 eclipse-emf-2.12.0-5.fc27"
I am trying to untag eclipse-ecf-3.13.3-3.fc27 and eclipse-emf-2.12.0-5.fc27
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6756
6 years, 10 months
[releng] Issue #6848: Adjust rawhide tags when testing is available
by Kevin Fenzi
kevin reported a new issue against the project: `releng` that you are following:
``
As soon as we have something to test rawhide builds we should adjust the tag flow.
Currently:
user builds package -> tagged into f27-pending (or whatever rawhide currently is) -> autosign signs it and moves it to f27 tag and that in turn populates f27-build for buildroot.
Desired:
user builds package -> tagged into f27-pending (or whatever rawhide currently is) -> autosign signs it and moves it to f27-pending-candidate and that populates f27-build for buildroot. Then the test process can look at builds in f27-pending-candidate and untag them if they fail testing. Then, pungi will look at f27-pending-candidate tagged builds and move them all to f27 and compose. (possibly we could add some sanity testing to pungi at the beginning). Additionally, maintainers could untag from f27-pending-candidate if they desired before the next compose runs.
``
To reply, visit the link below or just reply to this email
https://pagure.io/releng/issue/6848
6 years, 10 months