| 4 | | - The buildbot is currently triggered from a hook on Gerrit side. The hook could be modified to let refs/for/ changes go to buildbot, but I'm not sure if that would give buildbot enough info to submit its results |
| 5 | | - Buildbot recent versions have a GerritChangeSource (http://docs.buildbot.net/latest/manual/configuration/changesources.html#chsrc-GerritChangeSource), which sounds worth investigating (the current buildbot config has "Y U NO WORK" as a comment for the Git change source which is similar, but I don't know what the problem is with it from this very short description, and there is no ticket about it). |
| 6 | | - Buildbot also has a Gerrit buildstep (http://docs.buildbot.net/latest/manual/configuration/buildsteps.html?highlight=gerrit#gerrit) which integrates with the above to build separate changes in the same project, without creating a dedicated build for each. It can also be used without the changesource if we provide it with the extra info (so if we don't get the changesource working, it's still possible to use this part at least) |
| | 4 | - Concourse needs to be triggered somehow for each submitted change. |
