Welcome, guest | Sign In | My Account | Store | Cart

Notice! PyPM is being replaced with the ActiveState Platform, which enhances PyPM’s build and deploy capabilities. Create your free Platform account to download ActivePython or customize Python with the packages you require and get automatic updates.

Download
ActivePython
INSTALL>
pypm install collective.recipe.hudson

How to install collective.recipe.hudson

  1. Download and install ActivePython
  2. Open Command Prompt
  3. Type pypm install collective.recipe.hudson
 Python 2.7Python 3.2Python 3.3
Windows (32-bit)
1.0 Available View build log
1.0a3 Available View build log
1.0a2 Available View build log
Windows (64-bit)
1.0 Available View build log
1.0a3 Available View build log
1.0a2 Available View build log
Mac OS X (10.5+)
1.0 Available View build log
1.0a3 Available View build log
1.0a2 Available View build log
Linux (32-bit)
1.0 Available View build log
1.0a3 Available View build log
1.0a2 Available View build log
Linux (64-bit)
1.0 Available View build log
1.0a3 Available View build log
1.0a2 Available View build log
 
License
ZPL 2.1
Lastest release
version 1.0 on Feb 14th, 2011

Overview

This recipe has been superseded by jarn.jenkins maintained on Github at https://github.com/Jarn/jarn.jenkins.

This is a recipe to set up and configure Hudson in a Jetty servlet container.

Note

The recipe is currently not compatible with Python 2.7 due to an incompatibility in the iw.recipe.template recipe used internally.

Basic setup

A basic buildout configuration using this recipe looks like this:

[buildout]

parts =
    jetty-download
    hudson-download
    hudson

[jetty-download]
recipe = gocept.download
url = http://download.eclipse.org/jetty/stable-7/dist/jetty-distribution-7.0.1.v20091125.tar.gz
md5sum = b29813029fbbf94d05e1f28d9592813f
strip-top-level-dir = true

[hudson-download]
recipe = gocept.download
url = http://download.hudson-labs.org/war/1.375/hudson.war
md5sum = c9bd2515f5b01e46eed2f740aef5e145

[hudson]
recipe = collective.recipe.hudson
jetty-location = ${jetty-download:location}
hudson-location = ${hudson-download:location}

This will download both Jetty and Hudson and create an executable Jetty environment in parts/hudson. It will also create a control script in bin/hudson. The name of the script is the name of the section.

To test the setup run bin/hudson fg and check the console output. By default this will run a Jetty server on port 8070. The hudson instance is accessible in a browser at http://127.0.0.1:8070/hudson/.

Hudson will write all its log files into var/hudson/log. All its configuration including jobs and past runs will go into var/hudson/data. The directory name in var will have the name of the recipe section.

Options

The recipe supports the following options:

host
Name or IP address of the Jetty server, e.g. some.server.com. Defaults to 127.0.0.1.
port
Server port. Defaults to 8070.
java-opts

Optional. Parameters to pass to the Java Virtual Machine (JVM) used to run Jetty. Each option is specified on a separated line. If you run into memory problems it's typical to pass:

[hudson]
...
java-opts =
  -Xms512M
  -Xmx1024M
...

Changelog

1.0 - 2011-02-13
  • Superseded by jarn.jenkins. [hannosch]
1.0a3 - 2010-09-10
  • Added note about Python 2.7 incompatibility. Thanks to Rob Madole for notifying me. [hannosch]
  • Updated example to Hudson 1.375. [hannosch]
1.0a2 - 2010-03-04
  • Configure the HUDSON_HOME environment variable inside the jetty.xml instead of the control script. [hannosch]
  • Simplify the example buildout a bit. [hannosch]
1.0a1 - 2010-03-04
  • Better update handling. [hannosch]
  • Don't configure a ContextDeployer which allows us to skip the contexts examples cleanup. [hannosch]
  • Added basic package documentation. [hannosch]
  • Updated jetty configuration to match new class names caused by the move to the Eclipse project. [hannosch]
  • Initial code, largely based on collective.recipe.solrinstance. [hannosch]

Subscribe to package updates

Last updated Feb 14th, 2011

Download Stats

Last month:2

What does the lock icon mean?

Builds marked with a lock icon are only available via PyPM to users with a current ActivePython Business Edition subscription.

Need custom builds or support?

ActivePython Enterprise Edition guarantees priority access to technical support, indemnification, expert consulting and quality-assured language builds.

Plan on re-distributing ActivePython?

Get re-distribution rights and eliminate legal risks with ActivePython OEM Edition.