<uovobw>
greetings *. what is the best solution for having two repositories of the same code, that have to build in the same way, but from different branches? let's say i have a repo1 of which i need to build master and a repo2 of which i need to build any branch containing *integration*. my current configuration is https://paste.tapiri.org/paste/1UQGg91J#ws1npjJnRp7FeMd-HeClygHlILnK/svyZ3abX3yaU6w . so
<uovobw>
far it's working but i'm getting a build triggered for repo1 when a change is detected on repo2. plus, the build for repo1 fails as the repo2's branch that triggered the build is not present. i'm sure there is something i'm not getting, but so far i've been pretty stumped. thanks for any help
bdbaddog has joined #buildbot
<uovobw>
i'm trying to wrap my head around this setup, i'm sure i'm not getting something and it seems so trivial looking at the buildbot documentation. i need any changes to repo1 in branch master and any changes in repo2 in branches containing "integration" to run on a set of workers. each of these workers has a number of compilers available on them, so for example worker1 has gcc 8 and 9, clang 10 and
<uovobw>
11, worker2 has gcc 10 and 11, clang 12 and 13 and so on. ideally i'd like to run each change on each worker with each setting its env to use the given set of compilers, i'm not sure of what primitives i need to sue use for buildbot. in particular the relation between schedulers, builders and buildfactories still eludes me, there seems to be no exhaustive examples on the internet, or at least i