Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

Overview

This is a recipe to set up and configure Jenkins 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
    jenkins-download
    jenkins

[jetty-download]
recipe = hexagonit.recipe.download
url = http://download.eclipse.org/jetty/7.2.2.v20101205/dist/jetty-distribution-7.2.2.v20101205.tar.gz
strip-top-level-dir = true

[jenkins-download]
recipe = hexagonit.recipe.download
url = http://mirrors.jenkins-ci.org/war/1.397/jenkins.war
download-only = true

[jenkins]
recipe = jarn.jenkins
jetty-location = ${jetty-download:location}
jenkins-location = ${jenkins-download:location}

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

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

Jenkins will write all its log files into var/jenkins/log. All its configuration including jobs and past runs will go into var/jenkins/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:

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

Changelog

1.0b2 - 2011-03-15

  • Pass os.environ into the Jenkins process. [newbery]

1.0b1 - 2011-02-13

  • Renamed from collective.recipe.hudson to jarn.jenkins, following the Hudson to Jenkins renaming by the Jenkins community. [hannosch]

1.0a3 - 2010-09-10

  • Added note about Python 2.7 incompatibility. Thanks to Rob Madole for notifying me. [hannosch]

  • Updated example to version 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]

Metadata

Release files for jarn.jenkins 1.0b2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for jarn.jenkins 1.0b2
File Size Uploaded Provenance Actions
jarn.jenkins-1.0b2.zip 14.6 kB Without provenance Details for jarn.jenkins-1.0b2.zip

Release files / jarn.jenkins-1.0b2.zip

Download URL jarn.jenkins-1.0b2.zip
Size 14.6 kB
Tags Source
SHA-256 checksum
How to use checksums
9e9ec27b99de073278cb6340bb99863199d831e8dd69ac6fc470e1a69314aebf
BLAKE2b-256 checksum
How to use checksums
2922254cd88018a5591b07ea7f22717e46025d7e9fb35952b5fa1438395b227f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No

Security for jarn.jenkins 1.0b2

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page