particle-os/debian-koji
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

build policy

Browse source 
New 'build' policy replacing 'build_from_srpm' and 'build_from_repo_id'.

Related: https://pagure.io/koji/issue/3323

Author:    Tomas Kopecek <tkopecek@redhat.com>
This commit is contained in:
Tomas Kopecek 2022-06-21 15:43:20 +02:00
parent 07536056e8
commit e9ebe2250d
3 changed files with 13 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/source/access_controls.rst
View file

@ -51,9 +51,12 @@ Examples of access control polices are:
* cg_import: control which content generator imports are allowed
* vm: control which windows build tasks are allowed
* dist_repo: control which distRepo tasks are allowed
* build_from_srpm: control whether builds from srpm are allowed
* build_rpm: control whether builds are allowed, this is superceding older ``build_from_srpm``
to handle all task types. ``build_from_srpm`` and ``build_from_repo_id`` are now
deprecated and will be removed in koji 1.33. Default policy allows everything.
* build_from_srpm [deprecated]: control whether builds from srpm are allowed
* build_from_scm: control whether builds from the SCM are allowed and the behavior of the SCM
* build_from_repo_id: control whether builds from user-specified repos ids are allowed
* build_from_repo_id [deprecated]: control whether builds from user-specified repos ids are allowed
Note that not all policies are access control policies.
The ``channel`` and ``volume`` policies are used to control which channels tasks go to