[OpenAFS-devel] Transistioning to buildbot 1.x

[Michael Meffie]

Hello All,

We are in the process of transitioning to a modern version of buildbot for the
OpenAFS buildbot master hosted by MIT at buildbot.openafs.org.

The buildbot version 0.8.x setup by Jason Edgecombe has served us well over the
years, however we are long overdue for an upgrade. Since this time the
buildbot project has released a 1.0 version with major changes and some
incompatibilities requiring us to transition the buildbot master to a modern
version.

Starting with buildbot version 0.9, the buildbot project has deprecated the
term "buildbot slave" and transitioned to the new "buildbot worker"
terminology. Protocol changes have been made, however buildbot master version
1.x supports old buildbot slaves as well as modern buildbot workers. The
buildbot master version 0.8.x we are currently running only supports the legacy
buildbot slaves.

A new buildbot master[1] version 1.3 has been installed on buildbot.openafs.org
donated by MIT, running side-by-side the old buildbot master during this
transition. The new master is listening on a non-default port in order to run
side-by-side with the old master. We plan on testing out the new buildbot
master and the gerrit integration with a few slaves/workers for a few weeks.

After a test period, we will be shutting down the old master and changing the
ports so the existing buildslaves will start using the new buildbot master,
hopefully transparently.

The master configuration has been ported to the new version and is being
maintained on github[2] on branch buildbot-1xx.

Thanks goes to Ben Kuduk and the staff at MIT for assisting in this upgrade.

Thanks,
Mike

[1]: http://buildbot.openafs.org:8011
[2]: http://github.com/openafs-contrib/afsbotcfg

[Garrett Wollman]

Post by Michael Meffie
Starting with buildbot version 0.9, the buildbot project has deprecated the
term "buildbot slave" and transitioned to the new "buildbot worker"
terminology. Protocol changes have been made, however buildbot master version
1.x supports old buildbot slaves as well as modern buildbot workers. The
buildbot master version 0.8.x we are currently running only supports the legacy
buildbot slaves.

Note that the FreeBSD buildbot that I was operating stopped working a
year or more ago because of this change. I eventually shut the VM
down since it could not work with a 0.8 master. (That VM was outdated
anyway; once this transition is made I could spin up a variety of VMs
with more modern FreeBSD releases on them.)

-GAWollman

[Michael Meffie]

On Fri, 10 Aug 2018 13:02:19 -0400

Post by Garrett Wollman

Post by Michael Meffie
Starting with buildbot version 0.9, the buildbot project has deprecated the
term "buildbot slave" and transitioned to the new "buildbot worker"
terminology. Protocol changes have been made, however buildbot master version
1.x supports old buildbot slaves as well as modern buildbot workers. The
buildbot master version 0.8.x we are currently running only supports the legacy
buildbot slaves.

Note that the FreeBSD buildbot that I was operating stopped working a
year or more ago because of this change. I eventually shut the VM
down since it could not work with a 0.8 master. (That VM was outdated
anyway; once this transition is made I could spin up a variety of VMs
with more modern FreeBSD releases on them.)

Thank you Garrett.

Let me know if you are in a position to try out the new buildbot master
before we completely turn off the old buildbot master. The only change
should be to set the buildbot worker to use the default port number 9986.

Best regards,
Mike

[Derek Atkins]

Post by Michael Meffie
Let me know if you are in a position to try out the new buildbot master
before we completely turn off the old buildbot master. The only change
should be to set the buildbot worker to use the default port number 9986.

Do you want me to change the F28 slave to the new master?

Post by Michael Meffie
Best regards,
Mike

-derek

[Michael Meffie]

On Wed, 15 Aug 2018 11:02:37 -0400

Post by Derek Atkins

Post by Michael Meffie
Let me know if you are in a position to try out the new buildbot master
before we completely turn off the old buildbot master. The only change
should be to set the buildbot worker to use the default port number 9986.

Do you want me to change the F28 slave to the new master?

