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/deployments/gitops/images.md
+23-20Lines changed: 23 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,35 +15,38 @@ You can enrich the basic information reported with the image with issue-tracking
15
15
16
16
Complete these steps to see images in the Images dashboard.
17
17
18
-
1. (Mandatory) Build and push the Docker image
19
-
* Codefresh pipelines
20
-
Use the`build` step to build a Docker image declaratively in simple or multi-stage Dockerfiles. See[Build step in pipelines]({{site.baseurl}}/docs/pipelines/steps/build/).
18
+
1. (Mandatory) Build and push the Docker image
19
+
* Codefresh pipelines
20
+
Use the`build` step to build a Docker image declaratively in simple or multi-stage Dockerfiles. See[Build step in pipelines]({{site.baseurl}}/docs/pipelines/steps/build/).
21
+
The pipeline pushes the image to the default Docker registry.
22
+
You can also push the image to any external Docker registry that you integrate with Codefresh. See[Docker Registries for pipeline integrations]({{site.baseurl}}/docs/integrations/docker-registries/).
21
23
22
-
The pipeline pushes the image to the default Docker registry.
23
-
You can also push the image to any external Docker registry that you integrate with Codefresh. See[Docker Registries for pipeline integrations]({{site.baseurl}}/docs/integrations/docker-registries/).
24
-
25
-
Review different scenarios for building and pushing Docker images in our[Build/push examples]({{site.baseurl}}/docs/example-catalog/examples/#buildpush-examples).
24
+
Review different scenarios for building and pushing Docker images in our[Build/push examples]({{site.baseurl}}/docs/example-catalog/examples/#buildpush-examples).
26
25
27
-
* GitOps
28
-
Create the Docker image.
29
-
[Create a Docker image using Kaniko](https://codefresh.io/argohub/workflow-template/kaniko){:target="\_blank"}.
30
-
31
-
1. (Mandatory) GitOps: Connect to Docker registries
26
+
* GitOps
27
+
Create the Docker image.
28
+
[Create a Docker image using Kaniko](https://codefresh.io/argohub/workflow-template/kaniko){:target="\_blank"}.
29
+
30
+
{:start="2"}
31
+
1. (Mandatory) GitOps: Connect to Docker registries
32
32
Connect Docker registries to Codefresh to store Docker images.
1. (Mandatory) GitOps: Report image information to Codefresh.
36
-
This is the equivalent to pushing the image in Codefresh pipelines.
37
-
Use the[report-image-info] (https://github.com/codefresh-io/argo-hub/blob/main/workflows/codefresh-csdp/versions/0.0.6/docs/report-image-info.md){:target="\_blank"} DAG template to report image information to Codefresh.
35
+
{:start="3"}
36
+
1. (Mandatory) GitOps: Report image information to Codefresh
37
+
This is the equivalent to pushing the image in Codefresh pipelines.
38
+
39
+
Use the[report-image-info](https://github.com/codefresh-io/argo-hub/blob/main/workflows/codefresh-csdp/versions/0.0.6/docs/report-image-info.md){:target="\_blank"} DAG template to report image information to Codefresh.
38
40
39
41
>If you are using an external platform or tool for your CI pipelines such as GitHub Actions or Jenkins, or even Codefresh pipelines, we have a new template that combines image reporting and enrichment. See[GitOps CI integrations]({{site.baseurl}}/docs/gitops-integrations/ci-integrations) for details.
40
42
43
+
{:start="4"}
41
44
1. (Optional) Enrich image with annotations and metadata
42
-
Image enrichment exposes metadata such as feature requests, pull requests, and logs as part of the application’s deployment, for visibility into all aspects of the deployment, making it easier to track actions and identify root cause of failures.
Image enrichment exposes metadata such as feature requests, pull requests, and logs as part of the application’s deployment, for visibility into all aspects of the deployment, making it easier to track actions and identify root cause of failures.
Copy file name to clipboardExpand all lines: _docs/quick-start/ci-quick-start.md
+2-33Lines changed: 2 additions & 33 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,44 +1,13 @@
1
1
---
2
-
title:"Create a project for pipeline"
2
+
title:"CI quick starts"
3
3
description:""
4
4
group:quick-start
5
5
toc:true
6
6
---
7
7
8
-
Codefresh pipelines are grouped under projects. Think of a project as a folder or directory that groups related pipelines. For example, all pipleines that package/deploy the different microservices for an application.
9
-
You can define any name for the project, the most common example being the name of the application that the pipelines
10
-
11
-
###Where are you
12
-
13
-
14
-
15
-
###Before you beigin
16
-
17
-
*[Connect a Docker registry to Codefresh]({{site.baseurl}}/docs/quick-start/create-docker-registry-integration)
18
-
19
-
###How to
20
-
1. In the Codefresh UI, in the sidebar, from Pipelines, select**Projects**.
21
-
1. On the top-right, click**New Project**.
22
-
1. Enter the**Project Name**. For example,`my-first-project`.
23
-
1. Leave the**Project Tags** empty for the quick start.
24
-
1. Select any**Icon** you want. The icon is prefixed to the project name in the Projects page.