# cd /opt/cruisecontrol-bin-2.6
 
# ./cruisecontrol.sh

Top stop (aka Kill) CruiseControl use the UNIX command ‘ps’ to view the processes and corresponding process IDs as shown on this post on the source forge forums.

Find which PID (Process ID) you want to stop/kill type

 # ps -e

I dont know what the -e switch is for but from what I can tell it displays all the running processes in the system as opposed to just #ps which displays a limited list. If you want a more verbose list the type in

 #ps -e -f

(again I don’t know what the -f) switch is for, but it will return back to you even more information about the ongoing processes in your system. From here you can stop/kill the process you want based off the the displayed PID.

 # kill -9 'XXXX'

where ‘XXXX’ is the associated PID for the CruiseControl process you want to kill

Not all of these steps are required to get CruiseControl up and running on your server, but Im going to be posting more on setting up a full CI machine using CruiseControl so I figured, lets get everything on the box from the beginning so we don’t have to keep downloading and installing things. Lets get started…

Step 1
For easy cleanup create a tmp / download folder. We will move files around as we need to, but this way when we are done we can easily remove this folder for a quick and easy cleanup.

#mkdir /var/tmp

Step 2
Download the files your going to use in your installation.

Download CruiseControl from: http://cruisecontrol.sourceforge.net/download.html I used version 2.6 and downloaded it directly to my server using wget http://downloads.sourceforge.net/cruisecontrol/cruisecontrol-bin-2.6.zip?modtime=1168552955&big_mirror=0 into my /var folder

#cd /var/tmp
#http://downloads.sourceforge.net/cruisecontrol/cruisecontrol-bin-2.6.zip?modtime=1168552955&big_mirror=0

Download the FlexAntTasks

#wget http://weblogs.macromedia.com/pmartin/tooling/flexunit/FlexAntTasks.jar

Download Opera, I used Opera, but feel free to use mozilla, either one will be fine and wont change this walk through. Download Opera locally from here http://www.opera.com/download/ then upload it to your server /var/tmp folder.

Download the Linux Flash player from Adobe’s site and this one your going to want to download locally first then upload to your server. http://www.adobe.com/go/getflashplayerlinux

Downloading the Flex 3 SDK. A quick way to do this is go to http://www.adobe.com/products/flex/flexdownloads/index.html the first choice is the Flex 3 SDK, agree to the terms of the download, this will expose the download link.
Copy the link location for the sdk download and use a #wget to directly download this file into your server (I dont know if I can post this link directly here so I’m just showing a portion of it)

#wget http://download.macromedia.com/pub/flex/sdk....

Download the Java JDK from sun’s download site http://java.sun.com/javase/downloads/index.jsp I went with jdk 5 release 15 which you can download directly to your server

#wget http://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_Developer-Site/en_US/-/USD/VerifyItem-Start/jdk-1_5_0_15-linux-i586.bin?BundledLineItemUUID=RPhIBe.osm0AAAEaIc1xwMqB&OrderID=4H5IBe.o6LEAAAEaCs1xwMqB&ProductID=yL7ACUFBjqYAAAEYees5AXuQ&FileName=/jdk-1_5_0_15-linux-i586.bin

Download virtual frame buffer, at this point we don’t have to download this file, assuming you have YUM installed then we will be able to simply yum install it later on. If you do not have YUM installed then you should install it for this and many other reasons.

Step 3
Install CruiseControl by extracting the zip file and copying it to the /opt folder

#cp cruisecontrol-bin-2.6.zip /opt/cruisecontrol-bin-2.6.zip
#unzip /opt/cruisecontrol-bin-2.6.zip

Installing the JDK was fairly simple, one thing to note though which stumped me is that, where you extract the jdk is where is gets installed so pick your folder wisely I chose /usr/java. You can find more information on installing and configuring java jdk in linux here

#cp jdk-1_5_0_15-linux-i586.bin /usr/java/jdk-1_5_0_15-linux-i586.bin
#cd /usr/local

You’ll need to make this folder executable

#chmod +x jdk-1_5_0_15-linux-i586.bin

Now run the installer

./jdk-1_5_0_15-linux-i586.bin

Now that java is installed you will need to configure your Java Home, you can find more information on this here. You can set your Java Home by adding the export path to your bash profile.

#vi ~/.bash_profile

add in the lines:

	export JAVA_HOME=/usr/java/
	export PATH=$PATH:/usr/java/jdk1.5.0_07/bin

save and close this file and to see your changes you’ll need to log out and log back in.

At this point we have CruiseControl and Java installed, now we need to install Opera, we need to do this step before we can install the flash player because the flash player installer will require either Mozilla or Opera to be installed.

