-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi all,
As of a bit ago, I have made a few small changes to the Infrastructure tags in koji.
The basic change is that now, after you tagged it $dist-infra-candidate (or built for the "$dist-infra" target), it will still get signed, but NOT tagged into $dist-infra. Instead, the build will be tagged into $dist-infra-stg. This is an additional set of tags that gets put into a set of repositories enabled on staging, but not production, machines. This allows you to test the build thoroughly.
After you have tested the build, you can promote it to production. For instructions on that, see the Promoting topic in [1], but in short it's really just a koji move.
If you need any more information, just let me know.
Regards, Patrick
[1]: https://infrastructure.fedoraproject.org/infra/docs/docs/sysadmin-guide/sops...
On 08/11/2017 12:06 PM, Patrick Uiterwijk wrote:
After you have tested the build, you can promote it to production. For instructions on that, see the Promoting topic in [1], but in short it's really just a koji move.
I was unable to do this step with my bodhi-2.9.1 update today:
$ koji move f25-infra-stg f25-infra bodhi-2.9.1-1.fc25 ActionNotAllowed: tag requires autosign permission
On 08/15/2017 06:44 PM, Randy Barlow wrote:
I was unable to do this step with my bodhi-2.9.1 update today:
$ koji move f25-infra-stg f25-infra bodhi-2.9.1-1.fc25 ActionNotAllowed: tag requires autosign permission
I was able to do it for the epel7 tag, as written in the docs, so maybe the f25 tag just needs to be adjusted? I filed a ticket for this:
infrastructure@lists.fedoraproject.org