Reviewed: https://review.openstack.org/301583 Committed: https://git.openstack.org/cgit/openstack/kolla/commit/?id=cfd806aeff30818d2c1a909780f141ae0ac8dfef Submitter: Jenkins Branch: master
commit cfd806aeff30818d2c1a909780f141ae0ac8dfef Author: Paul Bourke <email address hidden> Date: Tue Apr 5 12:03:47 2016 +0100
Log the SHA of the Git ref for source builds
When using named refs in source builds, e.g. "reference = master", one can't easily tell from the build output what SHA master actually pointed to at that point and time. Update the debug output to include this.
Closes-Bug: #1566316
Change-Id: I95c1cc316ab7332fa30fa43e207a5a5512b76708
Reviewed: https:/ /review. openstack. org/301583 /git.openstack. org/cgit/ openstack/ kolla/commit/ ?id=cfd806aeff3 0818d2c1a909780 f141ae0ac8dfef
Committed: https:/
Submitter: Jenkins
Branch: master
commit cfd806aeff30818 d2c1a909780f141 ae0ac8dfef
Author: Paul Bourke <email address hidden>
Date: Tue Apr 5 12:03:47 2016 +0100
Log the SHA of the Git ref for source builds
When using named refs in source builds, e.g. "reference = master", one
can't easily tell from the build output what SHA master actually pointed
to at that point and time. Update the debug output to include this.
Closes-Bug: #1566316
Change-Id: I95c1cc316ab733 2fa30fa43e207a5 a5512b76708