Changes between Version 3 and Version 4 of SettingUpABuildServer


Ignore:
Timestamp:
10/30/12 11:49:15 (9 years ago)
Author:
jdreed
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SettingUpABuildServer

    v3 v4  
    1   1. Install either Debian testing (or stable, if it's new enough, but 
    2      see the note about sbuild below) or the latest Ubuntu release. 
    3      The build server must be installed with free space in an LVM 
    4      volume group.  The build chroots consume 4GB each. 
     1 = Setting Up A Build Server = 
    52 
    6 As of Oct 2012, we're using Precise, and we should prefer an Ubuntu LTS to Debian testing or unstable or experimental, per Ops' preferences. 
     3 *Note:* Every effort should be made to ensure that we use stock versions of the build tools wherever possible.  Where we can't, ensure that detailed build instructions, as well as a list of patches we apply, are available.  As of October 2012, we use stock versions of sbuild and schroot. 
    74 
    8   2. Install debathena-login as per the the instructions in 
    9      http://debathena.mit.edu/install. 
     51. The build server should ideally be an Ubuntu LTS (as of Oct 2012, Precise).  Ops prefers Ubuntu to Debian testing/unstable/experimental because they already maintain Ubuntu LTS servers (the dialups).  It should have free space in an LVM volume group (ideally named "builder", but configurable in most cases).  The build chroots consume 4GB each, and there are 2 architectures for each distro we support.  As of Oct 2012, a 50G LVM is sufficient, but this may change in the future. 
    106 
     72. Install debathena-login, as well as debathena-debian-dev. 
     8 * If you install debathena manually (please don't), ensure that you add the apt key, either via the debathena-archive-keyring package, or with `apt-key add /afs/sipb.mit.edu/project/debathena/apt/debathena-archive-keyring.asc`.  If you're very paranoid, you can run apt-key export on the old build server and then apt-key add on the new one. 
    119 
     103. Install the packages listed in scripts/build-server/packages.  debathena-debian-dev should have taken care of most of these.   
    1211 
    13 add the apt-key (though 
    14   3. apt-key add 
    15      /afs/sipb.mit.edu/project/debathena/apt/debathena-archive-keyring.asc 
     124. If we're still using a unioning filesystem, ensure that the necessary kernel modules are available.  See above about using stock versions wherever possible.  As of Oct 2012, the filesystems we use (overlayfs) and those we used in the past (aufs) are part of the stock kernel. 
    1613 
    17 For maximum paranoia, run apt-key export on the old build server and then apt-key add on the new one. 
     145. Append to /etc/approx/approx.conf the contents of `scripts/build-server/approx.conf.tail`.  Restart approx (as of precise, approx is run from inetd). 
    1815 
    19   4. Install the packages listed in scripts/build-server/packages 
    20      (using "aptitude install"). 
    21  
    22 Or apt-get install, until aptitude becomes less stupid about Multiarch support. 
    23  
    24      Note that currently the build system uses the latest version of 
    25      sbuild, so if you have not installed Debian testing, you'll need 
    26      to set up apt pinning to grab sbuild from there. See the 
    27      apt_preferences man page. You'll also need to grab schroot from 
    28      Debian experimental. 
    29  
    30 Also, WTF, why are these not part of debathena-build-depends or debathena-debian-dev or whatever? 
    31  
    32   5. Install the aufs-modules-2.6-amd64 package. 
    33  
    34 No, we now use overlayfs.  Also, both overlayfs and aufs are in the standard kernel packages. 
    35  
    36  
    37   6. Append to /etc/approx/approx.conf the contents of 
    38       scripts/build-server/approx.conf.tail. 
    3916     Run: /etc/init.d/approx restart 
    4017