x
/
ci-cd-pipeline-app-murano
Code Issues Proposed changes
ci-cd-pipeline-app-murano/tools
History
Sergey Kraynev 66214e4abe Use FQN for naming packages which we upload 
Use FQN from manifest file, instead of hardcoded prefix.
Also adopt upload logic for new packages names.

Change-Id: If190bcddad3b0d310a51dc302303e86c202a41fe
 		2016-08-12 15:42:29 +03:00
..
jenkins Add simple {shell,yaml}-check script 2016-07-27 14:31:09 +03:00
README.rst tools add README.rst 2016-07-13 16:13:14 -04:00
default_packages_list.sh Add shebang for default_packages_list.sh 2016-08-08 16:35:20 +00:00
prepare_packages.sh Use FQN for naming packages which we upload 2016-08-12 15:42:29 +03:00

README.rst

Setup

For using muranoclient please also specify necessary credentials in environment:

export OS_USERNAME=user export OS_PASSWORD=password export OS_TENANT_NAME=tenant export OS_AUTH_URL=http://auth.example.com:5000/v2.0 export MURANO_URL=http://murano.example.com:8082/

Examples

Build Gerrit and Jenkins: ./tools/prepare_packages.sh -s $source_dir -d $destination_dir -p Gerrit -p Jenkins

Build all packages with default settings: ./tools/prepare_packages.sh -s $source_dir -d $destination_dir or ./tools/prepare_packages.sh

Upload existing packages without building them: ./tools/prepare_packages.sh -S -U -d $destination_dir "