Age | Commit message (Collapse) | Author | Files | Lines |
|
This runs `tox` against any changes to the dashboard in the pharos-tools
repository.
Change-Id: Ia58e20973f38dda350eb5ff4e89746f97b829560
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Instead of deploying the dashboard when changes to any file happens,
only changes to the docker-compose.yml file should trigger a deploy.
The deployment process would then be as follows:
- Tag pharos-tools
- Create a patch to set the tag in 'docker-compose.yml'
- Merge the patch
- New version of dashboard deployed at specific tag
Change-Id: I67a6237f00b96021df24e7a79a063d31f43df5a6
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Moves the pharos dashboard jobs to their own file sperate and deploys
the dashboard when changes are merged to master.
Note: this may need to be manually triggered due to the timing
between the container being built and it being availble to be pulled.
Also includes the following changes to the job:
- Uploads backups to Google Storage
- Remove sudo usage as docker can be ran as the Jenkins user
- Renames jobs to match general naming scheme
JIRA: PHAROS-394
Change-Id: I516c4414d7b0158f1f8478214c10f0aa7d176739
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|