Build #2

Parameter to identify a SCM project to build. This is typically the project repo path. For example: ofextensions/circuitsw

Stream is often set to the same name as 'branch' but can sometimes be used as a name representing a project's release code name.

GitHub PR Trigger provided parameter for specifying the commit to checkout. If using GitHub, in a manual build override with a branch path or sha1 hash to a specific commit. For example: 'origin/master'

Version of lftools to install. Can be a specific version like '0.6.0' or a PEP-440 definition. https://www.python.org/dev/peps/pep-0440/ For example '<1.0.0' or '>=1.0.0,<2.0.0'.

Gerrit Trigger provided parameter to identify a Gerrit branch. If using Gerrit, in a manual build override with the branch to build against.

Gerrit Trigger provided parameter to identify a refspec to fetch from Gerrit. If using Gerrit, in a manual build override with a refspec. https://git-scm.com/book/en/v2/Git-Internals-The-Refspec For example: 'refs/heads/master'

Gerrit Trigger provided parameter to identify Gerrit project that triggered the build. This is typically the project repo path as exists in Gerrit. For example: ofextensions/circuitsw If using Gerrit, in a manual build this should match the PROJECT parameter above.