From bad2ee780e88331acf92cdddaa839a40635e0b08 Mon Sep 17 00:00:00 2001 From: Anas Nashif Date: Fri, 19 Feb 2021 15:58:46 -0500 Subject: [PATCH] doc: remove references to shippable We now use buildkite and GH actions. Signed-off-by: Anas Nashif --- README.rst | 2 +- doc/contribute/index.rst | 13 +++++++------ 2 files changed, 8 insertions(+), 7 deletions(-) diff --git a/README.rst b/README.rst index fb02a0bd233..021018c1b47 100644 --- a/README.rst +++ b/README.rst @@ -62,7 +62,7 @@ Here's a quick summary of resources to help you find your way around: subgroups`_ have their own archives and sign-up pages. * **Nightly CI Build Status**: https://lists.zephyrproject.org/g/builds The builds@lists.zephyrproject.org mailing list archives the CI - (shippable) nightly build results. + (buildkite) nightly build results. * **Chat**: Zephyr's Slack workspace is https://zephyrproject.slack.com. Use this `Slack Invite`_ to register. * **Contributing**: see the `Contribution Guide`_ diff --git a/doc/contribute/index.rst b/doc/contribute/index.rst index b41fde1f520..a354434eda7 100644 --- a/doc/contribute/index.rst +++ b/doc/contribute/index.rst @@ -167,7 +167,7 @@ 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 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) - service ``shippable``, which runs automatically on GitHub when you submit + service ``buildkite``, which runs automatically on GitHub when you submit your Pull Request (PR). You can see any failure results in the Shippable details link near the end of the PR conversation list. See `Continuous Integration`_ for more information @@ -224,8 +224,8 @@ every Pull Request (PR) in order to verify several aspects of the PR: * Twister builds for multiple architectures and boards * Documentation build to verify any doc changes -CI is run on the ``shippable`` cloud service and it uses the same tools -described in the `Contribution Tools`_ section. +CI is run both on the ``buildkite`` cloud service and Github Actions and it uses +the same tools described in the `Contribution Tools`_ section. The CI results must be green indicating "All checks have passed" before the Pull Request can be merged. CI is run when the PR is created, and again every time the PR is modified with a commit. @@ -238,8 +238,9 @@ of the run you will see: * "All checks have failed" In case of failure you can click on the "Details" link presented below the -failure message in order to navigate to ``shippable`` and inspect the results. -Once you click on the link you will be taken to the ``shippable`` summary +failure message in order to navigate to ``buildkite`` or ``Github Actions`` +and inspect the results. +Once you click on the link you will be taken to the ``buildkite`` summary 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. non-green) build and then click on the "Tests" tab to see the console output @@ -247,7 +248,7 @@ messages indicating the failure. The `builds@lists.zephyrproject.org mailing list `_ -archives the CI (shippable) nightly build results. +archives the CI (buildkite) nightly build results. Coding Guidelines *****************