Keep tarball and release properties for release 72/5372/1
authorFatih Degirmenci <fatih.degirmenci@est.tech>
Sat, 11 Jul 2020 12:55:52 +0000 (12:55 +0000)
committerFatih Degirmenci <fatih.degirmenci@est.tech>
Sat, 11 Jul 2020 18:13:53 +0000 (18:13 +0000)
commit2a8a667cb51ffb5e2f198a788c1666abdd34065a
tree2f6966122bb8cc0eed297db964eca6d16885fdc2
parentf293bffe8c125769c8ba6c393c0345c8a62c0bbf
Keep tarball and release properties for release

The installer file created by the package role can not be scanned by
JFrog XRAY due to it being an incompatible artifact type. In order for
the artifact to be scanned, it needs to be in one of the supported
formats.

This change updates package role to keep the tarball if the packaging
is run by release job in order to make scanning of artifacts possible.

In addition to keeping the tarball around, release job records release
metadata in release.properties file. This file is needed to be included
in tarball and installer file in order to make the traceability better.

Please note that both of these operations take effect if the release
metadata file /tmp/release.properties exists. This file is only created
by release job on Jenkins and does not exist for manual builds so there
is not change for manual packaging.

Change-Id: I3189806fc7a45b63328dc7236c94119f2ee9e295
(cherry picked from commit f8feaedc7ce75ad5524fab105d0b6d7dc178f9fc)
playbooks/roles/package/files/build.sh
playbooks/roles/package/tasks/main.yaml
playbooks/roles/package/tasks/record-shas.yaml [new file with mode: 0644]