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
Repeat the step for other applications, and then click **Start Build**.
56
+
3. Similar to application, you can also [pass build parameters](./deploying-application/triggering-ci.md#passing-build-parameters) in application groups before triggering the build.
57
57
58
-
58
+
{% hint style="info" %}
59
+
Passing build parameters feature is only available in <imgsrc="https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg">
Users need to have [Build and deploy permission](../user-guide/global-configurations/authorization/user-access.md#role-based-access-levels) or above (along with access to the environment and applications) to trigger the build
@@ -76,7 +96,7 @@ The **Configurations** tab of your application group allows you to configure the
76
96
77
97
As shown below, you can handle the configurations of more than one application from a single screen.
78
98
79
-
99
+
80
100
81
101
{% hint style="info" %}
82
102
Users need to have [Admin role](../user-guide/global-configurations/authorization/user-access.md#role-based-access-levels) or above (along with access to the environment and applications) to change their configuration. Please note, you might not be able to change the values of locked keys in deployment template. Refer [Lock Deployment Configuration](./global-configurations/lock-deployment-config.md) to know more.
@@ -89,23 +109,23 @@ The **Build & Deploy** tab of your application group helps you deploy one or mor
89
109
90
110
1. Select the applications using the checkboxes and click the **Deploy** button present at the bottom.
Users need to have [Build and deploy permission](../user-guide/global-configurations/authorization/user-access.md#role-based-access-levels) or above (along with access to the environment and applications) to initiate the deployment
@@ -125,31 +145,31 @@ In other words, you can hibernate running applications or unhibernate hibernated
125
145
126
146
1. In the `Overview` page of your application group, use the checkboxes to choose the applications you wish to hibernate, and click the **Hibernate** button.
127
147
128
-
148
+
3. Hibernation will initiate as shown below. You may close the window.
135
155
136
-
156
+
137
157
138
158
Your applications pods would be scaled down and would stop incurring costs.
139
159
140
160
#### Unhibernation Process
141
161
142
162
1. In the same `Overview` page, you can use the checkboxes to choose the hibernated applications you wish to unhibernate, and click the **Unhibernate** button.
143
163
144
-
164
+
3. Unhibernation will initiate as shown below. You may close the window.
151
171
152
-
172
+
153
173
154
174
Your applications would be up and running in some time.
155
175
@@ -159,27 +179,27 @@ Assume you have multiple applications (maybe 10, 50, 100, or more) showing up in
159
179
160
180
1. Click the filter next to the application group as shown below.
@@ -218,11 +238,11 @@ Assume you have a few applications whose [build pipelines](../reference/glossary
218
238
219
239
1. In the **Build & Deploy** tab of your application group, select the intended applications and click the **Change Branch** button present at the bottom.
2. Enter the new branch name. If your build pipeline has `Branch Regex` as the Source Type, you must ensure your new branch name matches the regex (regular expression) provided in that build pipeline. Once done, click **Update Branch**.
Users need to have [Admin role](../user-guide/global-configurations/authorization/user-access.md#role-based-access-levels) or above (along with access to the environment and applications) to update their branch
* Select the application in which the source CI pipeline is present.
218
-
* Select the source CI pipeline from the application that you selected above.
219
-
* Enter a name for the linked CI pipeline.
222
+
Thereafter, the source CI pipeline will indicate the number of Linked CI pipelines. Upon clicking it, it will display the child information as shown below. It reveals the applications and environments where Linked CI is used for deployment.
220
223
221
-
Click **Create Linked CI Pipeline**.
224
+
222
225
223
226
After creating a linked CI pipeline, you can create a CD pipeline.
224
-
Builds cannot be triggered from a linked CI pipeline; they can only be triggered from the source CI pipeline. There will be no images to deploy in the CD pipeline created from the 'linked CI pipeline' at first. To see the images in the CD pipeline of the linked CI pipeline, trigger build in the source CI pipeline. The build images will now be listed in the CD pipeline of the 'linked CI pipeline' whenever you trigger a build in the source CI pipeline.
227
+
228
+
{% hint style="warning" %}
229
+
Linked CI pipelines can't trigger builds. They rely on the source CI pipeline to build images. Trigger a build in the source CI pipeline to see the images available for deployment in the linked CI pipeline's CD stage.
Copy file name to clipboardExpand all lines: docs/user-guide/deploying-application/triggering-ci.md
+42-9Lines changed: 42 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# Triggering CI Pipelines
2
2
3
-
To trigger the CI pipeline, first you need to select a Git commit. To select a Git commit, clic the **Select Material** button present on the CI pipeline.
3
+
To trigger the CI pipeline, first you need to select a Git commit. To select a Git commit, click the **Select Material** button present on the CI pipeline.
@@ -10,9 +10,9 @@ Once clicked, a list will appear showing various commits made in the repository,
10
10
11
11
CI Pipelines with automatic trigger enabled are triggered immediately when a new commit is made to the git branch. If the trigger for a build pipeline is set to manual, it will not be automatically triggered and requires a manual trigger.
CI builds can be time-consuming for large repositories, especially for enterprises. However, Devtron's partial cloning feature significantly increases cloning speed, reducing the time it takes to clone your source code and leading to faster build times.
18
18
@@ -22,13 +22,49 @@ CI builds can be time-consuming for large repositories, especially for enterpris
22
22
* Faster software releases
23
23
* Improved productivity
24
24
25
-
Get in touch with us if you are looking for a way to improve the efficiency of your software development process
26
-
{% endhint %}
25
+
Get in touch with us if you are looking for a way to improve the efficiency of your software development process.
27
26
28
27
The **Refresh** icon updates the Git Commits section in the CI Pipeline by fetching the latest commits from the repository. Clicking on the refresh icon ensures that you have the most recent commit available.
29
28
30
29
The **Ignore Cache** option ignores the previous build cache and creates a fresh build. If selected, will take a longer build time than usual.
Users need to have [Build & deploy permission](../global-configurations/authorization/user-access.md#role-based-access-levels) or above (along with access to the environment and application) to pass build parameters.
38
+
{% endhint %}
39
+
40
+
If you wish to pass runtime parameters for a build job, you can provide key-value pairs before triggering the build. Thereafter, you can access those passed values by referencing the corresponding keys in the environment variable dictionary.
41
+
42
+
**Steps**
43
+
44
+
1. Go to the **Parameters** tab available on the screen where you select the commit.
<br /> Similarly, you may add more than one key-value pair by using the **+ Add Parameter** button.
57
+
58
+
4. Click **Start Build**.
59
+
60
+
{% hint style="info" %}
61
+
In case you trigger builds in bulk, you can consider passing build parameters in [Application Groups](../application-groups.md).
62
+
{% endhint %}
63
+
64
+
---
65
+
66
+
## Fetching Logs and Reports
67
+
32
68
Click the `CI Pipeline` or navigate to the `Build History` to get the CI pipeline details such as build logs, source code details, artifacts, and vulnerability scan reports.
33
69
34
70
To access the logs of the CI Pipeline, simply click `Logs`.
@@ -45,7 +81,4 @@ By selecting the `Artifacts` option, you can download reports related to the tas
45
81
46
82
To check for any vulnerabilities in the build image, click on `Security`. Please note that vulnerabilities will only be visible if you have enabled the `Scan for vulnerabilities` option in the advanced options of the CI pipeline before building the image. For more information about this feature, please refer to this [documentation](../../user-guide/security-features.md).
0 commit comments