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/steps/build.md
+6-7Lines changed: 6 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -89,7 +89,7 @@ step_name:
89
89
| `image_name` | The name of the image that is built. | Required |
90
90
| `region` | Relevant only for [Amazon ECR]({{site.baseurl}}/docs/integrations/docker-registries/amazon-ec2-container-registry/) integrations using either service accounts or explicit credentials. The names of the regions for which to perform cross-region replication. The names of the source region and the destination region name must be defined in separate steps. | Optional |
91
91
| `tag` | The single tag to assign to the built image. To assign multiple tags, use `tags` (see below). <br>The default tag is the name of the branch or revision that is built. | Default |
92
-
| `tags` | Multiple tags to assign to the built image. {::nomarkdown} <br>To assign a single tag, use <span>tag</span> (see above). <br> This is an array, and should conform to the following syntax: <br><span>tags:<br>- tag1<br>- tag2<br>- {% raw %}${{CF_BRANCH_TAG_NORMALIZED}}{% endraw %}<br>- tag4</span><br><br>OR<br><span>tags: [ 'tag1', 'tag2', '{% raw %}${{CF_BRANCH_TAG_NORMALIZED}}'{% endraw %}, 'tag4' ]</span>{:/} |Optional|
92
+
| `tags` | Multiple tags to assign to the built image. {::nomarkdown} <br>To assign a single tag, use <code>tag</code> (see above). <br> This is an array, and should conform to the following syntax:<br><code>tags:<br>- tag1<br>- tag2<br>- {% raw %}${{CF_BRANCH_TAG_NORMALIZED}}{% endraw %}<br>- tag4</code><br><br>OR<br><code>tags: [ 'tag1', 'tag2', '{% raw %}${{CF_BRANCH_TAG_NORMALIZED}}'{% endraw %}, 'tag4' ]</code>{:/} |Optional|
93
93
| `cache_from` | The list of cache sources to use as Docker cache when building the image. Every source in the list is passed to the build command using the `--cache-from` flag. See [Docker documentation](https://docs.docker.com/engine/reference/commandline/buildx_build/#cache-from){:target="\_blank"} for more info. | Optional |
94
94
| `registry` | The name of the registry to which to push the built image. You can define any registry that is integrated with Codefresh. <br>When not defined, and you have multiple registry contexts, Codefresh uses the one set as the [default registry]({{site.baseurl}}/docs/docker-registries/external-docker-registries/). | Optional |
95
95
| `registry_contexts` | Advanced property for resolving Docker images when [working with multiple registries with the same domain]({{site.baseurl}}/docs/ci-cd-guides/working-with-docker-registries/#working-with-multiple-registries-with-the-same-domain). When defined, pulls the image from the specified context. <br> NOTE: When using `buildx` to build and push multi-platform images, `registry_contexts` cannot be assigned a different registry from the same domain as the target registry defined for `registry`, as Docker does not support being logged in to multiple Docker registries that share the same domain at the same time. | Optional |
@@ -469,7 +469,7 @@ steps:
469
469
buildkit: true
470
470
```
471
471
472
-
`Buildkit` is also automatically enabled if you use any of its features such as the `progress` property:
472
+
<!----`Buildkit` is also automatically enabled if you use any of its featuressuch as the `progress` property:-->
473
473
474
474
`codefresh.yml`
475
475
@@ -478,12 +478,11 @@ version: '1.0'
478
478
steps:
479
479
BuildMyImage:
480
480
title: Building My Docker image
481
-
image_name: my-app-image
482
-
type: build
483
-
progress: tty
481
+
image_name: my-app-image
484
482
```
485
483
486
-
Possible values for `progress` are `tty` and `plain`.
484
+
<!--- commenting out as not supported currently. When supported add this line to the code snippet above and remove comments:type: build
485
+
progress:ttyPossible values for `progress` are `tty` and `plain`. -->
487
486
488
487
For secrets, you can either mention them in a single line:
489
488
@@ -580,7 +579,7 @@ steps:
580
579
581
580
{% endraw %}
582
581
583
-
You can combine all options (`ssh`, `progress`, `secrets`) in a single build step if desired.
582
+
You can combine all options (`ssh`,<!---`progress`,--> `secrets`) in a single build step if desired.