User talk:Snoble

Set up

Local developer environment

$ cat /etc/profile.d/smebuild.sh

# Developer environment
# This gets symlinked into /etc/profile.d 

export CVS_RSH=ssh # tell CVS to use ssh

# DO NOT set CVSROOT

alias rm='rm -i'
alias cp='cp -i --preserve=timestamps'
alias mv='mv -i'

Access to build system

$ yum install --enablerepo=smedev plague-client

# ask admin@contribs.org for certificates, 
# give email address to use for notifications, and to be subscribed to lists

# cp certs and config to ~/
.plague-client.cfg
.username.pem
.contribs-upload-ca.pem
.contribs-server-ca.pem

# check access
$ plague-client list_builders

Builders:
------------------------------------------------------------------------------------------
 build64-1.contribs.org      x86_64 amd64 ia32e noarch i386 i486 i586 i686 athlon available
 build32-1.contribs.org      i386 i486 i586 i686 athlon noarch  available

if local username is different to sf.net username

$ cat ~/.ssh/config
Host  smeserver.cvs.sourceforge.net
User  sfusername
Host  smecontribs.cvs.sourceforge.net
User  sfusername

$ chmod 600 ~/.ssh/config

Usage

Import cvs code (not source code)

mkdir ~/smeserver
cd ~/smeserver
cvs -z3 -d:ext:smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P rpms 
cd rpms
cvs -z3 -d:ext:smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P common 

mkdir ~/smecontribs
cd ~/smecontribs 
cvs -z3 -d:ext:smecontribs.cvs.sourceforge.net:/cvsroot/smecontribs co -P rpms 
cd rpms
cvs -z3 -d:ext:smecontribs.cvs.sourceforge.net:/cvsroot/smecontribs co -P common

Go to work

mezzanine, mzsfget, mzclean, mzprep, mzpatch, mzbuild, mzput have all be replaced with a new method

commands mostly used are below, details to be added after more usage

make sources
make local
make prep
make srpm
make tag
make build
make clean
make patch SUFFIX=<stuff>

# cd to work directory
cd smecontribs/rpms/smeserver-foo/contribs7

#

Workflow

Once the server successfully builds it will automatically be pulled on the next repo update run (40 past the even hours MDT). The package will either be put into the smedev (new package) or smetest (exist in higher repo) After verification the package is manually moved from smedev/smetest to smecontribs/smeupdates-testing

Check updates/status on the build server: http://buildsys.contribs.org

Contents