[RFE] tagging builds and builders per package/chroot/user

[fedora-copr-github-bot]

Original issue: https://pagure.io/copr/copr/issue/333
Opened: 2018-06-27 13:34:10
Opened by: praiskup

The https://bugzilla.redhat.com/1334701 solved the heterogeneous farm of builders problem,
but copr backend still treats all the available builders the same way. For this to resolve, it's now
only needed to implement the task-tagging on backend/frontend side ... to let the playbook which allocates builders know what type of builder I need/prefered.

Requirements:

• this is not needed for Fedora Copr instance, so first of all the functionality should be optional and non-intrusive for any Copr instance which doesn't need the functionality (opt-in)
• two types of tags are needed, "required tags", and "private tags". First type of tag would be used to say that the particular task "requires" builder having with tag say "x86_powerful". The second type would allow taking some privileged builder, say "praiskup_builder_x86_64" (that builder/tag is otherwise only allowed for user "praiskup")
• creating new tags must be a copr administrator action, so it's OK to have commandline-only interface
• labeling tasks/builds/packages should be user defined action, and web-ui would be enough

Ideas?

---

praiskup commented at 2020-06-22 09:47:59:

Using the resalloc on the backend side now, the "builder" part is already
ready for this now (builders have the tags) and the mechanism is very
flexible.

We have to solve the "frontend" part, and allow users to tag builds,
packages, projects, etc. so backend can properly match the tasks to the
builders.

[praiskup]

Triage mtg: @xsuchy: A good addition would be an AI doing the tagging automatically per build history (dumped time/processor/memory consumption per recent tasks, etc...).

[praiskup]

Touched again today, @Conan-Kudo needs this for chromium (and alike) projects.