Verify gpg signature of the latest commit message in $WORKSPACE.
This command assumes that $WORKSPACE is a git repo.
+lf-infra-pre-build
+------------------
+
+Macro that runs before all builders to prepare the system for job use.
+
lf-infra-package-listing
------------------------
Run `packer build` to build system images.
+:Required parameters:
+
+ :openstack: Packer template uses an OpenStack builder (true|false).
+ :openstack-cloud: Sets OS_CLOUD variable to the value of this parameter.
+ :packer-version: Version of packer to use.
+ :platform: Build platform as found in the vars directory.
+ :template: Packer template to build as found in the templates directory.
+
lf-infra-packer-validate
------------------------
:Required parameters:
+ :openstack: Packer template uses an OpenStack builder (true|false).
+ :openstack-cloud: Sets OS_CLOUD variable to the value of this parameter.
:packer-cloud-settings: Cloud configuration file. Loaded on the build
server as CLOUDENV environment variable.
:packer-version: Version of packer to use.
any macros that calles the
:ref:`lf-provide-maven-settings <lf-provide-maven-settings>` macro.
-.. _provide-sigul-config:
-
-lf-provide-sigul-configuration
-------------------------------
-
-Provides sigual configuration to the Jenkins build node.
-
-Requires the following Config File Provider managed files in Jenkins
-preconfigured.
-
-* sigul-config
-* sigul-password
-* sigul-pki
-
-.. _provide-sigul-config-cleanup:
-
-lf-provide-sigul-configuration-cleanup
---------------------------------------
-
-Cleanup configuration provided by `provide-sigul-config`.
-
lf-rtd-trigger-build
--------------------
ReadTheDocs verify script.
-lf-sigul-install
-----------------
+lf-sigul-sign-dir
+-----------------
-Install Sigul.
+Use Sigul to sign a directory via {sign-dir}.
Requires ``SIGUL_BRIDGE_IP`` configured as a global envvar.
+:Required Parameters:
+ :sign-artifacts: Whether or not to sign artifacts with Sigul.
+ :sign-dir: Directory to sign.
+
lf-infra-provide-docker-cleanup
-------------------------------
Parameters
==========
+lf-clm-parameters
+-------------------
+
+Provides the policy evaluation stage to run against Nexus IQ Server.
+Valid values include: 'build', 'stage-release', 'operate'.
+
+lf-cmake-parameters
+-------------------
+
+Provides parameters needed by CMake. Should be used by any jobs that need to
+call the ``cmake && make && make install`` pattern.
+
lf-infra-maven-parameters
-------------------------
used in all job templates. This primary objective of this trigger is to
gather build logs and copy them to a log server.
+lf-infra-publish-windows
+------------------------
+
+Windows publisher for use at the end of Windows job templates. Takes care of
+cleaning out the workspace at the end of a job.
+
+lf-stack-delete
+---------------
+
+Requirements:
+
+* lftools >= v0.17.0
+
+Delete an openstack heat stack. Use at the end of a job that creates a stack.
+
+This macro requires a parameter defined in the job named STACK_NAME
+containing the name of the stack to delete.
+
SCM
===
Wrappers
========
+lf-infra-wrappers-common
+------------------------
+
+Provides lf-infra recommended wrappers which should be used in every
+job-template. It's meant to be used by more specific wrappers below.
+
lf-infra-wrappers
-----------------
Provides lf-infra recommended wrappers which should be used in every
-job-template.
+job-template that's run on Linux systems.
-This wrapper requires that a managed file called `npmrc` exists in the Jenkins. The main use
-case here is to point to a npm proxy, on Nexus for example.
-The type of the file should be "Custom file". You can set various npmrc settings in it.
-Documentation on npm configuration can be found at https://docs.npmjs.com/files/npmrc.
-If you are not using npm then it is fine for the file to be empty.
+This wrapper requires that a managed file called `npmrc` exists in the Jenkins.
+The main use case here is to point to a npm proxy, on Nexus for example.
+The type of the file should be "Custom file". You can set various npmrc
+settings in it. Documentation on npm configuration can be found at
+https://docs.npmjs.com/files/npmrc. If you are not using npm then it is fine
+for the file to be empty.
Example npmrc:
.. code-block:: bash
registry=https://nexus3.onap.org/repository/npm.public/
+
+lf-infra-wrappers-windows
+-------------------------
+
+Provides lf-infra recommended wrappers which should be used in every
+job-template that's run on Windows systems.