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/userguide/dev/ci.md
+10-3Lines changed: 10 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,7 +55,7 @@ Individual tests can be configured in the ICU Github repository:
55
55
7. If a new test (check) needs to be added, use the search box above the table and type the display name of the check, then click on it in the drop down list to add it to the table of required checks.
56
56
57
57
58
-
## Github Actions Configuration
58
+
## Github Actions
59
59
60
60
ICU uses [Github Actions](https://github.com/features/actions) to run unit tests, environment tests, deployments of the User Guide, etc.
61
61
@@ -109,7 +109,7 @@ the workflow will not run and Github is not capable of ignoring the check in tha
109
109
110
110
Open Source users can now access machines with [at least 4 cores available per job](https://github.blog/2024-01-17-github-hosted-runners-double-the-power-for-open-source/).
111
111
112
-
## Azure Pipelines Configuration
112
+
## Azure Pipelines
113
113
114
114
ICU also uses [Azure Pipelines](https://azure.microsoft.com/en-us/products/devops/pipelines) to run CI jobs.
115
115
@@ -168,4 +168,11 @@ Note: The triggers for merges to a branch (ex: `main`) may need to be duplicated
168
168
169
169
### Caveats
170
170
171
-
In order to set up a pipeline, a person must simultaneously has access to the Azure Pipelines project for ICU and to the Github ICU repository.
171
+
In order to set up a pipeline, a person must simultaneously have access to the Azure Pipelines project for ICU and to the Github ICU repository.
172
+
173
+
If an Azure Pipeline only has one job,
174
+
that job might not be shown on a PR's main page within the list of all of the running CI checks.
175
+
There will only be an entry with the pipeline name in the list of checks.
176
+
However, if an Azure Pipeline has multiple jobs,
177
+
then each of the constituent jobs of the pipeline will be represent in the list of checks,
0 commit comments