Sequences that use the same service cannot be run in parallel. If you simultaneously trigger multiple sequences for the same service, they are queued to run sequentially. Sequences for different services can be run in parallel. This is possible when you have different automation projects or if you have multiple services within a project.
You can run tasks in parallel by putting them in different stages, each of which is triggered from the previous stage. The following shipyard illustrates this. Here, you see we have three stages:
load-test-2 are triggered
so will run in parallel.
apiVersion: "spec.keptn.sh/0.2.3" kind: "Shipyard" metadata: name: "shipyard-example-parallel-tasks" spec: stages: - name: "hardening" sequences: - name: "delivery" tasks: - name: "deployment" properties: deploymentstrategy: "direct" - name: "evaluation" - name: "release" - name: "load-test-1" sequences: - name: "load-test" triggeredOn: - event: "hardening.delivery.finished" tasks: - name: "my-load-test-configuration" - name: "load-test-2" sequences: - name: "load-test" triggeredOn: - event: "hardening.delivery.finished" tasks: - name: "my-load-test-configuration"