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
{{ message }}
This repository was archived by the owner on Nov 5, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: docs/modules/ROOT/pages/getting-started/get-started.adoc
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,3 @@
1
-
sectlinks
2
-
3
1
= Getting started
4
2
5
3
{ProductName} is a multi-tenant, software as a service (SaaS) based continuous integration and continuous delivery (CI/CD) service with an emphasis on secure supply chain features.
@@ -39,6 +37,7 @@ There are many perks to forking one of our samples, for example:
39
37
* Rebuilding dependencies from source
40
38
* Scanning your build for vulnerabilities, viruses, and other checks
41
39
40
+
[#How to fork a sample]
42
41
==== How to fork a sample
43
42
44
43
To fork the sample, complete the following steps:
@@ -52,14 +51,16 @@ To fork the sample, complete the following steps:
52
51
Right now we support GitHub, but come back soon for other Git providers!
53
52
====
54
53
54
+
55
55
=== Importing the code from your forked repository
56
56
57
57
. Return to the app and scroll up to *Bring in your own code*.
58
58
. In *Git repository URL*, paste the URL that you copied in the previous section.
59
59
. Click *Import code*.
60
60
61
+
[#Reviewing and configuring]
61
62
=== Reviewing and configuring
62
-
We now scan your Git repository for source code and detect your runtime and other configuration settings for you to review. You have the option to use our default build pipeline or to customize the pipeline. In this getting started guide, we'll stick with the default option.
63
+
We now scan your Git repository for source code and detect your runtime and other configuration settings for you to review. You have the option to use our default build pipeline or to customize the pipeline. Let's stick with the default option for now.
63
64
64
65
Complete the following steps to finish the process:
65
66
@@ -80,15 +81,17 @@ Great work! You're done with the first steps.
80
81
81
82
Because your application can run on one or more components, you might want to add more.
82
83
83
-
The additional source code that you add can either be from the same repository that you used when you created your application, _or_ a different Git repository. Remember, we call source code _components_.
84
+
The additional source code that you add can either be from the _same_ repository that you used when you created your application, or a _different_ Git repository. Remember, we call source code _components_.
84
85
85
86
In the *Overview* tab, select *Add component*:
86
87
87
88
image::Add_more_components.png[Overview tab that shows how you can add additional components to your application. The Overview button is on the bottom left and has a red arrow next to it.]
88
89
90
+
Follow the process in <<How to fork a sample>> to add any additional components.
91
+
89
92
=== Customizing your build pipeline
90
93
91
-
In this guide, we used the default built pipeline. To add automation, you can upgrade to custom build pipelines.
94
+
In the <<Reviewing and configuring>> section, you used the default built pipeline. To add automation, you can upgrade to custom build pipelines.
92
95
93
96
Custom build pipelines are pipelines as code, set on your component's repository. With custom build pipelines, pull requests and commits to your main branch automatically rebuild.
94
97
@@ -128,6 +131,8 @@ image::Application_route.png[In the Components tab, there is a link called Route
128
131
=== Managing compliance with Enterprise Contract
129
132
The Enterprise Contract (EC) is an artifact verifier and customizable policy checker. You can use EC to keep your software supply chain secure and to ensure that container images comply with your organization’s policies.
130
133
134
+
For more information about EC, refer to xref:how-to-guides/proc_managing-compliance-with-the-enterprise-contract.adoc[Managing compliance with the Enterprise Contract].
135
+
131
136
=== Deploying your app
132
137
Check the status of your application in *Environments*. You can view information about your environment such as its type, strategy, and deployment status:
133
138
@@ -141,7 +146,7 @@ For information about creating an application with your own cluster, refer to xr
141
146
142
147
A software bill of materials (SBOM) is a list of all the software libraries that a component uses. You can run 'cosign' in your command line interface (CLI) to inspect the image SBOM.
143
148
144
-
For more information on this topic, go to xref:how-to-guides/Secure-your-supply-chain/proc_inspect_sbom.adoc.
149
+
For more information on this topic, go to xref:how-to-guides/Secure-your-supply-chain/proc_inspect_sbom.adoc[Inspecting SBOMs].
0 commit comments