X-Git-Url: https://gerrit.linuxfoundation.org/infra/gitweb?a=blobdiff_plain;f=docs%2Fjjb%2Flf-release-jobs.rst;fp=docs%2Fjjb%2Flf-release-jobs.rst;h=8b5fa3d9bafdd9eecb7b89ad5926dd4b8b2ceb91;hb=9ce5ef214927e657dbd0d7cf6ed1ad613d642055;hp=cd0e1b556b1d8c8f03ec072a1467425840332029;hpb=98c1e382ce72ee76c628c4741e17753c89901e07;p=releng%2Fglobal-jjb.git diff --git a/docs/jjb/lf-release-jobs.rst b/docs/jjb/lf-release-jobs.rst index cd0e1b55..8b5fa3d9 100644 --- a/docs/jjb/lf-release-jobs.rst +++ b/docs/jjb/lf-release-jobs.rst @@ -49,7 +49,8 @@ For example, the parameters for a Maven release are as follows:: Maven Release Files ------------------- -An example of a maven release file appears below. +An example of a maven release file appears below. Name of release file +must start with "maven". eg. releases/maven-1.0.0-test.yaml .. code-block:: none @@ -179,11 +180,12 @@ The JSON schema for a container release file appears below. PyPI Release Files ------------------ -An example of a PyPI release file appears below. +An example of a PyPI release file appears below. Name of the release file must +start with "pypi". eg. releases/pypi-1.0.0-mypackage.yaml .. code-block:: none - $ cat releases/pypi-release.yaml + $ cat releases/pypi-1.0.0-mypackage.yaml --- distribution_type: pypi pypi_project: mypackage @@ -243,11 +245,12 @@ The JSON schema for a PyPI release file appears below. PackageCloud Release Files -------------------------- -An example of a PackageCloud release file appears below. +An example of a PackageCloud release file appears below. Name of release file +must start with "packagecloud". eg. releases/packagecloud-1.6.0-tree.yaml .. code-block:: none - $ cat releases/packagecloud-release.yaml + $ cat releases/packagecloud-1.6.0-tree.yaml --- distribution_type: packagecloud package_name: @@ -387,7 +390,7 @@ This template supports Maven and Container release jobs. **default**:: - compare-type: REG_EXP - pattern: '(releases\/.*\.yaml|\.releases\/.*\.yaml)' + pattern: '(releases\/maven.*\.yaml|\.releases\/maven.*\.yaml)' PyPI Release Merge @@ -428,6 +431,12 @@ template accepts neither a branch nor a stream parameter. should be the repository pypy.org. (default: pypi) :use-release-file: Whether to use the release file. (default: true) + :gerrit_trigger_file_paths: Override file paths filter which checks which + file modifications will trigger a build. + **default**:: + + - compare-type: REG_EXP + pattern: '(releases\/pypi.*\.yaml|\.releases\/pypi.*\.yaml)' PyPI Release Verify ~~~~~~~~~~~~~~~~~~~ @@ -466,6 +475,12 @@ verify template accepts neither a branch nor a stream parameter. should be the repository pypy.org (default: pypi) :use-release-file: Whether to use the release file. (default: true) + :gerrit_trigger_file_paths: Override file paths filter which checks which + file modifications will trigger a build. + **default**:: + + - compare-type: REG_EXP + pattern: '(releases\/pypi.*\.yaml|\.releases\/pypi.*\.yaml)' PackageCloud Release Verify ~~~~~~~~~~~~~~~~~~~~~~~~~~~ @@ -498,7 +513,7 @@ This template supports PackageCloud release jobs. **default**:: - compare-type: REG_EXP - pattern: '(releases\/.*\.yaml|\.releases\/.*\.yaml)' + pattern: '(releases\/packagecloud.*\.yaml|\.releases\/packagecloud.*\.yaml)' PackageCloud Release Merge @@ -529,7 +544,7 @@ This template supports PackageCloud release jobs. **default**:: - compare-type: reg_exp - pattern: '(releases\/.*\.yaml|\.releases\/.*\.yaml)' + pattern: '(releases\/packagecloud.*\.yaml|\.releases\/packagecloud.*\.yaml)' Setup for LFID, Nexus, Jenkins and Gerrit