From d447d287c8ba80f2689d365dd7574f887ce8cc27 Mon Sep 17 00:00:00 2001 From: Trevor Bramwell Date: Thu, 1 Nov 2018 18:11:11 -0700 Subject: Deploy Pharos Dashboard on changes to compose file 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 --- jjb/pharos/pharos-tools.yml | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/jjb/pharos/pharos-tools.yml b/jjb/pharos/pharos-tools.yml index 507e93eb3..ac5d1956e 100644 --- a/jjb/pharos/pharos-tools.yml +++ b/jjb/pharos/pharos-tools.yml @@ -44,10 +44,7 @@ - gerrit-trigger-change-merged: branch: 'master' project: '{project}' - # In the future this should be switch to just the compose file - # for when tags are updated - # files: 'dashboard/docker-compose.yml' - files: 'dashboard/**' + files: 'dashboard/docker-compose.yml' builders: - shell: -- cgit 1.2.3-korg