This release is a pre-release and may not be stable for production use.
README
Jenkins Job Builder takes simple descriptions of Jenkins jobs in YAML format, and uses them to configure Jenkins. You can keep your job descriptions in human readable text format in a version control system to make changes and auditing easier. It also has a flexible template system, so creating many similarly configured jobs is easy.
To install:
$ sudo python setup.py install
Online documentation:
Developers
Bug report:
Repository:
Cloning:
git clone https://git.openstack.org/openstack-infra/jenkins-job-builder
Patches are submitted via Gerrit at:
Please do not submit GitHub pull requests, they will be automatically closed.
More details on how you can contribute is available on our wiki at:
Writing a patch
We ask that all code submissions be pep8 and pyflakes clean. The easiest way to do that is to run tox before submitting code for review in Gerrit. It will run pep8 and pyflakes in the same manner as the automated test suite that will run on proposed patchsets.
When creating new YAML components, please observe the following style conventions:
All YAML identifiers (including component names and arguments) should be lower-case and multiple word identifiers should use hyphens. E.g., “build-trigger”.
The Python functions that implement components should have the same name as the YAML keyword, but should use underscores instead of hyphens. E.g., “build_trigger”.
This consistency will help users avoid simple mistakes when writing YAML, as well as developers when matching YAML components to Python implementation.
Installing without setup.py
For YAML support, you will need libyaml installed.
Mac OS X:
$ brew install libyaml
Then install the required python packages using pip:
$ sudo pip install PyYAML python-jenkins
Metadata
Release files for jjb-puppetlabs 1.2.1.dev145
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jjb-puppetlabs-1.2.1.dev145.tar.gz | 303.2 kB | Without provenance | Details for jjb-puppetlabs-1.2.1.dev145.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jjb_puppetlabs-1.2.1.dev145-py2-none-any.whl | Python 2 | none | any | Details for jjb_puppetlabs-1.2.1.dev145-py2-none-any.whl |
Total release size: 475.7 kB
Release files / jjb-puppetlabs-1.2.1.dev145.tar.gz
| Download URL | jjb-puppetlabs-1.2.1.dev145.tar.gz |
|---|---|
| Size | 303.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
656ca42918764271c89b08e1f5dafaea06d40a902d18733fb71b616c3184fac5
|
|
BLAKE2b-256 checksum How to use checksums |
22f9ceca9edf3d3a56268307a771ec85cf10941d530b353679accc4142b44ad9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / jjb_puppetlabs-1.2.1.dev145-py2-none-any.whl
| Download URL | jjb_puppetlabs-1.2.1.dev145-py2-none-any.whl |
|---|---|
| Size | 172.4 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
6677fded15b1471f7344c755909297d9c136b38b7acda91579eb342026f55c2b
|
|
BLAKE2b-256 checksum How to use checksums |
412ec9dddf3748889ea06ffbd16fd107bfb270171007560d2446ee3bc7e7de01
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for jjb-puppetlabs 1.2.1.dev145
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.