Name: cloudbreak-deployer
Owner: Hortonworks Inc
Description: Cloudbreak Deployer Tool
Created: 2015-03-18 09:40:45.0
Updated: 2018-01-04 21:36:16.0
Pushed: 2018-01-15 15:51:24.0
Homepage: https://goo.gl/NbswU2
Size: 11429
Language: Shell
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
Install GO:
install go
Export GOPATH and add to PATH the go/bin directory:
Get cloudbreak-deployer project with GO:
et github.com/hortonworks/cloudbreak-deployer
Development process happens on separate branches. Open a pull-request to contribute your changes.
To build the project:
ke deps needed only once
deps
install
To run the unit tests:
tests
If you want to test the binary CircleCI build from your branch named fix-something
, to validate the PR binary cbd
tool will be tested. It is built by CircleCI for each branch.
ch=fix-something
le_url=https://circleci.com/api/v1/project/hortonworks/cloudbreak-deployer
le_token=[CIRCLE_TOKEN]
st_build=$(curl -s -G -d circle-token=${circle_token} ${circle_url}/tree/${branch}?filter=completed\&limit=1 | grep -m 1 build_num | sed 's/[^0-9]*//g')
-sL $(curl -s -G -d circle-token=${circle_token} ${circle_url}/${latest_build}/artifacts | grep url | grep -i $(uname) | cut -d\" -f 4) | tar -xz -C $(dirname $(which cbd))
We recommend that you always use the latest release, but you might also want to check new features or bugfixes in the master
branch.
All successful builds from the master
branch are uploaded to the public S3 bucket. You can download it using:
-L s3.amazonaws.com/public-repo-1.hortonworks.com/HDP/cloudbreak/cloudbreak-deployer_snapshot_$(uname)_x86_64.tgz | tar -xz
Instead of overwriting the released version, download it to a local directory and use it by referring to it as ./cbd
d --version
Shell scripts shouldn?t raise exceptions when it comes to unit testing. basht is used for testing. See this link to learn why not bats or shunit2.
You must cover your bash functions with unit tests and run the test with:
tests
The master branch is always built on CircleCI.
When you want to create a new release, run:
release-next-ver
The make release-next-ver
performs the following steps:
master
branch:VERSION
file by increasing the patch version number (For example, from 0.5.2 to 0.5.3).CHANGELOG.md
with the release date.CHANGELOG.md
.release-0.5.x
.origin/master
.release
branch.Now you should test this release. You can update to it by running curl -L -s https://github.com/hortonworks/cloudbreak-deployer/archive/release-x.y.z.tar.gz | tar -xz -C $(dirname $(which cbd))
. Comment with LGTM (Looking Good To Me).
Once the PR is merged, CircleCI will:
v
prefix like: v0.0.3
.