Pin a pipeline to an specific agent

[6543]

workaround could be done with set a "custom" platform, but since #690 it's autodetected ...

the idea is to use the "agent labels" as filter but they do not work?

https://github.com/woodpecker-ci/woodpecker/blob/2f91bdd4a0f5167ef304c220865141c15f2dd563/cmd/agent/agent.go#L39-L44 ...

[anbraten]

304

[6543]

hmm could be a dublicate ... depending on if they can be used for this kind of feature ... - I need to test them and they need a good documentation!

[anbraten]

We probably need to refactor them a bit. I would like to have something like a tag property for whole pipelines & pipeline steps and something similar for agents. So it should be possible to

• add one / multiple tags to a pipeline to pin it to an agent having the same tags
• pin an agent based on its hostname (maybe not even needed as it could be solved by tags)
• pin an agent based on its backend #708 (maybe we could add automatic tags like backend:docker to solve this)

[s00500]

Hm.... so this does work, I could add a filter to an agent like this:

WOODPECKER_FILTER="mysyslabel == 'mylabeledrunner'"

Then I can specify labels in the root of the yaml file like

pipelines:
  ...
labels:
  mysyslabel: mylabeledrunner

from the logic I can also see that the condition would be able to filter on "repo" and "platform"... But as pointed out in the older issue the normal platform check is skipped when a filter condition is active on an agent

[anbraten]

We introduced those agent labels which can be used for tagging in #902