You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: _docs/pipelines/conditional-execution-of-steps.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -242,6 +242,10 @@ Try running the pipeline above and see how it behaves when a variable called `MY
242
242
243
243
>Notice that if you use this pattern a lot it means that you are trying to create a complex pipeline that is very smart. We suggest you create instead multiple[simple pipelines for the same project]({{site.baseurl}}/docs/ci-cd-guides/pull-request-branches/#trunk-based-development).
244
244
245
+
246
+
##Single step dependencies
247
+
When[parallel execution]({{site.baseurl}}/docs/docs/pipelines/advanced-workflows/#parallel-pipeline-execution) is enabled, the`when:` conditional can be used to set up step dependencies using the`steps:` and`on:` keywords. For more information,[check the parallel pipeline execution page]({{site.baseurl}}/docs/docs/pipelines/advanced-workflows/#parallel-pipeline-execution).
248
+
245
249
##Related articles
246
250
[Codefresh YAML for pipeline definitions]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/)
247
251
[Variables in pipelines]({{site.baseurl}}/docs/pipelines/variables/)