|
|
@ -179,8 +179,8 @@ on https://github.com and have Git tools available on your development system. |
|
|
|
(Linux, macOS, and Windows) but some of the tools used in the sections below |
|
|
|
(Linux, macOS, and Windows) but some of the tools used in the sections below |
|
|
|
are only available on Linux and macOS. On Windows, instead of running these |
|
|
|
are only available on Linux and macOS. On Windows, instead of running these |
|
|
|
tools yourself, you will need to rely on the Continuous Integration (CI) |
|
|
|
tools yourself, you will need to rely on the Continuous Integration (CI) |
|
|
|
service ``buildkite``, which runs automatically on GitHub when you submit |
|
|
|
service using Github Actions, which runs automatically on GitHub when you submit |
|
|
|
your Pull Request (PR). You can see any failure results in the Buildkite |
|
|
|
your Pull Request (PR). You can see any failure results in the workflow |
|
|
|
details link near the end of the PR conversation list. See |
|
|
|
details link near the end of the PR conversation list. See |
|
|
|
`Continuous Integration`_ for more information |
|
|
|
`Continuous Integration`_ for more information |
|
|
|
|
|
|
|
|
|
|
@ -696,11 +696,10 @@ every Pull Request (PR) in order to verify several aspects of the PR: |
|
|
|
* Twister builds for multiple architectures and boards |
|
|
|
* Twister builds for multiple architectures and boards |
|
|
|
* Documentation build to verify any doc changes |
|
|
|
* Documentation build to verify any doc changes |
|
|
|
|
|
|
|
|
|
|
|
CI is run both on the ``buildkite`` cloud service and Github Actions and it uses |
|
|
|
CI is run on Github Actions and it uses the same tools described in the |
|
|
|
the same tools described in the `Contribution Tools`_ section. |
|
|
|
`Contribution Tools`_ section. The CI results must be green indicating "All |
|
|
|
The CI results must be green indicating "All checks have passed" before |
|
|
|
checks have passed" before the Pull Request can be merged. CI is run when the |
|
|
|
the Pull Request can be merged. CI is run when the PR is created, and |
|
|
|
PR is created, and again every time the PR is modified with a commit. |
|
|
|
again every time the PR is modified with a commit. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The current status of the CI run can always be found at the bottom of the |
|
|
|
The current status of the CI run can always be found at the bottom of the |
|
|
|
GitHub PR page, below the review status. Depending on the success or failure |
|
|
|
GitHub PR page, below the review status. Depending on the success or failure |
|
|
@ -710,17 +709,16 @@ of the run you will see: |
|
|
|
* "All checks have failed" |
|
|
|
* "All checks have failed" |
|
|
|
|
|
|
|
|
|
|
|
In case of failure you can click on the "Details" link presented below the |
|
|
|
In case of failure you can click on the "Details" link presented below the |
|
|
|
failure message in order to navigate to ``buildkite`` or ``Github Actions`` |
|
|
|
failure message in order to navigate to ``Github Actions`` and inspect the |
|
|
|
and inspect the results. |
|
|
|
results. |
|
|
|
Once you click on the link you will be taken to the ``buildkite`` summary |
|
|
|
Once you click on the link you will be taken to the ``Github actions`` summary |
|
|
|
results page where a table with all the different builds will be shown. To see |
|
|
|
results page where a table with all the different builds will be shown. To see |
|
|
|
what build or test failed click on the row that contains the failed (i.e. |
|
|
|
what build or test failed click on the row that contains the failed (i.e. |
|
|
|
non-green) build and then click on the "Tests" tab to see the console output |
|
|
|
non-green) build. |
|
|
|
messages indicating the failure. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The `builds@lists.zephyrproject.org mailing list |
|
|
|
The `builds@lists.zephyrproject.org mailing list |
|
|
|
<https://lists.zephyrproject.org/g/builds>`_ |
|
|
|
<https://lists.zephyrproject.org/g/builds>`_ archives any nightly build results |
|
|
|
archives the CI (buildkite) nightly build results. |
|
|
|
produced by CI. |
|
|
|
|
|
|
|
|
|
|
|
Contributions to External Modules |
|
|
|
Contributions to External Modules |
|
|
|
********************************** |
|
|
|
********************************** |
|
|
|