9596b94775
We already had some protection for duplicate semaphore definitions: we would simply ignore all but the first. Normalize this to the recently changed behavior for secrets and nodes: ignore duplicate definitions on different branches of the same project, but otherwise, do not allow them. This is more agressive configuration validation in some cases -- folks with existing duplicate semaphore definitions will now encounter errors. We also perform more validation of semaphores for proposed config updates. We still don't use the new values, however, we do verify that the change won't cause any config parse errors or duplicate errors. Change-Id: I61b43fa1d1e67c35ab5653f35a7667138ed25aa2 |
||
---|---|---|
.. | ||
README | ||
zuul.yaml |
test