1193920 - Install one version of buildbot at a fixed file location on Windows slaves

Status: RESOLVED DUPLICATE of bug 1198779

(Infrastructure & Operations :: RelOps: Puppet, task)

Description

[Mark Cornmesser [:markco]]

Currently the active buildbot directories are determined by buildslave::install. Currently: 

        "0.8.4-pre-moz7":
            active => true;

The defined resource buildslave::install::version has the logic in it to initiate the python virtual environment and in return to create the directories. Thus far I have not been able to pull the value out of Puppet. This would be useful in cases such as setting the path for runner. For now I am going to hard code the variable in buildslave::install, so that work with deploying runner through Puppet can move forward, and that it will be set in the same place that a newer version of buildbot would be introduced.

Comment 1

[Dustin J. Mitchell [:dustin] (he/him)]

This ability to install multiple versions of Buildbot is "nifty", and works great on Linux, but hasn't been much used -- I think moz2 was the first version we deployed lo those many years ago, and we're only on moz7 now.  Also, support for installing things simultaneously was meant to allow us to switch to a new version (and switch back) rapidly without hammering our pypi mirrors.  With EC2 instances for builders this is a lot less important now.

So, I'd be amenable to the idea of simplifying all of this mechanics to install only ONE version of Buildbot at a fixed filename.  I think it would simplify the Windows stuff substantially!