From 3aa372722546252f629ad996ce206ece5ab7e582 Mon Sep 17 00:00:00 2001 From: "James E. Blair" Date: Fri, 27 Sep 2013 08:33:10 -0700 Subject: [PATCH] Allow multiple invocations of the same job Previously if a job was listed more than once for a project, it was ignored. That's pretty arbitrary (it silently dropped the second without an error; and if there are two, which is the right one anyway?). OTOH, it's potentially useful to run a job more than once in order to increase the chance of encountering notdeterministic behavior. And if listing a job twice is an error, it is now more likely to be noticed by the operator. This removes the check for duplicate invocations of a job. Change-Id: If8e2e8cc3fca855bd6b14eb3a957dadddfe143ed --- zuul/model.py | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/zuul/model.py b/zuul/model.py index 3b5a1a5cf5..0b197bed58 100644 --- a/zuul/model.py +++ b/zuul/model.py @@ -532,10 +532,9 @@ class JobTree(object): self.job_trees = [] def addJob(self, job): - if job not in [x.job for x in self.job_trees]: - t = JobTree(job) - self.job_trees.append(t) - return t + t = JobTree(job) + self.job_trees.append(t) + return t def getJobs(self): jobs = []