# Example configuration for intersphinx: refer to the Python standard library.
intersphinx_mapping = {
'jjb': ('https://docs.openstack.org/infra/jenkins-job-builder/', None),
+ 'lfdocs': ('http://docs.releng.linuxfoundation.org/en/latest/', None),
'lftools': ('http://lftools.releng.linuxfoundation.org/en/latest/', None),
'python': ('https://docs.python.org/', None),
}
:gerrit_verify_triggers: Override Gerrit Triggers.
+Test an in-progress patch
+^^^^^^^^^^^^^^^^^^^^^^^^^
+
+To test an in-progress patch from a GitHub Pull Request. Upload this
+job to the :doc:`Jenkins Sandbox <lfdocs:jenkins-sandbox>`. Then when manually
+building the job replace the GERRIT_REFSPEC parameter with the GitHub Pull
+Request number of the patch you would like to test.
+
+Example GitHub:
+
+.. code-block:: none
+
+ GERRIT_REFSPEC: origin/pr/49/merge
.. _gjjb-packer-verify:
scm:
- lf-infra-github-scm:
url: '{git-clone-url}{github-org}/{project}'
- refspec: ''
- branch: 'refs/heads/{branch}'
+ refspec: >
+ +refs/heads/*:refs/remotes/origin/*
+ +refs/pull/*:refs/remotes/origin/pr/*
+ branch: '$GERRIT_REFSPEC'
submodule-recursive: '{submodule-recursive}'
submodule-timeout: '{submodule-timeout}'
choosing-strategy: default
--- /dev/null
+---
+features:
+ - |
+ The GERRIT_REFSPEC build parameter can now be used to trigger a test build
+ from the Jenkins Sandbox system against a work in progress packer image
+ patch from a GitHub Pull Request.