summaryrefslogtreecommitdiffstats
path: root/doc/source/execution.rst
Commit message (Collapse)AuthorAgeFilesLines
* Fix links causing redirectsThanh Ha2020-01-221-2/+2
| | | | | | | | Some links have been permanently redirected to a new URL so adjust the links to go directly to the new URL. Change-Id: I900091f8bdc39aa5fd06eae04a9b18ef23add8f2 Signed-off-by: Thanh Ha <zxiiro@gmail.com>
* Add config options --jobs-only and --views-onlyAnil Belur2018-09-191-0/+5
| | | | | | | | | | | | | | | | | | | | | Add options --jobs-only and --views-only to job_builder section in config file. By default JJB updates both jobs and views. Some cases non-admin users are not allowed to update views on Jenkins which requires explicity using -j flag. Allow users to set a config option 'update=jobs|views|all' in the 'job_builder' section implicitly use --jobs-only or --views-only and control these flags from the config file. Note: CLI options takes precedence over the config file. Change-Id: I2a94e5a2d671ccbfc505de2f19b578ecfef9e9d7 Co-Authored-By: Thanh Ha <zxiiro@linux.com> Signed-off-by: Anil Belur <askb23@gmail.com> Signed-off-by: Thanh Ha <zxiiro@linux.com> Signed-off-by: Anil Belur <askb23@gmail.com>
* Add retain_anchors config option.Vicky Chijwani2018-05-311-0/+9
| | | | | | | | | If set to True, YAML anchors can be referenced across files, allowing jobs to be composed from bits of YAML defined in separate files. False by default. Story: 2000338 Task: 2547 Change-Id: I034ce3bce0030093cb8d4266dabbdb06d96306d6
* Fix a typo in docAnushka Bhandari2018-05-191-1/+1
| | | | | | | Fix correct link to CloudBees Folders Plugin Add missing comma in line 1290 of module wrappers Change-Id: Idb0311064945965c58c0cc608fc6cab00eef3ee9
* Merge "Add views and jobs only options for update"Zuul2018-02-231-0/+7
|\
| * Add views and jobs only options for updateAnil Belur2018-01-251-0/+7
| | | | | | | | | | | | | | | | | | | | JJB 2.0 update does not allow updating only views or jobs which would be useful, which is implemented with delete and delete-all. This patch add's thoses flags for the update option. Change-Id: I3712c8552ea83a4c29c05461894c4464aa41230f Signed-off-by: Anil Belur <askb23@gmail.com>
* | Added option to print job names as urlsSorin Sbarnea2018-01-261-0/+5
|/ | | | | | | | Add print_job_urls = True to [job_builder] to enable output as urls instead of simple job names when changing them. Change-Id: I3454606a50ca385c87d8c13d3eab5d30d94cf02f Signed-off-by: Sorin Sbarnea <ssbarnea@redhat.com>
* Allow update to provide plugin_info via yamlThanh Ha2017-09-191-0/+19
| | | | | | | | | | | | | | | | | | Getting plugin info requires Administrator permissions. It seems the test command allows providing the plugin_info details via a yaml configuration file. This patch allows the same command to be passed to the update command to allow us to configure the plugin versions manually and not require administrator permissions. Additionally this patch adds a new command called get-plugins-info which can create the plugins_info.yaml file to pass to the plugin_info_path. See: http://lists.openstack.org/pipermail/openstack-infra/2016-June/004388.html Change-Id: I5a34979407d863a84f34afbf8f565081ec52190a Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
* Add option to make test output file layout match JenkinsPeter Eisentraut2017-05-271-0/+8
| | | | | | | | | | | | | | | | | | Before, `jenkins-job-builder test -o outdir` would write outdir/job_name With the new option `--config-xml`, it writes outdir/job_name/config.xml to match the layout that Jenkins uses internally. This is more useful for diffing against existing Jenkins installations or uploading job definitions by other means. Also, it seems better to give the output files an .xml extension. Change-Id: I78fc7aff531925ee071b8e19f40f766b4af0b5ad
* Add note regarding a bug with !include-raw-escapeThanh Ha2017-03-161-1/+1
| | | | | | | | This spawned from discussions on the mailing list: http://lists.openstack.org/pipermail/openstack-infra/2017-March/005233.html Change-Id: I7916ebec86350fa760bb02b6bde38e27c71dc359 Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
* Add view management functionalityThanh Ha2016-10-141-15/+32
| | | | | | | | | | | | | | | | | | | - Adds the ability for JJB to work with views - Views can be created, updated, and deleted. - New modules for List view and Build Pipeline view are added - New tests for testing the deletion of views Example View configuration: - view: name: MyView view-type: list Change-Id: Idb29a4407bcc14593e10a4d951036cb04e8e6c27 Co-Authored-By: Brandon Leonard <brandon.leonard@rackspace.com> Co-Authored-By: Joao Vale <jpvale@gmail.com> Co-Authored-By: Lucas Dutra Nunes <ldnunes@ossystems.com.br> Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>
* Fix documentation of --delete-old: affects only managed jobs.Jonathan Perret2016-07-131-2/+3
| | | | | | | | | | | | | | | | As far back as its introduction (2cefa400), the `--delete-old` option has only ever deleted jobs that were marked with the special "<!-- Managed by Jenkins Job Builder -->" comment that JJB adds to descriptions. This change fixes the documentation of the `--delete-old` option, which erroneously used to state that even jobs that were never managed by JJB would be subject to deletion. The test for the feature was slightly enriched as well: the fact that unmanaged jobs were not deleted, was not actually tested. Change-Id: I438a7b555b6e122869988b3a2b9ea40896004122
* Merge "Take parameter order from yaml in trigger_parameterized_builds"Jenkins2016-04-221-0/+14
|\
| * Take parameter order from yaml in trigger_parameterized_buildsDarragh Bailey2016-03-071-0/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Support taking the order of the parameters to be passed through to a triggered parameterized build from the user defined yaml via config option. Use the existing order by default so as not to break current usage. The XML ordering of the parameters matters since when the same parameter is defined through multiple sources, Jenkins uses the ordering to determine which will be the one that that should win. ie if FOO=BAR is set as a build parameter of the current job and a properties file is generated during build that attempts to set FOO=BAZ; the XML ordering determines which value, BAZ or BAR, that the triggered job sees for the parameter FOO. Change-Id: Ia0dafad8ed3976e7b0b11feb6b3af844bbda9d4a
* | cmd: Add a config file fallback to the user's home directorySebastian Schuberth2016-04-181-4/+4
|/ | | | | | | | | | | | | | | | | The system-global path of /etc/jenkins_jobs/jenkins_jobs.ini is not applicable on Windows. To solve that, and as Linux users would benefit from a per-user configuration file, too, introduce a fallback at ~/.config/jenkins_jobs/jenkins_jobs.ini following the XDG Base Directory Specification. Try to use that per-user file if no configuration file is given on the command line and none is present in the script directory for development purposes. Change-Id: I1a22454999ee8ac60d6f22545850c33aa03bb29b
* Add parallelization optionsDavid Caro2015-12-011-0/+7
| | | | | | | | | | | | | | | | * Only update_jobs uses the parallel features right now * --workers N - If set to 0, it will use parallel execution and use the number of cores in the machine as thread count - Any other value enables the parallel extensions and sets the number of concurrent threads to that value - Will use 1 by default Add some tests to make sure the parallel execution helpers work as expected. Change-Id: Ib0abd34ea7525f75fff4ff480287a6e589deba90 Signed-off-by: David Caro <dcaroest@redhat.com>
* cmd.py: tweak plugin information querying logicJonathan Lebon2015-10-301-4/+4
| | | | | | | | | | | | | | | | | | We don't want to unconditionally disable plugin querying just because --conf is not given. That would mean that the query_plugins_info field in the default paths would always be ignored, even if set to True. This patch tweaks the logic so that we remember in options.conf the actual name of the config file that we read from, whether it be from --conf or from one of the default paths. This way, the `test` command will still work out of the box, as commit f68831b envisioned. But query_plugins_info is now checked if the user has a configuration file (whether it be a default one, or one specified through --conf). Change-Id: Id71ad207f0419f7cc52eca174dd859d4182d7250 Story: 2000387
* Allow JJB to set connection timeout to jenkins serverKhai Do2015-09-211-0/+4
| | | | | | | | | | | Change If84778231b provided an option to set a connection timeout in the python-jenkins library. This change allows JJB to override that timeout value. Add tests to ensure that the timeout is only set when specified via the config options. Change-Id: I3dfe9139469dd0e8549eeedb1833c55ac79ea8b5
* Stash publisher's credentials configurationNicolas Glayre2015-08-241-0/+14
| | | | | | | | | | As per now if you want to configure the stash publisher and give it a username and password, you need to set them in clear text within the yaml file. This pull request gives the possibility to set these credentials within the jenkins_jobs.ini file and therefore makes it possible to not expose them to everyone. Change-Id: I2e5d6caefb87ded2468c7b7e015e20464ffef99e
* Add a JJB quick start guideKhai Do2015-08-121-0/+265
This change does the following: 1. add a quick start guide 2. move the info about executing jjb from installation.rst to execution.rst and slightly update the verbage. The intention is to kick off this guide with a few simple use cases not to have a comprehensive set of use cases. Change-Id: I719c6dec5cc5f2731ef95094b76ec54c12b41b8e
generated by cgit (git 2.34.1) at 2025-09-02 20:28:54 +0000