Difference between revisions of "Jenkins Sandbox"
From fd.io
| Line 18: | Line 18: | ||
JJB reads user-specific configuration from a jenkins.ini in the top-level ci-management directory. | JJB reads user-specific configuration from a jenkins.ini in the top-level ci-management directory. | ||
| − | |||
[job_builder] | [job_builder] | ||
Revision as of 19:41, 8 January 2020
Jenkins Sandbox
The purpose of the jenkins-sandbox is to allow projects to test their JJB setups before merging. It is configured similarly to the master instance, although it cannot publish artifacts or vote in Gerrit.
To request access to the sandbox please open a ticket at support.linuxfoundation.org. Please provide your LFID and email address.
Notes Regarding the Sandbox
- Jobs are automatically deleted every Saturday at 08:00 UTC
- Committers can log in and configure Jenkins jobs in the sandbox directly
- The Sandbox configuration mirrors production wherever possible
- Sandbox jobs can NOT be trigged via Gerrit
- Sandbox verify jobs need the Refspec configured
- Sandbox jobs can NOT upload artifacts to Nexus
- Sandbox jobs can NOT vote on Gerrit
Configuration Make sure you have the correct version of JJB installed.
JJB reads user-specific configuration from a jenkins.ini in the top-level ci-management directory.
[job_builder] ignore_cache=True keep_descriptions=False include_path=. recursive=True [jenkins] user=<LFID> password=<Jenkins token> url=https://jenkins.fd.io/sandbox query_plugins_info=False
