Build Process Instructions

https://confluence.symas.com/display/SIK/%5BDRAFT%5D+Build+Procedure+-+Symas+OpenLDAP

Build Servers

Host Type

dhimay.rb.symas.net RHEL4 64bit

dayaereh.rb.symas.net RHEL4 64bit

scraper.rb.symas.net RHEL5 64bit

bockadabock.rb.symas.net RHEL6 64bit

darbuka.rb.symas.net Debian 6 32bit

davul.rb.symas.net Debian 6 64bit

dongson.rb.symas.net Debian 5 32bit

dholak.rb.symas.net Debian 5 64bit

afoxe.rb.symas.net OpenSuSE 12 64bit

crotale.rb.symas.net Debian7 64bit

Archive Steps

SSH to crwth.ext.symas.net
SSH to build machine
ls -lS /home/build to list all files by sizes
Contact large file owners and request permission to archive
Tar files to be archived (note: run as sudo to compact all jobs)

cd /home/build

sudo tar czf symas.tgz symas-/*

SSH to crwth.ext.symas.net and browse to /BUILD_ARCHIVE/RHEL4 (or OS specific folder) (archive storage location)
Download file from build box to crwth.ext.symas.net using the following command:

sudo scp jtrupp@:/home/build/.tgz .

Enter password

Rename to SOL format using sudo mv

Browse to /home/build folder on buildbox and delete all files archived including .tgz file

***NOTE: Complete this step before proceeding with the build!

Prep Steps

SSH to crwth.ext.symas.net
SSH to build machine
CD /home/build

Make sure that there are no pre-existing installs of SOL or SUUM. They will break the build! To do this run the following command for build type:

    RHEL & SuSE 

                 rpm -qa | grep symas 

    Debian 

                 dpkg --list|grep symas 

    Solaris 

                 pkginfo | ggrep -Ei '(symas|suum)' 

    HP-UX 

                 (not specified) 

    TODO 

                 (not specified) 

    AIX 

                 lslpp -l | grep symas

You will also need to clean up /tmp due to a perftools bug. The following line removes all the perftool stuff and more:
```
    sudo rm -rf /tmp/lt-heap* /tmp/sampling_test_dir /tmp/pprof* /tmp/perftool* /tmp/heap_profile_info /tmp/krb* 
```
Check that you have enough free space for the build. (Off-hand 3 gigs is a medium estimate)
```
    sudo df -h 
```
If releases are not already on build machine, copy them from crwth:/tmp//<#>/***.tgz to /home/build

sudo scp crwth:/tmp//<#>/.tgz /home/build/

Make sure Release Notes are updated

    In Stash (Sold/RelNotes.txt) 

    Use Diff to see changes 

    vl RelNotes.txt 

                 Add any changes necessary, save and exit

Build Steps

Pull in new build source using git clone command included in build request email

 Example: git clone --recursive ssh://git@stash.symas.com:7999/sold/sold.git sold-2.4.42.1

CD to build directory (sold-2.. created by git clone command)
Checkout the build
```
 Example: git checkout symas-2.4.42.1 
```
Download submodule updates by running following command:
```
 git submodule update 
```

***NOTE: Notify Matt if errors encountered during this process

Enter git status to see branches
CD into branch to see what submodules have been updated

With multitail installed:

 make #first make that will err 

 make > build.log 2>&1 && make test > test.log 2>&1 & 

 touch test.log; multitail -cs -i build.log -cs -i test.log

Without multitail:

 make #first make that will err 

 make > build.log 2>&1 && make test > test.log 2>&1 & 

 touch test.log; tail -f build.log -f test.log

Regenerate version.var by running following command:

 make (regenerates version.var and exits) 

 nohup make > make.log 2>&1 &

Build Check

Assuming everything finishes you’ll want to take a look at your log files. Build.log should finish with a list of system packages and .info files. Test.log should finish with an announcement that all tests passed. Note that on machines that build for multiple architectures test.log is a concatenation of the testing for both.

Run this command for respective environment:

 Linux: 

      grep -B 1 -A 1 -E '([>=])\1{2,}' test.log -n --color=always| grep -iE 'fail(ed)?' --color -A 2 -B 1 

 Solaris: 

      ggrep -B 1 -A 1 -E '([>=])\1{2,}' test.log -n --color=always| ggrep -iE 'fail(ed)?' --color -A 2 -B 1 

 Normal Failures: 

      Three failures of test_nist2 in heimdal.  Same failure we always see. 

      One failure of test058-syncrepl-asymmetric for bdb in the nonopt package

Running individual tests:

 Find copies of the test run binary. 

 In the base of the build directory type: 

      find . -name run 

 Choose which 'run' to use based on what failed then execute the test: 

      ./run <testname>

Core File Check

 Core files are often generated when a test fails and can point you towards the problem area. Often, with OpenLDAP projects, there is already a patch  

 for the issue upstream. 

 In the base of the build directory run: 

      find ./build/ -name core\* -type f |xargs file |grep -E '(core file|empty)' 

 NOTE: Currently having a slew of core dumps from the perftools tests is ""normal"". We only use libtcmalloc but this SHOULD be fixed at some point.