feature request: gerrit files option for pipeline triggers
Bug #1370105 reported by
Anita Kuno
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Zuul |
Triaged
|
Wishlist
|
Steven Weston | ||
Bug Description
Currently we have a gerrit trigger branch option: http://
We do not have a similar option to filter pipeline triggers on change file patterns.
14:57:49 fungi | it's worth noting that the lack of a files option for pipeline triggers in zuul is probably something we'd be glad to support if someone wrote up the patches to add and test it, we just haven't needed to maintain file-specific pipelines in our production environment and so never implemented it
http://
Revision history for this message
| Jeremy Stanley (fungi) wrote | #1 |
| Changed in zuul: | |
| status: | New → Triaged |
| importance: | Undecided → Wishlist |
| Changed in zuul: | |
| assignee: | nobody → Steven Weston (steve.weston) |
To post a comment you must log in.
The relevancy here is for some Third-Party CI systems reporting on OpenStack projects, who want to limit their systems to only report on changes which modify files with potential interaction in their particular test scenarios. Limiting all jobs to specific file matches currently causes Zuul to successfully report that it ran no jobs on other changes not matching those patterns, which could be seen as useless noise on changes which only modify documentation or other non-impacting files.