-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP: Refactor master cfg #673
Conversation
b5ddc95
to
da131b1
Compare
@cvicentiu regarding the failure on I see two potential solutions:
Proposed removal of:
One interesting note, this is why
|
cdd1653
to
7e4e702
Compare
* Remove star imports * master-private.cfg always loaded from base directory for all masters.
buildbot.tac as the entrypoint for a buildbot master should use relative paths based on the deployment directory structure. Furthermore, the basedir should be set to <srcdir> so that all imports will work relative to <srcdir>, not the location of buildbot.tac or master.cfg.
Simplify and ensure it returns a 3-value tuple.
This will remove code duplication across master.cfg files.
b14af51
to
147cadd
Compare
147cadd
to
171c728
Compare
8858fbd
to
8ad133a
Compare
* Also fixup unescaped backslashes in strings
73f207f
to
67d005c
Compare
67d005c
to
9e14038
Compare
* Also simplify branch matching functions
8df173d
to
c70e9a1
Compare
* os_info.yaml now provides tags / os * os_info.yaml specifies directly the image tag. This removes the need to do transformations within buildbot configuration code. * define_masters no longer generates a custom buildbot.tac by replacing the log file for the master with a custom name. buildbot.tac now uses a log file based on the master directory. * master-config.yaml now groups builders by architecture.
00b902c
to
bb80148
Compare
Pr to be recreated from FORK so CI does not run twice. |
This pull request is built on top of the code for:
#637
#638
#643
The purpose of this commit is to simplify the master.cfg definitions.