aboutsummaryrefslogtreecommitdiff
path: root/kolla
diff options
context:
space:
mode:
authorJoshua Harlow <jxharlow@godaddy.com>2016-11-21 18:28:32 -0800
committerJoshua Harlow <jxharlow@godaddy.com>2016-12-01 16:13:55 -0800
commitec8e72df7a9b04a3e5977cf23b12ba1fdf8a1f57 (patch)
tree50aa5ec4e255f5ac25c31a136a63380dd9f8e1a3 /kolla
parent8b57bb070e03f07c27c8370c70e2a3bb79f76660 (diff)
downloadkolla-ec8e72df7a9b04a3e5977cf23b12ba1fdf8a1f57.tar.gz
kolla-ec8e72df7a9b04a3e5977cf23b12ba1fdf8a1f57.zip
Don't process/queue children not matched
It seems like children that are unmatched are still submitted onto the queue (and then they don't do anything) when we can just avoid that processing in the first place by just not submitting them in the first place. Change-Id: I5d576faab25b3a47b395b9f627b131370d31e191
Diffstat (limited to 'kolla')
-rwxr-xr-xkolla/image/build.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/kolla/image/build.py b/kolla/image/build.py
index f84193be5..3816fc8e4 100755
--- a/kolla/image/build.py
+++ b/kolla/image/build.py
@@ -266,6 +266,8 @@ class BuildTask(DockerTask):
])
if self.image.children and self.success:
for image in self.image.children:
+ if image.status == STATUS_UNMATCHED:
+ continue
followups.append(BuildTask(self.conf, image, self.push_queue))
return followups