Skip to content

Commit c556ee5

Browse files
committed
Cleanup Continuous Infrastructure
This commit tackles cleaning up some of the wording in CI documentation and adds a section on downloading CI artifacts (layout-tests, binaries, etc...).
1 parent 48b2dc7 commit c556ee5

File tree

1 file changed

+13
-6
lines changed
  • Sources/WebKit/WebKit.docc/InDepth/Build

1 file changed

+13
-6
lines changed

Sources/WebKit/WebKit.docc/InDepth/Build/CI.md

Lines changed: 13 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,23 +2,30 @@
22

33
## Overview
44

5-
WebKit’s CI ([continuous integration](https://en.wikipedia.org/wiki/Continuous_integration)) infrastructure is located at [build.webkit.org](https://build.webkit.org/)).
5+
WebKit’s CI ([continuous integration](https://en.wikipedia.org/wiki/Continuous_integration)) infrastructure is located at [build.webkit.org](https://build.webkit.org/).
66

7-
[build.webkit.org](https://build.webkit.org/) will build and test commits from WebKit in the chronological order
8-
and report test results to [results.webkit.org](https://results.webkit.org/).
9-
Due to the chronological ordering, results could be a few hours behind during the work week.
7+
The CI will build and test commits from WebKit in chronological order and report test results to [results.webkit.org](https://results.webkit.org/).
8+
Due to chronological ordering, results may require several hours to complete during peak times.
109

10+
## Dashboard
1111

1212
We also have a dashboard to monitor the health of [build.webkit.org](https://build.webkit.org/)
1313
at [build.webkit.org/dashboard](https://build.webkit.org/dashboard/).
1414
If you observe that some bots are offline, or otherwise not processing your patch,
1515
please notify [[email protected]](mailto:[email protected]).
1616

17-
This dashboard isn't great for investigating individual test failures,
17+
## Results
18+
19+
This dashboard isn't great for investigating individual test failures;
1820
[results.webkit.org](https://results.webkit.org/) is a better tool for such investigations.
1921
It keeps track of individual test status by configuration over time.
2022
You can search individual tests by name or look at the historical results of entire test suites.
2123
These results will link back to the test runs in Buildbot which are associated with a specific failure.
2224
See layout tests section for more details on how to use these tools to investigate test failures observed on bots.
2325

24-
FIXME: Add a section about downloading build products from build.webkit.org.
26+
## CI Artifacts
27+
28+
The test results and build artifacts are available to download for every CI run.
29+
Upon opening the specific run you can find the layout test results available for download under
30+
`layout-test`. The binaries used for the run can be found using the link in `download-build-product`.
31+
Other tests like `run-api-tests` also have their logs available for download in their respective sections.

0 commit comments

Comments
 (0)