Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Update advanced-workflows.md#382

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
NimRegev merged 1 commit intomasterfromclassic-CR-9719
Mar 9, 2022
Merged
Changes fromall commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions_docs/codefresh-yaml/advanced-workflows.md
View file
Open in desktop
Original file line numberDiff line numberDiff line change
Expand Up@@ -303,11 +303,12 @@ first.txt second.txt

This illustrates the side effects for both parallel steps that were executed on the same volume.

>It is therefore your responsibility to make sure that steps that run in parallel playnice with each other. Currently Codefresh performs no conflict detection at all. If there are race conditions between your parallel steps (e.g. multiple steps writing at the same files) the final behavior is undefined. It is best to start with a fully sequential pipeline and use parallelism in a gradual manner if you are unsure about the side effects of your steps
>It is therefore your responsibility to make sure that steps that run in parallel play nice with each other. Currently, Codefresh performs no conflict detection at all. If there are race conditions between your parallel steps, (e.g. multiple steps writing at the same files), the final behavior is undefined. It is best to start with a fully sequential pipeline, and use parallelism in a gradual manner if you are unsure about the side effects of your steps

## Implicit parallel steps
> If you use implicit parallel steps, you _cannot_ use _parallel pipeline mode_.

In all the previous examples, all parallel steps have been defined explicitly in a pipeline. This works well for a small number of steps, but in some cases it can be cumbersome to write suchasa pipeline, especially when the parallel steps are similar.
In all the previous examples, all parallel steps have been defined explicitly in a pipeline. This works well for a small number of steps, but in some cases it can be cumbersome to write such a pipeline, especially when the parallel steps are similar.

Codefresh offers two handy ways to lessen the amount of YAML you have to write and get automatic parallelization with minimum effort.

Expand DownExpand Up@@ -524,6 +525,7 @@ of matrix variations can quickly grow if you add too many dimensions.
Notice that, as with the `scale` syntax, the defined values/properties are merged between parent step (`MyUnitTests` in the example above) and children steps. For example, if you set an environment variable on the parent and also on child matrix steps , the result will a merged environment where all values are available.

## Parallel pipeline mode
> If you use parallel pipeline mode, you _cannot_ use _implicit parallel steps_.

To activate advanced parallel mode for the whole pipeline you need to declare it explicitly at the root of the `codefresh.yml` file:

Expand Down

[8]ページ先頭

©2009-2025 Movatter.jp