> Run only takes one playbook.

I was convinced of this until a couple of days ago when I noticed one
of our users specifying multiple runs.
The docs also says it can take multiple:
https://zuul-ci.org/docs/zuul/reference/job_def.html#attr-job.run

> Further playbooks should not be located in zuul.d

This is probably the real problem since zuul is trying to parse the
playbooks as zuul configuration items.
Didn't someone implement a .zuulignore to be able to do just this?

On Fri, Nov 27, 2020 at 2:17 PM <Tobias.Henkel@bmw.de> wrote:
>
> Hi,
>
> I see two issues there, see below.
>
> On 27.11.20, 14:11, "Åsmund Østvold" <asmundo@gmail.com> wrote:
>
>     hi Again,
>
>     I like Zuul but it is a bit hard to get it correct. Sorry for the amount of text.
>     A project has zuul.d/job.yaml:
>     ---
>     - job:
>         name: build-and-integration-test
>         parent: base
>         run:
>           - playbooks/build_project.yaml
>           - zuul.d/run_testing.yaml
>         required-projects:
>           - zuul/irma-common-jobs
>
> Run only takes one playbook. If you want several you can move one into
> pre-run or combine them using a master playbook. Further playbooks
> should not be located in zuul.d since zuul treats this as zuul configuration
> and thus fails to parse them as they're ansible playbooks not zuul config.
>
> Cheers,
> Tobias
>
> _______________________________________________
> Zuul-discuss mailing list
> Zuul-discuss@lists.zuul-ci.org
> http://lists.zuul-ci.org/cgi-bin/mailman/listinfo/zuul-discuss