Fwd: Re: Odd behaviour regarding missing job parent
Forwarding my reply to ml because I forgot to cc. -yoctozepto -------- Forwarded Message -------- Subject: Re: Odd behaviour regarding missing job parent Date: Wed, 10 Jun 2020 08:48:00 +0200 From: Radosław Piliszek <radoslaw.piliszek@gmail.com> To: Clark Boylan <cboylan@sapwetik.org> On 2020-06-10 00:27, Clark Boylan wrote:
That's exactly the case! I thought it might have some usage. Thanks for confirming that.
As do its docs, https://zuul-ci.org/docs/zuul/reference/job_def.html#attr-job.branches, which say: "If there is no job definition for a given job which matches the branch of an item, then that job is not run for the item."
Aye, but it gets confusing when you consider inheritance and this paragraph does not discuss it. It seems it can be extended to "not defined or having any undefined ancestor", i.e. I would not be surprised in case like: # Add undefined job foo - project: check: jobs: foo as this is easier to spot and documented there exactly.
I do think that if no branches defined that parent job then you would have received an error, but because the job is only defined on particular branches it is assumed that you only want to run those jobs on those branches.
Yeah, that makes sense. Only the inheritance part made it confuse me. -yoctozepto
participants (1)
-
Radosław Piliszek