Group not respected when used with matrix in .drone.yaml

Should group take higher precedence than matrix?

Drone file looks like this:

    - ENV11: val11
      ENV21: val21
    - ENV12: val12
      ENV22: val22

    group: group1

    group: group2

I see that step1 and step2 are executed in parallel instead of step1 run first and then step2.

Groups are limited to each matrix build, so this is an expected behavior.

@tboerger is correct, the group attribute will not control matrix concurrency. The matrix and parallel features are separate features, used to solve two different use cases. Let me provide a bit more detail to help better clarify –

The use case for matrix pipelines are testing multiple configurations in parallel. For example, you want to test your code using Go 1.5, Go 1.6, and Go 1.7. A matrix configuration essentially creates multiple copies of a pipeline, one for each permutation, and then executes each permutation in parallel. They execute completely independently of one another. This means there is no way for one matrix permutation (e.g. Go 1.5) to wait for or yield to another matrix permutation (e.g. Go 1.6).

The use case for parallel steps (groups) are when you want a single pipeline execution to fan out and then fan back in. For example, maybe you want your Go 1.7 unit tests to run in parallel so that your pipeline executes more quickly.

It is possible to use these features, matrix steps and parallel step execution, together. For example, imagine you wanted to test your codebase against Go 1.5, 1.6, and 1.7. That would be a matrix build. Now image you have a large test suite. You could parallelize your unit tests for each version of Go.

The yaml might look something like this:

    image: plugins/git

    image: golang:${go_version}
      - go test ./unit/...
    image: golang:${go_version}
      - go test ./integration/...
    image: plugins/slack
        golang: 1.7

    - 1.7
    - 1.8

So how will the above yaml execute? We can visualize what this would look like below:

I hope that helps provide a bit more information about these two independent features, how they work, and how they can potentially be used together.

Thanks @tboerger and @bradrydzewski.

@bradrydzewski: Regarding your example. what would I add to the .drone.yaml if I wanted to execute a step just before Finish that runs after all previous tasks are complete? (in essence sequentially)

1 Like

@ptagr and @bradrydzewski would be interested on the same feature. We have some very IO-bound steps which we like to run on different agents using matrix builds and then only in the case they all succeed run certain steps after them. Could this be achieved with a custom plugin ?

@pyry there is really no way to enable this behavior, even with plugins.

Matrix builds are intended for testing different configurations (multiple versions of redis, node, etc). Using matrix builds to parallelize tasks across machines is more of a hack, since this is not the intended use case. There is an open issue for tracking proper multi-machine parallelism that you can subscribe to for updates at