The reason for creating a new buildbot is that the our current buildbot is using a very old buildbot version that is hard to maintain (old not supported code). It has also serious limitations, for example it can't use the git protocol for protected branches.
The new buildbot configurations will largely use native Dockers. This will make the new buildbot about 2.5 faster and use less resources for doing builds.
In addition it will support connectivity to GitHub directly integrated through oAuth.
Monty to signal to server developers (on Slack, on Tuesday Dev call (12.5.2020), or email to server@mariadb.com, Cc Vlad Vic Kaj, or a combination thereof): “I will start using the new Buildbot from now on. It is what we want to move to. Only by using it can we give adequate feedback to the Buildbot developers (Vlad Bogolin, Vicentiu Ciorbaru), and the new Buildbot is now good enough to make the switch. The key benefit for now is that it’s 2,5x faster. It also has native Docker container support, and connectivity to GitHub directly integrated through oAuth.”
don't move this to new Jira!
Monty to signal to server developers (on Slack, on Tuesday Dev call (12.5.2020), or email to server@mariadb.com, Cc Vlad Vic Kaj, or a combination thereof): “I will start using the new Buildbot from now on. It is what we want to move to. Only by using it can we give adequate feedback to the Buildbot developers (Vlad Bogolin, Vicentiu Ciorbaru), and the new Buildbot is now good enough to make the switch. The key benefit for now is that it’s 2,5x faster. It also has native Docker container support, and connectivity to GitHub directly integrated through oAuth.”
Monty to signal to server developers (on Slack, on Tuesday Dev call (12.5.2020), or email to server@mariadb.com, Cc Vlad Vic Kaj, or a combination thereof): “I will start using the new Buildbot from now on. It is what we want to move to. Only by using it can we give adequate feedback to the Buildbot developers (Vlad Bogolin, Vicentiu Ciorbaru), and the new Buildbot is now good enough to make the switch. The key benefit for now is that it’s 2,5x faster. It also has native Docker container support, and connectivity to GitHub directly integrated through oAuth.”
The reason for creating a new buildbot is that the our current buildbot is using a very old buildbot version that is hard to maintain (old not supported code). It ha also serious limitations, for example it can't use the git protocol for protected branches.
The new buildbot configurations will largely use native Dockets. This will make the new buildbot about 2.5 faster and use less resources for doing builds.
In addition it will support connectivity to GitHub directly integrated through oAuth.
The reason for creating a new buildbot is that the our current buildbot is using a very old buildbot version that is hard to maintain (old not supported code). It ha also serious limitations, for example it can't use the git protocol for protected branches.
The new buildbot configurations will largely use native Dockets. This will make the new buildbot about 2.5 faster and use less resources for doing builds.
In addition it will support connectivity to GitHub directly integrated through oAuth.
The reason for creating a new buildbot is that the our current buildbot is using a very old buildbot version that is hard to maintain (old not supported code). It ha also serious limitations, for example it can't use the git protocol for protected branches.
The new buildbot configurations will largely use native Dockets. This will make the new buildbot about 2.5 faster and use less resources for doing builds.
In addition it will support connectivity to GitHub directly integrated through oAuth.
The reason for creating a new buildbot is that the our current buildbot is using a very old buildbot version that is hard to maintain (old not supported code). It ha also serious limitations, for example it can't use the git protocol for protected branches.
The new buildbot configurations will largely use native Dockets. This will make the new buildbot about 2.5 faster and use less resources for doing builds.
In addition it will support connectivity to GitHub directly integrated through oAuth.
The reason for creating a new buildbot is that the our current buildbot is using a very old buildbot version that is hard to maintain (old not supported code). It has also serious limitations, for example it can't use the {{git}} protocol for protected branches.
The new buildbot configurations will largely use native {{Dockers}}. This will make the new buildbot about 2.5 faster and use less resources for doing builds.
In addition it will support connectivity to {{GitHub}} directly integrated through {{oAuth}}.
Task
Major
Replaced by MDBF-880