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

update docs for kickstart/build_rpm policy

Browse source 
Related: https://pagure.io/koji/issue/3183
This commit is contained in:
Tomas Kopecek 2023-05-17 10:01:34 +02:00
parent 70c9b3e37a
commit 2ddfd5e977
2 changed files with 8 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

5
docs/source/defining_hub_policies.rst
View file

@ -131,6 +131,11 @@ Available policies
The system currently looks for the following policies
* ``tag``: checked during tag/untag/move operations
* ``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
when py2 support will be dropped (rhel6 builders).
Default policy allows everything.
* ``build_from_srpm``: checked when a build from srpm (not an SCM reference) is
requested.
* ``build_from_scm``: checked when a build task from SCM is executing on builder

3
docs/source/image_build.rst
View file

@ -61,6 +61,9 @@ URL would have the ``?`` and ``#`` right next to each other.
If we passed ``--ksurl`` the string above, and gave
``--kickstart "server-ec2.ks"``, then Koji would do the following:
* Consult hub SCM policy ``build_rpm``. Name of the policy could change in the
future as it has misleading name now. Policy could check if the given SCM is
allowed for this method, etc. In case it deny the build, it ends here.
* Clone the repository locally
* Call ``git reset --hard 68c40eb7``
* Search in the "fedora22" subdirectory of the clone for a file called