Usage

The servers on the OpenCSW build farm are to be used exclusively for building packages for the OpenCSW project.
Details to the buildfarms can be found at http://www.opencsw.org/extend-it/contribute-packages/build-standards/build-machines/

This page is for buildfarm admins.

Setting up a build server

To build packages for OpenCSW at least three servers are needed:

1. Solaris 9 Sparc to build 32 bit and 64 bit Sparc binaries
2. Solaris 9 x86 to build 32 bit build x86 binaries
3. Solaris 10 x86 to build 64 bit x86 binaries

• Servers with Solaris 10 Sparc are optional for most of the packages. However, there may be packages which rely on private kernel data (like "top") which needs to be build for each and every Solaris version to run on.
• The user homes should be in /home/<user> and the home directory should be shared between the build machines. This is important for building x86 packages as the 32 bit part needs to be build on Solaris 9 and the 64 bit part on Solaris 10.
• Under /home/experimental/<project>/ are project-specific directories with permissions 0755 which are accessible via http://buildfarm.opencsw.org/experimental.html. experimental/ itself is 01755 and users are free to create new projects as needed.
• The installed packages are listed on http://buildfarm.opencsw.org/versionmatrix.html

Installing Software

All software is archived and available from /home/farm on the bo Buildfarm.
Make sure you deinstall SUNWgmake. That versions is outdated and misses functions needed by GAR (e. g. abspath).

Install Java Package

There are versions of JDK and JRE between Java 1.3 and Java 6 installed in /usr.

• Solaris 9 Sparc: cd /usr; for F in java/*sparc*; do sh $F; done
• Solaris 9 x86: cd /usr; for F in java/*i586*; do sh $F; done
• Solaris 10 Sparc: cd /usr; for F in java/*sparc*; do sh $F; done
• Solaris 10 x86: cd /usr; for F in java/*i586* java/*amd64* java/*x64*; do sh $F; done

Install Sun Studio Compiler

On Solaris 8 the Sun Studio 11 Compiler is installed, on Solaris 9 and 10 both Sun Studio 11 and 12 is installed. Solaris 10 has also Sun Studio 12u1 installed.

Sun Studio 11

1. cd ss11
2. Sparc only: cd /CD1
3. PATH=/usr/j2re1.4.2_17/bin:$PATH ./batch_installer -d /opt/studio/SOS11

Uninstall:

1. cd /var/sadm/prod/com.sun.studio_11
2. ./batch_uninstall_all

Please note: If you have also Sun Studio 12 installed the installer will erranously remove some packages from Sun Studio 12 so you may need to reinstall it after SOS 11 removal.

Sun Studio 12

1. cd ss12
2. ./batch_installer -d /opt --accept-sla

Uninstall:

1. export PATH=/usr/jre1.6.0_20/bin:$PATH
2. cd /opt
3. java -cp . uninstall_Sun_Studio_12 -nodisplay -noconsole

Please note: If you have also Sun Studio 11 installed the installer will erranously remove some packages from Sun Studio 11 so you may need to reinstall it after SOS 12 removal.

Sun Studio 12u1

Headless installation is a bit more complicated here as described in http://docs.sun.com/app/docs/doc/820-7601/gemyt?a=view

Sun Studio Compilers for OpenSolaris

• Sun Studio 12u1
• Sun Studio Express 11/08
• Sun Studio Express 3/09

See here for details.

Don't forget to patch the compilers, with PCA or manually.

Adding Users

From here on in (Jan 2009), we are trying to keep userids in sync across "all" machines. www.opencsw.org is consider the "master".
If a user exists on www, then an account created from them on other machines, should be made to match up userids.

There are some older, legacy, nonmatchedup accounts. To make it easier to identify between newer and older accounts, "cleanly" created accounts are created in the range 17100-18000. Older accounts may be migrated/synced into the range 17000-17099 if desired.

thus, if there is an account created on non-www machines, that is desired to be non-synced, it should be OUTSIDE the range of 17000-18000

The normal process for creating accounts across all machines, is that Phil runs a script on www, which in turn calls scripts maintained by Ihsan and Dagobert, to create accounts on www and buildfarm machines, respectively.

SSH Agent for each user

It is advised to use a passphrase for the SSH key. This can easily be done by using the following steps:

1. Set passphrase on the key

ssh-keygen -p -f .ssh/id_dsa

# executed for interactive shells
if [ "x$HOSTNAME" = "xlogin" ]; then
  if [ -f ~/.ssh-agent ]; then
    source ~/.ssh-agent
  fi

  if [ -z "$SSH_AUTH_SOCK" -o ! -w "$SSH_AUTH_SOCK" ]; then
    if read -q '?Start ssh-agent? (y/n) '; then
        ssh-agent -s >~/.ssh-agent              && \
            source ~/.ssh-agent                 && \
            ssh-add
    fi
  fi
fi

(echo "Host current*"; echo "\tForwardAgent yes") >> ~/.ssh/config

There are similar methods with keychain available:

• GPG, agent, pinentry and keychain