Jenkins

Differences between revisions 15 and 16
Revision 15 as of 2011-03-31 18:52:40
Size: 1868
Editor: james-page
Comment:
Revision 16 as of 2011-04-18 08:02:22
Size: 1851
Editor: james-page
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
|| '''Current Jenkins Version''' || 1.396-0ubuntu1~test17 || || '''Current Jenkins Version''' || 1.396-0ubuntu1~test20 ||
Line 33: Line 33:
|| jenkins-bazaar-plugin || 1.16 || Works OK - depends on bzr || || jenkins-bazaar-plugin || 1.16 || Works OK ||

Current Jenkins Version

1.396-0ubuntu1~test20

Please report bugs to hudson-ubuntu-users at lists dot launchpad dot net

Getting Started

Install Jenkins

sudo add-apt-repository ppa:hudson-ubuntu/testing
sudo apt-get update
sudo apt-get install jenkins

or use this handy cloud-config file if you want to spin on in ec2

Install Jenkins (on Tomcat6)

sudo add-apt-repository ppa:hudson-ubuntu/testing
sudo apt-get update
sudo apt-get install jenkins-tomcat

Access Jenkins

http://localhost:8080

Install Plugins

Plugin Name

Version

Notes

jenkins-ssh-slaves-plugin

0.14

Works OK

jenkins-bazaar-plugin

1.16

Works OK

jenkins-url-change-trigger-plugin

1.2

Works OK

jenkins-ec2-plugin

1.10

Not that great but inline with upstream release

Plugins are activated after restarting jenkins.

Current Know Issues

Title

Description

Workaround

Fix

Missing Libraries

Because the base distribution does not include the normal plugins which upstream bundle, some other plugins fail due to missing libraries

openid

required commons-httpclient which is pulled in my the maven plugin build to Jenkins core.

install maven plugin.

commons-httpclient now installed in war.

Plugin Manager

had some odd behaviour in ec2 instances with limited inbound access - JSON response from update center was truncated

For some reason fixing the port that slaves use to a single port resolved this issue

Index

ServerTeam/Jenkins (last edited 2011-08-16 19:53:25 by james-page)