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/testing/create-composition.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ toc: true
20
20
Compositions can be launched as part of a unit test step, an integration test step, or to run an image for manual testing. You can create compositions from scratch or import an existing`docker-compose.yml` file.
21
21
22
22
##Create composition
23
-
1. In the Codefresh UI, fromtheArtifactssectionin the sidebar,click[**Compositions**](https://g.codefresh.io/compositions){:target="\_blank"}.
23
+
1. In the Codefresh UI, from Artifacts in the sidebar,select[**Compositions**](https://g.codefresh.io/compositions){:target="\_blank"}.
24
24
1. Click**Create Composition**.
25
25
26
26
{% include
@@ -64,7 +64,7 @@ max-width="70%"
64
64
65
65
{:start="5"}
66
66
1. Click**Next**, and continue with one of the following:
Copy file name to clipboardExpand all lines: _docs/testing/integration-tests.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
---
2
-
title:"Integrationtests"
2
+
title:"Integrationtesting"
3
3
description:"Launch additional services in Codefresh pipelines"
4
4
group:testing
5
5
redirect_from:
@@ -25,7 +25,7 @@ They are much more flexible than compositions in these areas:
25
25
1. Attaching service containers to the whole pipeline instead of individual steps .
26
26
1. Auto-mounted Codefresh[shared volume]({{site.baseurl}}/docs/pipelines/introduction-to-codefresh-pipelines/#sharing-the-workspace-between-build-steps) for freestyle steps (unlike compositions), making file access very easy. You can execute your tests from the Git repository that was cloned.
27
27
28
-
>This article explains how to run additional services that are automatically discarded once the pipeline has completed its run. If you are interested in temporary test environments, see the[preview environments]({{site.baseurl}}/docs/getting-started/on-demand-environments/).
28
+
>This article explains how to run additional services that are automatically discarded once the pipeline has completed its run. If you are interested in temporary test environments, see the[preview environments]({{site.baseurl}}/docs/quick-start/ci-quickstart/on-demand-environments/).
Copy file name to clipboardExpand all lines: _docs/testing/security-scanning.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -42,8 +42,8 @@ Common strategies are:
42
42
43
43
44
44
Here is an example pipeline that scans a Docker image:
45
-
* With[Aqua](https://www.aquasec.com/){:target="\_blank"} after being pushed to the[default Docker registry]({{site.baseurl}}/docs/docker-registries/external-docker-registries/#the-default-registry)
46
-
* Before it is promoted to the[external Azure Registry]({{site.baseurl}}/docs/docker-registries/external-docker-registries/azure-docker-registry/){:target="\_blank"}.
45
+
* With[Aqua](https://www.aquasec.com/){:target="\_blank"} after being pushed to the[default Docker registry]({{site.baseurl}}/docs/integrations/docker-registries/#default-registry).
46
+
* Before it is promoted to the[external Azure Registry]({{site.baseurl}}/docs/docker-registries/azure-docker-registry/).
47
47
48
48
{% include image.html
49
49
lightbox="true"
@@ -181,7 +181,7 @@ max-width="60%"
181
181
182
182
##Security annotations
183
183
184
-
Security scan results are also a perfect candidate for[extra metadata]({{site.baseurl}}/docs/docker-registries/metadata-annotations/) to add to your Docker images.
184
+
Security scan results are also a perfect candidate for[extra metadata]({{site.baseurl}}/docs/pipelines/docker-image-metadata/) to add to your Docker images.
185
185
186
186
{% include image.html
187
187
lightbox="true"
@@ -196,6 +196,6 @@ You can add any metadata such as the number of issues for each category or even
196
196
197
197
##Related articles
198
198
[Codefresh YAML for pipeline definitions]({{site.baseurl}}/docs/pipelines/what-is-the-codefresh-yaml/)
Copy file name to clipboardExpand all lines: _docs/testing/test-reports.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -124,7 +124,7 @@ max-width="80%"
124
124
125
125
You will use the name of the integration as an environment variable in your Codefresh pipeline.
126
126
127
-
You can also use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/pipeline-integrations/secret-storage/) (such as Kubernetes secrets), as values, by clicking on the lock icon that appears next to field:
127
+
You can also use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/secret-storage/) (such as Kubernetes secrets), as values, by clicking on the lock icon that appears next to field:
128
128
* If you have already specified the resource field during secret definition, just enter the name of the secret directly in the text field, for example,`my-secret-key`.
129
129
* If you didn't include a resource name during secret creation, enter the full name in the field, for example,`my-secret-resource@my-secret-key`.
130
130
@@ -153,7 +153,7 @@ max-width="60%"
153
153
154
154
You will use the name of the integration as an environment variable in your Codefresh pipeline.
155
155
156
-
You can also use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/pipeline-integrations/secret-storage/) (such as Kubernetes secrets), as values, by clicking on the lock icon that appears next to field:
156
+
You can also use any[external secrets that you have defined]({{site.baseurl}}/docs/integrations/secret-storage/) (such as Kubernetes secrets), as values, by clicking on the lock icon that appears next to field:
157
157
* If you have already specified the resource field during secret definition, just enter the name of the secret directly in the text field, for example,`my-secret-key`.
158
158
* If you didn't include a resource name during secret creation, enter the full name in the field, for example,`my-secret-resource@my-secret-key`.