Fix the jjb-deploy job to accept a JJB_VERSION parameter in the
build parameters field so that projects can select which version
of JJB they want for the job.
Issue: RELENG-3073
Change-Id: I33653d50e11c79a00a5858c395bc05f20a03d283
Signed-off-by: Anil Belur <abelur@linuxfoundation.org>
Signed-off-by: Thanh Ha <zxiiro@gmail.com>
project: "{project}"
stream: "{stream}"
branch: "{branch}"
+ - lf-infra-jjb-parameters:
+ jjb-cache: "{jjb-cache}"
+ jjb-version: "{jjb-version}"
wrappers:
- lf-infra-wrappers:
- job-template:
name: "{project-name}-jjb-deploy-job"
id: gerrit-jjb-deploy-job
+ <<: *lf_jjb_common
+ # yamllint disable-line rule:key-duplicates
<<: *lf_jjb_deploy_job
scm:
- job-template:
name: "{project-name}-jjb-deploy-job"
id: github-jjb-deploy-job
+ <<: *lf_jjb_common
+ # yamllint disable-line rule:key-duplicates
<<: *lf_jjb_deploy_job
properties:
--- /dev/null
+---
+fixes:
+ - |
+ Fix the jjb-deploy job to accept a JJB_VERSION parameter in the parameters
+ field so that projects can select which version of JJB they want for the job.
+
+ The change that ended up breaking jjb-deploy was caused by this Gerrit
+ patch here:
+
+ https://gerrit.linuxfoundation.org/infra/c/releng/global-jjb/+/62788
+
+ The bug was introduced in the lf-env.sh when the lf-pip-install macro was
+ removed. Prior to the removal the jjb-deploy job was installing the latest
+ and greatest JJB version. However now jjb-deploy is now installing the
+ fallback version of JJB_VERSION from the lf-env.sh script which is 2.8.0.
+
+ Reference: `RELENG-3073 <https://jira.linuxfoundation.org/browse/RELENG-3073>`_