...
- Roll forward version numbers in source code and ensure that all values match:
- Swagger API
- apis/swagger-spec/ndslabs.yaml: NDS Labs swagger API spec version number
- API Server:
- apiserver/build.sh: NDS Labs API Server Docker image version tag
- apiserver/version.go: NDS Labs API / Server version number
- CLI Client:
- apictl/build.sh: NDS Labs CLI version number
- apictl/cmd/clientVersion.go: NDS Labs CLI / API version number
- UI Client:
- gui/Dockerfile.ndslabs-gui: NDS Labs UI / webserver Docker image version tag
- gui/js/package.json: NDS Labs UI / webserver NPM package version number
- gui/js/bower.json: NDS Labs UI Angular app Bower package version number
- gui/js/app/app.js: NDS Labs UI Angular app build version number
- Swagger API
- Regenerate Swagger API / Client from spec (if the spec has changed)
- apiserver/???: generated Go swagger server
- gui/js/app/shared/api.js: generated AngularJS swagger client
- Build new Docker images from master branch
- API: ./build.sh build && ./build.sh release
- GUI: ./build.sh -c && ./release.sh version-number
- Tag / push new images to DockerHub (version tag: push, latest: push)
- Commit and push new build version / date(s) to upstream master on GitHub
- Create a new tag in GtiHub for the new version
Repositories that will need to be tagged:
- ndslabs (API server / REST API / CLI / UI)
- ndslabs-specs (specs)
- ndslabs-devenvs (developer environments)
- gluster (global file system)
- deploy-tools (ansible scripts)