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

Commit6490e36

Browse files
author
Ted Spinks
authored
Clarify working directory behavior (codefresh-io#322)
* Update what-is-the-codefresh-yaml.mdClarify details about the working_directory field.* Update what-is-the-codefresh-yaml.mdRevise details about the working_directory field
1 parentda9572a commit6490e36

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

‎_docs/codefresh-yaml/what-is-the-codefresh-yaml.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -153,8 +153,8 @@ In the context of a step, a working directory can be of the following type:
153153
{: .table .table-bordered .table-hover}
154154
| Working Directory| Description|
155155
| ---------------------------------------------------------------------------------------------------------------------------------------------| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
156-
| Empty| Defaults to the[Codefresh volume]({{site.baseurl}}/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines/#sharing-the-workspace-between-build-steps) (found at`/codefresh/volume`). If there is a[git clone step]({{site.baseurl}}/docs/codefresh-yaml/steps/git-clone/) with the special name`main_clone` then the default working directory is now the[project folder]({{site.baseurl}}/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines/#cloning-the-source-code) that was checked out.|
157-
| Variable that contains the ID of a[Git-Clone]({{site.baseurl}}/docs/codefresh-yaml/steps/git-clone/) step| Runs the step within the cloned directory.If you name your clone step as`main_clone` then all subsequent pipeline steps will automatically use that cloned directory as working directory. This only applies to[built-in]({{site.baseurl}}/docs/codefresh-yaml/steps/#built-in-steps) Codefresh steps and not[custom plugins]({{site.baseurl}}/docs/codefresh-yaml/steps/#creating-a-typed-codefresh-plugin).|
156+
| Empty| Defaults to the[Codefresh volume]({{site.baseurl}}/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines/#sharing-the-workspace-between-build-steps) (found at`/codefresh/volume`). If there is a[git clone step]({{site.baseurl}}/docs/codefresh-yaml/steps/git-clone/) with the special name`main_clone` then the default working directoryfor built-in stepsis now the[project folder]({{site.baseurl}}/docs/configure-ci-cd-pipeline/introduction-to-codefresh-pipelines/#cloning-the-source-code) that was checked out - this only applies to[built-in]({{site.baseurl}}/docs/codefresh-yaml/steps/#built-in-steps) Codefresh steps and not[custom plugins]({{site.baseurl}}/docs/codefresh-yaml/steps/#creating-a-typed-codefresh-plugin).|
157+
| Variable that contains the ID of a[Git-Clone]({{site.baseurl}}/docs/codefresh-yaml/steps/git-clone/) step| Runs the step within the cloned directory.|
158158
| Variable that contains the ID of any other step| Runs the step within the same working directory that the specified was executed. This option is not available for for[**Git-Clone**]({{site.baseurl}}/docs/codefresh-yaml/steps/git-clone/) steps.|
159159
| Absolute filesystem path| Treated as is within the container.|
160160
| Relative filesystem path| Treated as relative path from the cloned directory of the service|

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp