Here is the message I was seeing:

ERROR: Error cloning remote repo 'origin' : Could not clone https://username@github.com/username/repository.git
ERROR: Cause: Error performing git clone -o origin https://username@github.com/username/repository.git /srv/hudson/jobs/repository/workspace
Trying next repository
ERROR: Could not clone from a repository
FATAL: Could not clone
hudson.plugins.git.GitException: Could not clone
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:587)
at hudson.plugins.git.GitSCM$2.invoke(GitSCM.java:535)
at hudson.FilePath.act(FilePath.java:753)
at hudson.FilePath.act(FilePath.java:735)
at hudson.plugins.git.GitSCM.checkout(GitSCM.java:535)
at hudson.model.AbstractProject.checkout(AbstractProject.java:1038)
at hudson.model.AbstractBuild$AbstractRunner.checkout(AbstractBuild.java:479)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:411)
at hudson.model.Run.run(Run.java:1257)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:129)

To solve the problem we need to create an ssh key for the tomcat user so that it can access the repository.

cd /usr/share/tomcat6
sudo mkdir .ssh
cd .ssh/
sudo touch known_hosts
sudo ssh-keygen -t rsa -C "tomcat@forthedeveloper.com"

When creating the key pair save the key to /usr/share/tomcat6/.ssh/id_rsa.

I don’t know how to tell tomcat the passphrase for a ssh key, so I just left the passphrase blank.

Once the key has been created we need to add the github site to the known_hosts file. If you have already setup your normal account for working with github and have xclip installed you can run the following to copy the github ssh host information:

ssh-keygen -F github.com | xclip -sel clip

Edit the /usr/share/tomcat6/.ssh/known_hosts file and paste in the copied host information.

To finish things up:

sudo chown -R tomcat6:tomcat6 /usr/share/tomcat6/.ssh/
sudo /etc/init.d/tomcat6 restart

You can copy the new ssh key for tomcat to your clipboard if you have xclip installed with:

cat /usr/share/tomcat6/.ssh/id_rsa.pub | xclip -sel clip