Hello Derek,

Yes please, that would be a useful test.

I've new master config to have the same name/password. You can change the
port number to 9986 in the buildbot.tac file and restart the worker.

Best regards,
Mike

[Derek Atkins]

Post by Michael Meffie
Hello Derek,
Yes please, that would be a useful test.
I've new master config to have the same name/password. You can change the
port number to 9986 in the buildbot.tac file and restart the worker.

Done.

Seems to be in better shape now, but not doing anything of note.

Post by Michael Meffie
Best regards,
Mike

-derek

[Pat Riehecky]

Any chance we can add a regular run of cppcheck to master?

https://docs.buildbot.net/latest/manual/cfg-buildsteps.html#id44

Post by Michael Meffie
Hello All,
We are in the process of transitioning to a modern version of buildbot for the
OpenAFS buildbot master hosted by MIT at buildbot.openafs.org.
The buildbot version 0.8.x setup by Jason Edgecombe has served us well over the
years, however we are long overdue for an upgrade. Since this time the
buildbot project has released a 1.0 version with major changes and some
incompatibilities requiring us to transition the buildbot master to a modern
version.
Starting with buildbot version 0.9, the buildbot project has deprecated the
term "buildbot slave" and transitioned to the new "buildbot worker"
terminology. Protocol changes have been made, however buildbot master version
1.x supports old buildbot slaves as well as modern buildbot workers. The
buildbot master version 0.8.x we are currently running only supports the legacy
buildbot slaves.
A new buildbot master[1] version 1.3 has been installed on buildbot.openafs.org
donated by MIT, running side-by-side the old buildbot master during this
transition. The new master is listening on a non-default port in order to run
side-by-side with the old master. We plan on testing out the new buildbot
master and the gerrit integration with a few slaves/workers for a few weeks.
After a test period, we will be shutting down the old master and changing the
ports so the existing buildslaves will start using the new buildbot master,
hopefully transparently.
The master configuration has been ported to the new version and is being
maintained on github[2] on branch buildbot-1xx.
Thanks goes to Ben Kuduk and the staff at MIT for assisting in this upgrade.
Thanks,
Mike

[Michael Meffie]

On Tue, 21 Aug 2018 13:20:55 -0500

Post by Pat Riehecky
Any chance we can add a regular run of cppcheck to master?
https://docs.buildbot.net/latest/manual/cfg-buildsteps.html#id44

Hi Pat,

Sure thing. We just need a buildbot-worker that has cppcheck
installed. I could add that to the exisiting machine that
is running the clang-static analyzer when I move it to the
new buildbot master, or if you have a machine you can provide
to run a buildbot-worker and has cppcheck installed, I can
update the new master config to run cppcheck nightly with
the buildbot step you pointed out.

Best regards,
Mike

[Pat Riehecky]

Post by Michael Meffie
On Tue, 21 Aug 2018 13:20:55 -0500

Post by Pat Riehecky
Any chance we can add a regular run of cppcheck to master?
https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.buildbot.net_latest_manual_cfg-2Dbuildsteps.html-23id44&d=DwICAg&c=gRgGjJ3BkIsb5y6s49QqsA&r=OAMtP0DWou0nlXG7Kmxo2enjXJfwb1DXS9fwcaESuTE&m=FNlHvZekkypI4nUxzRLqNgc1hb4rzSKm6-YTFoh0P_Q&s=y9d0E8IE8leezCFXgLc0pSfE246oYOoZDG3I5pRi7_w&e=

Hi Pat,
Sure thing. We just need a buildbot-worker that has cppcheck
installed. I could add that to the exisiting machine that
is running the clang-static analyzer when I move it to the
new buildbot master, or if you have a machine you can provide
to run a buildbot-worker and has cppcheck installed, I can
update the new master config to run cppcheck nightly with
the buildbot step you pointed out.
Best regards,
Mike

Alas, I've not got any hardware for this, it should be safe to run on
the same host that is running clang-static.

Pat