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)
Introduce stack setup script
This change introduces setup-stack.sh script which will do setup
for the stack itself such as setting the default scenario if not
specified by the user and more importantly installing the dependencies.
Further changes will be sent, moving dependencies to stacks and
installations of those into stack setup script.
Depends-On: I6b9d27edd2016594b197a368b8ed393e98beef7f
Change-Id: I7892fa217a7db5c0c7b84a1b57aa6f311ee14cc6
(cherry picked from commit
d7c1e7673b19be3c8ee33283762aba19a606b6cd)
Control docker version within stack
Docker version was originally controlled within engine repository
but it is more appropriate to control it within the stack as the
version requirements could be different across the stacks. See the
dependent change for how it was controlled before.
Depends-On: Id5f2c72e35bba4d5ab413f7b19119330540f5674
Change-Id: I2720d6b6ddcde0f742f527e3f86b3085f13aaeda
(cherry picked from commit
bfdd3d8ef9d2aa002bab69ebd36f971df3918146)