Details
-
Task
-
Resolution: Fixed
-
Normal
-
None
-
None
-
NDS Sprint 9, NDS Sprint 10
Description
From the discussions resulting from NDS-370, we agree that it would be desirable to automatically build and push any new Git tags that are pushed to nds-org on GitHub.
It may be helpful to automate the build of "master" as well for at least the NDS Labs images.
Image builds to be automated:
- Infrastructure
- NDS Labs System Shell
- NDS Labs Deploy Tools
- GlusterFS?
- NGINX / LoadBalancer?
- NDS Labs itself
- NDS Labs API server (assumes
NDS-392) - NDS Labs UI
- NDS Labs Developer Tutorial(s)?
- NDS Labs API server (assumes
- Applications
- Dataverse (dataverse, rserve, solr, dvicat, tworavens)
- iRODS (icat, cloudbrowser, cbui)
- Cloud9 (base, go, cpp, nodejs)
- Clowder / Extractors (many, many extractors...)
- ELK (logspout?)
For each of the above image repos:
- Be sure to save any tags that you would like to preserve beforehand
- Delete previous (non-automated) build from Docker Hub
- Create a new Automated Build pointing towards the Dockerfile on nds-org in Git
- Set up the automatic build of "master" to push to "latest"
- Set up an automatic build of all tags to push to their tag name
- Leave tag name blank to build all newly-pushed Git tags into images
- Leave Docker tag name blank to name the image tag after the Git tag
- Trigger the build to ensure that "latest" exists
- Trigger each desired tag explicitly as well
This ticket is complete when nds-org has been fully automated on all tags, and optionally "master".