Comment 1 for bug 2007650

Revision history for this message
Jürgen Gmach (jugmac00) wrote (last edit ):

The documentation may not be clear enough, but where did you read that a pipeline could specify a list of list of jobs?

A pipeline could either consist of one job or of a list of jobs, and you could have multiple pipelines

From the specification ( https://docs.google.com/document/d/14MXIbRTBpp8bvtxJBOR12S9JcLisdNJi9r3taJx96LE/edit )

```
pipeline:
  - [test, lint] # this stage is a list, which means jobs are executed in parallel
  - build-wheel # this stage will only execute if previous steps in the pipeline passed
```

As already mentioned in the ~lpcrafters channel, parallel job / pipeline execution is currently not yet implemented. [needs to be documented]

AFAIK we only ever intended to implement the parallel execution on the Launchpad level, not in lpcraft. [needs to be clarified and documented]

Not executing jobs in parallel is one thing, a stalled CI pipeline is another.

Having a look at the commit history, it seems that the isses started with the introduction of list of lists for a single pipeline.

https://git.launchpad.net/~alexmurray/qa-regression-testing/commit/?id=cea273d3efb01c1e67721de7bd2969942f4f05a7

So the first thing to check would be the yaml parser / write a failing test for that case for Launchpad - as we had to use a different parser for Launchpad, as Launchpad is on an older version.

The most interesting bit is ... why is CI stalled even after reverting the changes?