Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Aye. There are two ways to do this: tasks and stages. My guess is that you want stages.</p> <p>To have your builds running in parallel, you must have several jobs running inside one stage. If you take the jobs that can't be run in parallel and put them in separate stages, they will run serially. For example, if you have:</p> <pre><code>Test Foo Stage: Init Foo Database Job Hammer Foo Database Job Smash Foo Database Job Test Baz Stage: Init Baz Database Job Bamboozle Baz Database Job Befuddle Baz Database Job </code></pre> <p>Then the Init/Hammer/Smash of the foo stage will run problematically in parallel. However, you can put each in its own stage:</p> <pre><code>Test Foo Init Stage: Init Foo Database Job Test Foo Hammer Stage: Hammer Foo Database Job Test Foo Smash Stage: Smash Foo Database Job Test Baz Init Stage: Init Baz Database Job Test Baz Bamboozle Stage: Bamboozle Baz Database Job Test Baz Befuddle Stage: Befuddle Baz Database Job </code></pre> <p>Then, each task will run in serial, not parallel. Of course, this effectively limits you to a single useful agent.</p> <p>If you really want to only use a single agent, you can always disable all but one agent, but that will affect all the builds, so that wouldn't be a good idea if you want anything to run in parallel.</p> <p>And as a last comment, it is also possible to get where you want with tasks instead of stages. Concatenate the tasks from each Job and they will be run in serial by a single agent. Of course, each task will see the changed files and state from the previous task, so you'll want to make sure they won't interfere.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload