Add cmw-seed.yaml and update fesa agent labels

The yaml file should be rather called fes-agent.yaml (fes - front-end software)

it started as just fesa, it also has dsf,
but cmw and timing will go to separate files,
for now I guess it can stay as fesa, we want to keep them separated,
all the *.yaml files in casc should automatically be loaded when deploying

OK, so you will organize with Brice setup of additional agents for CMW & Timing. Thanks!

changed this line in version 2 of the diff

oops, you mean fesa-agent not fesa-seed, yeah, it should be renamed to fes-agent in current situation

for now it would be more straightforward to use one agent for all fes pipelines, and yeah, the agent should be renamed to fes-agent

thanks!

Can we increase the number of executors to 8? It is a strong machine ...

changed this line in version 2 of the diff

Yeah we mostly used 16 for testing, updated

added 1 commit

• 6a897493 - Edit fes-agent

Compare with previous version

The labelString - is it a list of all supported labels?

yeah, this is a list of all labels that the agent is associated with, then pipelines and stages get dispatched on agents based on conditions on labels

Thanks

merged

mentioned in commit 7229982b