If you are only using hudson for one repository you can just add the public key to the one repository in the repository admin (ex: https://github.com/username/repository/edit) under the ‘Deploy Keys’ area. Otherwise you can add it to your account’s ‘SSH Public Keys’ to allow the tomcat server access to all of your repositories.

Now when you run hudson against your private github repository it should have the proper access.


Caused by: hudson.plugins.git.GitException: Command returned status code 128:
*** Please tell me who you are.

Run

git config --global user.email "you@example.com"
git config --global user.name "Your Name"


I was a little confused to see this message since I had already configured git to have my user name and email. Then I remembered that hudson is running on tomcat which is running with the tomcat6 user. I needed to configure the tomcat6 user to have the git configuration necessary to tag on the git repositories.

[UPDATE: 24 Jun 2010]

I was working on repeating this process on Ubuntu 10.04 and was getting permission errors running the command to set the git config for the tomcat6 user. Here is an updated method:

First we need to create a .gitconfig file for the tomcat6 user:


sudo touch /usr/share/tomcat6/.gitconfig
sudo chown tomcat6:tomcat6 /usr/share/tomcat6/.gitconfig
sudo nano /usr/share/tomcat6/.gitconfig


Place the following in the .gitconfig file:


[user]
name = Hudson
email = hudson@myDomain.com


Once the file is saved–you may need to restart Tomcat–it should pick up your git configuration.

[/UPDATE]

[ORIGINAL: see updated instructions above]

Setup the git configuration for the tomcat6 user by doing the following:


sudo -s -H -u tomcat6
git config --global user.name "Hudson"
git config --global user.email "hudson@mydomain.com"
exit


As a note, if you are using hudson to commit and push to another repository these configuration settings will be used for all commits done by Hudson.

The next step is to let hudson know where the HOME is for the tomcat6 user. On the hudson/configure page there is a checkbox for defining environment variables. Once it is checked you will be able to put in a key-value pair. Add the following pair and save your configuration:


name: HOME
value: /usr/share/tomcat6/


The next time a hudson project is built you should see the following line close to the top of the console output:

Env: HOME=/usr/share/tomcat6/

[/ORIGINAL]

The git plugin should now be able to successfully tag the repository and continue with the build.

Step 1: Download Needed Files

The first step is to download all the files you will need. Since the downloads usually take some time we’ll get them out of the way first.

For my installation I wanted to get more familiar with the Server edition of Ubuntu and to require fewer resources. You should be able to do a similar installation with the Desktop edition.

• Download VirtualBox – The official VirtualBox download page.
• Download Ubuntu – To download the Server edition you will need to find a mirror that hosts the installer images. Once you find a mirror navigate to the 9.10 directory and find the download link for the ubuntu-9.10-server-i386.iso file.
• Download ColdFusion – The official Developer Edition Download is available on the Adobe ColdFusion page. Download the Linux 32 bit installer.

Step 2: Install VirtualBox

Once you have downloaded all the files, run the VirtualBox installer.

If you would like to learn more about VirtualBox the installation comes with a user manual or you can download a pdf copy from their download page.

Step 3: Create an Ubuntu Virtual Machine

Click the New icon in VirtualBox to start the wizard for adding a new VM.

1. Click Next to start the wizard.
2. Enter Ubuntu CF for the Name of the VM.
3. Select Linux and Ubuntu in the OS Type drop downs.
4. Click Next.
5. Click Next to accept the default amount of RAM. (You can adjust if you want to…)
6. Click Next to create a new hard disk image to use for the VM.
   1. Click Next to start the wizard .
   2. Click Next to create a dynamically expanding storage.
   3. Click Next to accept the default name and size.
   4. Click Finish to accept the choices for the disk image.
7. Click Finish to end the wizard.

Step 4: Install Ubuntu

Now that there is a VM setup to hold the guest Ubuntu system we need to install Ubuntu on it.

In VirtualBox Double Click on the Ubuntu CF listed in the left column to start up the VM. Since this is the first time you are starting the VM it will bring a up a First Run Wizard to guide you in setting up the new VM.

1. Click Next to start the wizard.
2. Change the Media Source to Image File and click the Other... icon.
   1. Click the Add icon along the top.
   2. Select the ubuntu-9.10-server-i386.iso file we downloaded earlier.
   3. Click Select with the ubuntu-9.10-server-i386.iso item selected.
3. Click Next to continue.
4. Click Finish to end the wizard.

The VM should now startup and bring up the installation the Ubuntu. I’m not going to go into the details of installing Ubuntu here, so just continue with the next step once Ubuntu installation is complete. Also, since we are going to be using apache you may wish to have the setup create a LAMP server configuration when choosing features or you can install it manually afterwards.

Step 5: Setup Guest Additions

In order to have the Shared Folders work we will need to install the Guest Additions.

Before we install the Guest Additions we will need to install dkms:

sudo apt-get install dkms

To mount the Guest Additions disc image to the VM press Command + D or select Devices > Install Guest Additions... from the VM menu. Then install the Guest Additions by running:

cd /cdrom

sudo sh ./VBoxLinuxAdditions-x86.run

Step 6: Setup Shared Folders

One of the goals when creating the virtual machine was to be able to edit the files natively but run them on the guest operating system that reflects the production environment.

With shared folders we are able to use a local directory as a share on the guest VM.

Before we add the shared folder we need to have a folder to share. For this example I’m using the directory I created at /Users/randy/Documents/cf9/.

With the VM powered off edit the Settings and select the Shared Folder icon.

1. Click the Add a new shared folder definition icon on the right side.
2. Enter the Folder Path (/Users/randy/Documents/cf9/) or select Other... from the drop down and locate the directory.
3. Enter the name you would like the share to be referenced as in the Folder Name field. In this case I am going to call it cf9.

Now that we have the shared folder available to the VM we want it to mount the share each time the VM starts. To do this we startup the Ubuntu VM and edit the /etc/fstab file and add the following line at the end of the file (note that you will need to change the username to match your user):

cf9	/home/randy/Documents/cf9	vboxsf	uid=randy,gid=users	0	0

You will also need to create a blank directory at /home/randy/Documents/cf9 that the share will mount to.

The next time your VM is started it should have access to /Users/randy/Documents/cf9 on the host machine at /home/randy/Documents/cf9 on the guest machine.

Step 7: Enable Port Forwarding

To setup the port forwarding you will need to stop the VM. In the terminal run the following commands to setup the port forwarding. (Note that "Ubuntu CF" needs to match the name of the VM created above.)

VBoxManage setextradata "Ubuntu CF" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guesthttp/Protocol" TCP
VBoxManage setextradata "Ubuntu CF" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guesthttp/GuestPort" 80
VBoxManage setextradata "Ubuntu CF" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/guesthttp/HostPort" 8580

This will change the VM settings to have the guest port of 80 (which is the default apache port) of the guest forwarded to port 8580 on the host. Without this you would not be able to talk to the guest operating system.

Step 8: Install ColdFusion

Since we already downloaded the installer for ColdFusion we just need to get that file to the VM. Luckily we already setup a shared folder so if you move the installer to the /Users/randy/Documents/cf9/ directory it will be available in the VM.

To run the ColdFusion installer:

cd /home/randy/Documents/cf9/

chmod +x ColdFusion_9_WWE_linux.bin

sudo ./ColdFusion_9_WWE_linux.bin

This should start the installer. During the installation, apache should be configured to run with ColdFusion.

Step 9: Test Environment

To test that the development environment is working correctly you should be able to place an index.cfm file in your /Users/randy/Documents/cf9/ directory. Make sure that you place some CFML in the file to test that ColdFusion is doing it’s thing. Then visit http://localhost:8580/ in a browser on your host to test out the new development environment!

Using the Sun Java

I started off by doing your standard Google search and came up with this page listed promently on the Ubuntu community site:

https://help.ubuntu.com/community/EclipseIDE

I followed the instructions to get the Java 6 from Sun installed on the system. But I stopped after the install of Java 6 since my install is basically a download of eclipse it wasn’t going to have the /etc/eclipse/java_home that was described on the community page.

With a little more searching I came across this page which gave a brief description his installation. From his post I edited my ~/.bashrc file and added in the export JAVA_HOME=/usr/lib/jvm/java-6-sun/ so that my default JAVA_HOME would be the sun java.

Getting Eclipse

To get the latest eclipse distribution I went to the eclipse download page and downloaded the eclipse classic, my preferred base distro. Once I had the file I extracted the eclipse directory. I’m not a linux guru and didn’t know the ‘best’ place to put the eclipse directory so i put it in /opt/.

Running Eclipse

Once I had the application in the directory I decided to add it to my applications menu. I did so by right clicking on the ‘Applications’ menu and selecting the ‘Edit Menus’ option. From there I went into the Applications > Programming menu on the left side and created a ‘New Item’. I chose the type of ‘Application’ and a name of ‘Eclipse’. For the command I entered ‘/opt/eclipse/eclipse -vm /usr/lib/jvm/java-6-sun/bin/java’ just to make sure that eclipse was being loaded with the correct jvm.

Using Eclipse

So far I have not had any problems with any of the plugins that I commonly use (CFEclipse, Subclipse, etc) that aren’t found on all system.

That’s what I did to get Eclipse 3.4 Ganymede running on Ubuntu 8.04.1 Hardy Heron, so enjoy!

I was thinking today of how many crazy things that I try to do, how many of them don’t work, and how many of them I don’t share when they do. So today I attempt to share a successful install of ColdFusion 8 (developer version) on my Ubuntu 8.04 64-bit box.

For this installation I am going to connect it to my apache 2 installation. So if you do not have apache or do not want to connect it to apache then just skip that part.

To start off I downloaded the coldfusion-801-lin64.bin file from Adobe.

Once I had the file I made it executable:

$ sudo chmod +x coldfusion-801-lin64.bin

Now it is time to run the installer:

$ sudo ./coldfusion-801-lin64.bin

At first the installer extracts the files for installation then brings up the menu to select the locale. I speak only english so luckily there was the option for english.

Next they give you a nice introduction telling you that you are installing ColdFusion and you can go back in the installer by typing ‘back’ and you can exit the installer by typing ‘quit’. ( I pressed ‘enter’. )

Next we go through the wonderful License Agreement for using ColdFusion. You should probably read it, but since I am only installing the developer version I didn’t pay much attention and pressed enter a lot until I got to the question of if I accept. Then I pressed ‘Y’ and ‘enter’.

Next the installer goes through a pre-installation check to see if your computer has everything that is needed by ColdFusion. My box unfortunately pulled up a warning telling me:

The installer was unable to determine if libstdc++.so.5 is available. The library is necessary for C++ custom tags, webservices and some cfimage functionality to work properly.

When I checked my packages I have libstdc++6 installed. I’m no linux guru, just trying to learn more about it, but I continued the installation in spite of the warning. I’ll write a new post later if this comes back to bite me. So I pressed ‘enter’ and ignored the warning.

For my wonderful installation attempt I chose to select the Developer Edition since I am not rich and this is only for local development anyways. If you are rich, or want to install any of the other options, go ahead, I just may not have the same options that you do.

Next it asks for the installer configuration that I would like to use. At first I thought that I would like to go with the multi-server install, but I have tried playing around with it in the past and it just seemed overkill for what I wanted to do for my development so I chose to do just a regular ‘server configuration’. I also found it interesting they decided to include a second semi-colon on this menu, adds a nice touch.

Ofttimes it doesn’t do well to have ColdFusion already installed and install it again. So the next step asks to make sure you don’t already have ColdFusion installed. I do not so i answer no.

The next part is where you get to do whatever set of addons you want. For my install I did not want the documentation since I use livedocs, and I didn’t want LiveCycle and Search Services since they would be overkill and overhead. I also removed the option to start ColdFusion on system init since I am not always developing on it and plan on having a bash script to start it up and shut it down when needed.

I went with the default for the install directory ( /opt/coldfusion8 ). I have no reason to change it and don’t know enough about linux to slap myself for doing it.

No previous version of ColdFusion installed so the next option was a no.

Configuring webservers is what I have had the most trouble with while trying to install ColdFusion before so I’ll see if I can get it right. I selected  the ‘Add Web Server Configuration’ option to try and attach it to apache.

I am running apache so I selected the ‘Apache’ option.

If you would like a handy reference for where your files are for apache check out this post from the crumb.

Next it asks for the directory that contains the httpd.conf file. On this box that the path is:

/etc/apache2

Next is asked for the binary file for apache:

/usr/sbin/apache2

And for the control file used to start and stop apache:

/usr/sbin/apache2ctl

Next it shows the menu about web server configuration. But since I have done my damage I just tell it to ‘Continue with Installation’.

For the administrator location I chose ‘/var/www’ so that it is out there where I can get to it without a lot of changes.

The runtime user is something that I wasn’t sure of, but one of my sys-admin friends told me to use the www-data user for it so that is what i used.

My password for my home dev server I put as ’1d10t’. And if you want to buy some nice insurance I know a guy….

RDS is one of those things that you hear about… but just never used. At least it is for me. So this time I am going to try out the RDS option this time and see what it can do for me. For that password I chose ‘t01d1′.

Now it shows the installation summary of what it is about to do.

Installation Type:
Server configuration

Licensing:
Developer Edition

Installation Directories:
Product: /opt/coldfusion8
Web root: /var/www

Server Information:
Web Server: Apache (/etc/apache2)
Port:
Search Services: not installed
Adobe LiveCycle Data Services ES: not installed
Documentation: not installed
RDS: enabled

Disk Space Information (for Installation Target):
Required: 432,138,779 bytes
Available: 198,957,346,816 bytes

Press enter and it whirls away in ASCII to install your ColdFusion 8 server.

Yeah:

You have successfully completed the first step in installing Adobe ColdFusion 8.

To continue with your installation, go to /opt/coldfusion8/bin and type "./coldfusion start" to start your server.

Once the server, is started log in to the Configuration Wizard at http://[machinename]/CFIDE/administrator/index.cfm

Next to see if the ColdFusion server will startup.

$ cd /opt/coldfusion8/bin
$ sudo ./coldfusion start

From past experience if I don’t start the Coldfusion service as root it gives me some strange errors and things do not work right. So here i just told it to startup as root from the beginning.

Starting ColdFusion 8...
The ColdFusion 8 server is starting up and will be available shortly.
======================================================================
Running the ColdFusion 8 connector wizard
======================================================================
Configuring the web server connector (Launched on the first run of the ColdFusion 8 start script)
Running apache connector wizard...
Connector installation succeeded for apache
======================================================================
ColdFusion 8 has been started.
ColdFusion 8 will write logs to /opt/coldfusion8/logs/cfserver.log
======================================================================

Now to test it out. I loaded up my localhost/CFIDE/administrator/ and it pulls up the coldfusion administrator. Looks good to me. Went through the administrator and setup a couple of things, tested out a cfm page in the root. All seems to be working well… good job Adobe.