| Summary: |
Assertion error when two buildset configurations use GitPoller for same repository |
| Product: |
[Infrastructure] AutoBuilder
|
Reporter: |
Johannes Schrimpf <johannes.schrimpf> |
| Component: |
autobuilder | Assignee: |
Joshua Lock <joshuagloe> |
| Status: |
RESOLVED
FIXED
|
QA Contact: |
|
| Severity: |
normal
|
|
|
| Priority: |
Medium
|
CC: |
infras.ab.watcher, Infras.watcher, pidge, pokylinux
|
| Version: |
unspecified | |
|
| Target Milestone: |
2.4 | |
|
| Hardware: |
x86 | |
|
| OS: |
Multiple | |
|
| Whiteboard: |
|
|
OS type for building Yocto:
|
---
|
Type of Regression:
|
---
|
|---|
|
Verified:
|
|
Documentation change:
|
No (bug/feature does not impact docs)
|
|---|
| Attachments: |
|
Created attachment 3762 [details] A suggested patch which is tested and working on my local setup When two different buildset configurations register a GitPoller for the same repository, an assertion error occurs in buildbot. To prevent this, a check should be implemented whether a GitPoller for this repository is already in yocto-sources and it should only be added if not. A suggested patch which is tested and working on my local setup is attached. When reproducing, please note that other than in the documentation different GitPollers have to have different names and that the second poller in the MultiBranch GitPoller example in the documentation overwrites the first one. This will be reported as an additional bug.