The Ceph SHA1 is divined by the -setup job, and not available in the
parent job. That's easily fixed by the same method it's passed to the
-build job: grab the file artifact and use it to inject SHA1 into the
environment. This means the parent job can show the SHA1 in its build
label for humans, and can also be searched by Jenkins API calls.
Signed-off-by: Dan Mick <dmick@redhat.com>
- github:
url: https://github.com/ceph/ceph-ci
- copyartifact:
- projects: ceph-dev-new-build
+ projects: ceph-dev-new-build, ceph-dev-new
parameters:
- string:
- name: ceph-dev-new-setup
current-parameters: true
exposed-scm: false
+ - copyartifact:
+ project: ceph-dev-new-setup
+ filter: dist/sha1
+ which-build: multijob-build
+ - inject:
+ properties-file: ${WORKSPACE}/dist/sha1
- multijob:
name: 'ceph dev build phase'
condition: SUCCESSFUL
- github:
url: https://github.com/ceph/ceph
- copyartifact:
- projects: ceph-dev-build
+ projects: ceph-dev-build, ceph-dev
parameters:
- string:
- name: ceph-dev-setup
current-parameters: true
exposed-scm: false
+ - copyartifact:
+ project: ceph-dev-setup
+ filter: dist/sha1
+ which-build: multijob-build
+ - inject:
+ properties-file: ${WORKSPACE}/dist/sha1
- multijob:
name: 'ceph dev build phase'
condition: SUCCESSFUL