Skip to content

Commit 511a3df

Browse files
committed
Update marketplace screenshot
1 parent c81c72b commit 511a3df

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

_docs/pipelines/introduction-to-codefresh-pipelines.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ max-width="70%"
7474

7575
1. The first step runs under the context of a Node image that prepares the application and runs unit tests.
7676
1. The second step uses an image with s3 command line tools and uploads the test results to a bucket that holds test reports.
77-
1. The helm step creates a Helm chart and pushes it to a Helm repository.
77+
1. The third step creates a Helm chart and pushes it to a Helm repository.
7878

7979
You don't need to contact Codefresh and ask them to add the S3 executable on the build runners. You just use a prebuilt Docker image that contains it. The version used for Node is defined by you and if you wish to upgrade to another version
8080
you simply change the definition of the pipeline.
@@ -102,7 +102,7 @@ or your own) to use a build context in your step. This makes Codefresh a future-
102102
that exist now and all of them that will appear in the future. As long as there is a Docker image for a tool, Codefresh
103103
can use it in a pipeline without any extra configuration.
104104

105-
Codefresh also offers a [marketplace](https://codefresh.io/steps/){:target="\_blank"} with several existing plugins.
105+
Codefresh also offers a [marketplace](https://codefresh.io/steps/){:target="\_blank"} with dozens of existing plugins.
106106

107107
{% include
108108
image.html

images/pipeline/plugin-directory.png

201 KB
Loading

0 commit comments

Comments
 (0)