Code Review / kni / installer.git / commit
? search:
summary | shortlog | log | commit | commitdiff | review | tree
(parent: 7607fa5) | patch
Parameterize the name of the blueprint 97/1797/1
authorYolanda Robla <yroblamo@redhat.com>
Thu, 17 Oct 2019 10:41:39 +0000 (12:41 +0200)
committerYolanda Robla <yroblamo@redhat.com>
Thu, 17 Oct 2019 10:42:56 +0000 (12:42 +0200)
commitf5734452fbf913fb2d0b0a6c56f3cdbd5c1d6879
treeb044272517ac8e17e8caf8818d96c7d690a19d8atree | snapshot
parent7607fa50cbfa6f8d333d6b87857ccbdb593bf6d5commit | diff
Parameterize the name of the blueprint

Now we don't have a single blueprint, but two.
So we cannot have the name of the blueprint hardcoded
anymore. By looking at the env vars provided by
jenkins, we can reuse the GIT_CHECKOUT_DIR env var
instead, that will contain the name of the blueprint.

Signed-off-by: Yolanda Robla <yroblamo@redhat.com>
Change-Id: I3a0e517d64268f2287bb19ca50d2e5f7431ded22
ci/kni_deploy_aws.sh diff | blob | history
ci/kni_deploy_libvirt.sh diff | blob | history