summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
authorClark Boylan <clark.boylan@gmail.com>2022-03-31 17:19:21 -0700
committerClark Boylan <clark.boylan@gmail.com>2022-04-05 16:35:25 -0700
commitc393e41d00814a7ad56a79475bd3faaf87cd72cd (patch)
tree79532a5b7a32474cb023f4a9f08eebe2eee1aca5 /releasenotes
parent08348143f5c438547b3b4b73f6af7ff7e753e013 (diff)
downloadzuul-c393e41d00814a7ad56a79475bd3faaf87cd72cd.tar.gz
Handle greedy project name regexes
Some users (and our documentation [0]) may want to have project name regexes that match all projects: ^.*$. If the zuul installation has colliding project names this is always an error because we evaluate the non canonical names first then check for collisions. We have realized the point of the regex system is to simplify configuration and apply configs to any projects that match. Collisions don't impact this. Stop returning an error if there are collisions and instead apply the configs to those projects. [0] https://zuul-ci.org/docs/zuul/latest/tutorials/quick-start.html#configure-zuul-pipelines Change-Id: I48fbab74fb42ba7c8005ef1a07b61c090acc154d
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/project-regex-update-dcc183d923a6acdd.yaml8
1 files changed, 8 insertions, 0 deletions
diff --git a/releasenotes/notes/project-regex-update-dcc183d923a6acdd.yaml b/releasenotes/notes/project-regex-update-dcc183d923a6acdd.yaml
new file mode 100644
index 000000000..87c0e3fb1
--- /dev/null
+++ b/releasenotes/notes/project-regex-update-dcc183d923a6acdd.yaml
@@ -0,0 +1,8 @@
+---
+fixes:
+ - |
+ Project name regex handling has been updated to return all possible
+ matches. Previously if there were collisions with short names it was an
+ error. The point of the regex system is to simplify configuration and
+ apply configs to all projects that match. Collisions don't impact this
+ behavior so we don't need to raise an error in these cases.