jjb
/
jenkins-job-builder
Code Issues Proposed changes
Tools to make Jenkins jobs from templates
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
3,270 Commits
1 Branch
35 Tags
34 MiB
Python 99.3%
Shell 0.6%
 
 
master
5.0.2
5.0.1
5.0.0
4.3.0
4.2.0
4.1.0
4.0.0
3.12.0
3.11.0
3.10.0
3.9.0
3.8.0
3.7.0
3.6.0
3.5.0
3.4.0
3.3.0
3.2.0
3.1.0
3.0.2
3.0.1
3.0.0
2.10.1
2.10.0
2.9.1
2.9.0
2.8.0
2.7.0
2.6.0
2.5.0
2.4.0
2.3.0
2.2.1
2.2.0
2.1.0
2.0.11
2.0.10
2.0.9
2.0.8
2.0.7
2.0.6
2.0.5
2.0.4
2.0.3
2.0.2
2.0.1
2.0.0
2.0.0.0b3
2.0.0.0b2
1.6.2
2.0.0.0b1
1.6.1
1.6.0
1.5.0
1.4.0
1.3.0
1.2.0
1.1.0
1.0.0
0.4.2
0.9.0
0.8.1
0.8.0
0.7.0
0.6.0
0.5.0
0.4.0
0.3.0
0.2.0
0.1.0
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '4.2.0'
${ noResults }
Go to file
Piotr Falkowski 5cea04aa2a New permissions option for GitHub PR Comment Build plugin 
In version 78.v2dcf62ba199b GitHub Pull Request Comment Build Plugin
introduced permissions check for users triggering jobs with comments.
This added a new checkbox/XML element that allows untrusted users to
trigger builds.
(see https://github.com/jenkinsci/github-pr-comment-build-plugin/pull/46)

This commit adds support for this option by allowing dictionary syntax for GH PR Comment Build plugin:
 ```
 - trigger-build-on-pr-review:
    allow-untrusted-users: true
 ```
 while preserving support for currently existing syntax:
 ```
 - trigger-build-on-pr-review: true
 ```

Change-Id: I554129c779161b47cba4566f7821ef7590a242e0
 		3 months ago
doc Tests: Rename yamlparser tests and fixture directories 4 months ago
etc Add update option to the JJB config sample 5 years ago
jenkins_jobs New permissions option for GitHub PR Comment Build plugin 3 months ago
samples reference tests as examples 9 years ago
tests New permissions option for GitHub PR Comment Build plugin 3 months ago
tools Replace openstack.org git:// URLs with https:// 4 years ago
.gitignore Add TAGS file to .gitignore 12 months ago
.gitreview OpenDev Migration Patch 4 years ago
.pre-commit-config.yaml Update Zuul CI 6 months ago
.zuul.yaml Update Zuul CI 6 months ago
LICENSE Add a LICENSE file. 11 years ago
MANIFEST.in Just give in and use setuptools_git. 11 years ago
README.rst Move tests to pytest 6 months ago
docs-requirements.txt Add a requirements file for readthedocs 8 years ago
requirements.txt Requirements: Fix setuptools version 4 months ago
setup.cfg fix: Drop testing for Python 3.6 1 year ago
setup.py Auto-generated output from python-black 4 years ago
test-requirements.txt Move tests to pytest 6 months ago
tox.ini Support for follow-symlinks in archive publisher 5 months ago

README.rst

README

Jenkins Job Builder takes simple descriptions of Jenkins jobs in YAML or JSON 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:

$ pip install --user jenkins-job-builder

Online documentation:

Developers

Bug report:

Repository:

Cloning:

git clone https://opendev.org/jjb/jenkins-job-builder.git

Install pre-commit from https://pre-commit.com/#intro in order to run some minimal testing on your commits.

A virtual environment is recommended for development. For example, Jenkins Job Builder may be installed from the top level directory:

$ virtualenv .venv
$ source .venv/bin/activate
$ pip install -r test-requirements.txt -e .

Patches are submitted via Gerrit at:

Please do not submit GitHub pull requests, they will be automatically closed.

Mailing list:

IRC:

  • #openstack-jjb on OFTC

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.

Unit Tests

Unit tests have been included and are in the tests folder. Many unit tests samples are included as examples in our documentation to ensure that examples are kept current with existing behaviour. To run the unit tests, execute the command:

tox -e py38

Unit tests could be run in parallel, using pytest-parallel pytest plugin:

tox -e py38 -- --workers=auto
  • Note: View tox.ini to run tests on other versions of Python, generating the documentation and additionally for any special notes on running the test to validate documentation external URLs from behind proxies.

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