#cd /var/tmp
#tar -zxvf opera-9.5.tar.gz

Run the Opera installer, this will install Opera to the “/usr/bin/opera” folder, remember or copy this path because you will need it in the next step. If you ever need to get the path of Opera or any application for that matter simply use the #which command which will return back the path to the application

#which opera

Now lets install the linux flash player

#cd /var/tmp
#tar -zxvf install_flash_player_9_linux.tar.gz
#cd install_flash_player_9_linux
#flashplayer-installer

When prompted for the Opera path paste in the path from above.

Last but not least lets install the Virtual Frame buffer needed by Flash to run in linux, we will do this using YUM, again if you do not have YUM I would suggest installing it, as it will make this and many other common installations much much simpler.

yum install Xvfb

Step 4
Now if all goes as planned, or if I haven’t completely butchered this install walk through then you should be able to now start CruiseControl and start using it via your web browser. To start CruiseControl

#cd /opt/cruisecontrol-bin-2.6
# ./cruisecontrol.sh

You should see CruiseControl running in your browser on port 8080 http://YourDomain.com:8080

First thing your going to want to do is grab a copy of YUM if you don’t already had it installed, you can check to see if you have YUM installed by typing #yum in your terminal, if you see something like “Loading “installonlyn” plugin” then you have yum installed and then just skip this step, if you see something like “-bash: yum: command not found” then your going to need to install yum. Start by creating an install directory

Step 1.

#mkdir /usr/local/src/yum
#cd /usr/local/src/yum

next download the yum rpm

#wget http://mirror.centos.org/centos/4/apt/i386/RPMS.os/yum-2.4.3-3.el4.centos.noarch.rpm

now install yum

#rpm -Uvh *rpm

finally update your yum

#yum -y update

If you want to clean up after yourself, you can delete the install directory you created at the begining of this step by

#rm -rf /usr/local/src/yum

now your ready to install Subversion

Step 2.

Install Subversion

#yum -y install subversion

Done! you can test subversion is successfully installed by typing #svnadmin in your console, you should see something like “Type ‘svnadmin help’ for usage.”

Step 3. Now your going to want to configure subversion to work with plesk. I like to keep things separate, so I run my subversion server through a subdomain http://svn.domain.com so this part will walk you through configuring subversion in a subdomain.

Your going to want to make sure thatmod_dav_svn.so is being loaded into your http.conf, to do this type

#vi /etc/httpd/conf/httpd.conf

search for “mod_dav_svn.so” in your LoadModules section

my httpd.conf file has the following lines which you can copy and paste into yours

LoadModule dav_module modules/mod_dav.so
 
LoadModule dav_svn_module modules/mod_dav_svn.so
 
LoadModule authz_svn_module modules/mod_authz_svn.so

once you have done this, save the httpd.conf file [esc + w + q (escape, write, quit)]

Step 4
Next your going to want to create your central repository, lets put it in the /var/www directory

mkdir /var/www/repository

svnadmin create /var/www/repository

note, if you choose not to place your repository in this directory, you may run into an issue I came across where my repositories were not configured for the web, and although the authentication windows would display and svn was running correctly, the web browser wouldn’t show the repos correctly.

After a lot of testing and not getting it to work i read this post: http://www.svnforum.org/2017/viewtopic.php?t=372&postdays=0&postorder=asc&start=15 and it basically said that if your running centos or rehl then there is a known issue on some configurations that causes svn over http not to work due to permissions. this is fixed by putting your repository in the /var/www directory. so my repo is now in /var/www/repository and that worked, this is why I suggested putting the repository in this directory’

now you have a working subversion repository you can start using, but it isn’t accessible to web users yet.

Step 5
Now since plesk will rewrite the main site configuration files every time you use plesk your going to want to write a configuration file in your vhost conf folder

#vi /var/www/vhosts/[you_domain_name]/subdomains/[you_subdomain_name]/conf/vhost.conf

This vhost file will automatically be included in apache’s httpd.conf file. The vhost.conf file will contain the instructions for you subdomain to map to your svn repository.

Edit your vhost.conf file to contain the location of your svn files as shown below

 #svn.yourdomain.com -- vhost.conf file
Location /
DAV svn
 
SVNPath /var/www/repository
AuthType Basic
 
AuthName "Subversion Repository"
 
AuthUserFile /etc/svn-auth-file
Require valid-user
/Location

Save your changes. Now you’ll want to add a valid user to this repository by typing

#htpasswd -c /etc/svn-auth-file my_user_name

whenever you make a change to your vhost files your going to want to restart apache using

/etc/init.d/httpd restart

and there you go… now you should be able to browse to your subdomain and use your repository on your CentOS box running Plesk.

Cheers.