Support for the Throttle Plugin is added to JJB jobs so static build servers can restrict the number of concurrent JJB jobs ran at the same time.
This must be explicitly enabled by setting throttle-enabled on the jobs.
The JJB Deploy Job is configured to trigger only if the Gerrit comment starts with the jjb-deploy keyword.
Without the regex being optimized the job triggers on any occurance of the jjb-deploy keyword in a Gerrit comment, with is waste infra resources.
Example of a valid command in Gerrit comment that triggers the job:
jjb-deploy builder-jjb-*
Example of a invalid command in Gerrit comment that would _not_ trigger the job:
Update the job. jjb-deploy builder-jjb-*
sign-mode parameter which
allows jobs to choose to sign artifacts using either parallel mode
or serial mode (default).lf-sigul-sign-dir users need to add a new parameter sign-mode to
their job-templates setting either parallel or serial as the value, we
recommend setting serial mode for this setting.
{project-name}-maven-stage-{stream}’s Sigul signer now defaults to serial mode instead of the previous parallel behaviour. To change this back to the previous behaviour pass the “sign-mode” parameter to the job template:
- project:
name: parallel-sign
jobs:
- gerrit-maven-stage:
sign-mode: parallel
Jobs using the lf-maven-stage macro now need to update to the new usage. Preparation calls to lf-provide-maven-settings, lf-infra-create-netrc, and lf-provide-maven-settings-cleanup are no longer necessary to prepare the lf-maven-stage macro.
Usage:
- lf-maven-stage:
mvn-global-settings: 'global-settings'
mvn-settings: 'settings'
mvn-staging-id: 'staging profile id'
Add a puppet-verify job to lf-ci-jobs. This job will perform Puppet linting on the specified repository.
- project:
name: lf-infra-puppet-mymodule
project-name: lf-infra-puppet
project: puppet/modules/mymodule
jobs:
- gerrit-puppet-verify
lf-stack-create macro allows job-templates to setup a OpenStack
Heat stack, useful for spinning up CSIT labs to run integration tests
against. Use with the lf-stack-delete macro.New macro lf-maven-central is available to deploy artifacts to OSSRH staging for jobs that want to eventually deploy to Maven Central.
---
- job-template:
name: lf-maven-central-macro-test
#####################
# Default variables #
#####################
mvn-central: true
mvn-global-settings: ''
mvn-settings: ''
ossrh-profile-id: ''
#####################
# Job configuration #
#####################
builders:
- lf-maven-central:
mvn-central: '{mvn-central}'
mvn-global-settings: '{mvn-global-settings}'
mvn-settings: '{mvn-settings}'
ossrh-profile-id: '{ossrh-profile-id}'
lf-stack-delete has been modified to be a companion macro to
lf-stack-create in order to cleanup the stack at the end of a job run.
It now includes a required parameter openstack-cloud to choose the
clouds.yaml cloud configuration for the project. Existing users of
this macro will need to update their job templates accordingly.Requires JJB 2.8.0 for the jenkins-sandbox-cleanup job to not fail.
Note
Despite the failure if JJB 2.8.0 is not available the job will successfully delete all jobs and views, the primary purpose of this job.
delete-all is run.New view-templates project-view, common-view, and csit-view are
available for projects to manage Jenkins views through code.
To use the project-view template in a project:
- project:
name: aaa-view
views:
- project-view
project-name: aaa
To use the common-view template in a project:
- project:
name: daily-builds
views:
- common-view
view-name: Periodic
view-regex: '.*-periodic-.*'
To use the csit-view template in a project:
- project:
name: csit
views:
- csit-view
view-name: CSIT
view-regex: '.*csit.*'
- project:
name: csit-1node
views:
- csit-view
view-name: CSIT-1node
view-regex: '.*-csit-1node-.*'
Add support to maven-stage jobs to publish to Maven Central via OSSRH.
This is accomplished by adding these 2 new optional parameters to the job configuration.
- gerrit-maven-stage:
mvn-central: true
ossrh-profile-id: 7edbe315063867
submodule-timeout parameter to provide a timeout value (in minutes)
for git fetch operations.submodule-timeout parameter
for git fetch operations, defaulting to 10 minutes.common-view template in their
local ci-management repo. This common-view is called project-view
in global-jjb so rename all instances of common-view to
project-view when upgrading and remove the local common-view
view-template definition from ci-management.jenkins-urls in order to use the job.submodule-timeout value. It
is recommended to default this value to 10 since it is the
default used by the Jenkins Git Plugin.openstack module will now be installed as part of
pre-build.Add a new nexus-iq-namespace optional parameter to insert a namespace
into Nexus IQ AppID. This is useful for shared Nexus IQ systems where
projects might have concern about namespace collision.
Note
We recommend when using the namespace to add a trailing - to the value. Eg. ‘odl-‘, this is to make the namespace look nice for example “odl-aaa” is the result of namespace odl-, and project name aaa.
lf-infra-publish-windows. A publisher for use at the end of Windows
based job-templates.clouds.yaml config model
implemented in global-jjb v0.25.0.set -u which
causes Jenkins to fail when activating virtualenvsNew macro lf-sigul-sign-dir available to sign artifacts in a provided
directory using Sigul.
Usage:
- lf-sigul-sign-dir:
sign-dir: '$WORKSPACE/m2repo'
This macro also requires a boolean variable to SIGN_ARTIFACTS to be set
to true to activate the macro. We recommend the job-template that uses
this macro to define it in the job parameters section.
Example:
- bool:
name: SIGN_ARTIFACTS
default: '{sign-artifacts}'
description: Use Sigul to sign artifacts.
Add Sigul signing support to the maven-staging job. To activate Sigul
signing make sure to set sign-artifacts: true. Example:
- project:
name: abc
jobs:
- gerrit-maven-stage
sign-artifacts: true
Add lf-stack-delete macro to delete an openstack heat stack at the end of the job.
This macro requires a parameter defined in the job named STACK_NAME containing the name of the stack to delete.
Global JJB now has non-JJB YAML configuration and requires action on the ci-management repo when upgrading to this version of Global JJB to prevent JJB from picking up these YAMLs as config. Follow the instructions below BEFORE upgrading globall-jjb:
cd <git-root>
git mv jjb/global-jjb global-jjb
mkdir jjb/global-jjb
ln -s ../../global-jjb/shell jjb/global-jjb/shell
ln -s ../../global-jjb/jjb jjb/global-jjb/jjb
git add jjb/global-jjb
git commit -sm "Prepare repo for global-jjb v0.25.0"
packer buildpip install --user for global tool
installs.