Jenkins is the market leading continuous integration system, originally created by Kohsuke Kawaguchi. This API makes Jenkins even easier to use by providing an easy to use conventional python interface.
Jenkins (and It’s predecessor Hudson) are fantastic projects - but they are somewhat Java-centric. Thankfully the designers have provided an excellent and complete REST interface. This library wraps up that interface as more conventional python objects in order to make most Jenkins oriented tasks simpler.
This library can help you:
- Query the test-results of a completed build
- Get a objects representing the latest builds of a job
- Search for artifacts by simple criteria
- Block until jobs are complete
- Install artifacts to custom-specified directory structures
- Username/password auth support for jenkins instances with auth turned on
- Search for builds by subversion revision
- Add, remove and query jenkins slaves
[ ] Currently incompatible with Jenkins > 1.518. Job deletion operations fail unless Cross-Site scripting protection is disabled.
For other issues, please refer to the support URL below.
Egg-files for this project are hosted on PyPi. Most Python users should be able to use pip or setuptools to automatically install this project.
Most users can do the following:
pip install jenkinsapi
JenkinsAPI is intended to map the objects in Jenkins (e.g. Builds, Views, Jobs) into easily managed Python objects:
Python 2.7.4 (default, Apr 19 2013, 18:28:01) [GCC 4.7.3] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import jenkinsapi >>> from jenkinsapi.jenkins import Jenkins >>> J = Jenkins('http://localhost:8080') >>> J.keys() # Jenkins objects appear to be dict-like, mapping keys (job-names) to ['foo', 'test_jenkinsapi'] >>> J['test_jenkinsapi'] <jenkinsapi.job.Job test_jenkinsapi> >>> J['test_jenkinsapi'].get_last_good_build() <jenkinsapi.build.Build test_jenkinsapi #77>
JenkinsAPI lets you query the state of a running Jenkins server. It also allows you to change configuration and automate minor tasks on nodes and jobs.
You can use Jenkins to get information about recently completed builds. For example, you can get the revision number of the last succsessful build in order to trigger some kind of release process.:
from jenkinsapi.jenkins import Jenkins def getSCMInfroFromLatestGoodBuild(url, jobName, username=None, password=None): J = Jenkins(url, username, password) job = J[jobName] lgb = job.get_last_good_build() return lgb.get_revision() if __name__ == '__main__': print getSCMInfroFromLatestGoodBuild('http://localhost:8080', 'fooJob')
When used with the Git source-control system line 20 will print out something like ‘8b4f4e6f6d0af609bb77f95d8fb82ff1ee2bba0d’ - which looks suspiciously like a Git revision number.
JenkinsAPI is a pure-python project and can be improved with almost any programmer’s text-editor or IDE. I’d recomend the following project layout which has been shown to work with both SublimeText2 and Eclipse/PyDev
Make sure that pip and virtualenv are installed on your computer. On most Linux systems these can be installed directly by the OS package-manager.
- Create a new virtualenv for the project::
- Change to the new directory and check out the project code into the src subdirectory
cd jenkinsapi git clone https://github.com/salimfadhley/jenkinsapi.git src
- Activate your jenkinsapi virtual environment::
cd bin source activate
- Install the jenkinsapi project in ‘developer mode’ - this step will automatically download all of the project’s dependancies::
cd ../src python setup.py develop
- Test the project - this step will automatically download and install the project’s test-only dependancies. Having these installed will be helpful during development::
python setup.py test
Set up your IDE/Editor configuration - the misc folder contains configuration for Sublime Text 2. I hope in time that other developers will contribute useful configurations for their favourite development tools.
The project maintainers welcome any code-contributions. Please conside the following when you contribute code back to the project:
- All contrubutions should come as github pull-requests. Please do not send code-snippets in email or as attachments to issues.
- Please take a moment to clearly describe the intended goal of your pull-request.
- Please ensure that any new feature is covered by a unit-test