Skip to content
  1. Jun 27, 2023
  2. May 19, 2023
    • Lingkai Dong's avatar
      docs: Consolidate info for testing in a dedicated page · 0401a55f
      Lingkai Dong authored and Hugues Kamba Mpiana's avatar Hugues Kamba Mpiana committed
      
      
      The page `docs/README.md` was not added to the website, because we
      used `docs/index.md` instead which is an alias of the root-level
      `README.md`.
      
      Since `docs/README.md` still contained some useful information for
      integration tests, this commit
      
      * renames `docs/README.md` to `docs/testing.md`, and makes it availabe
        in the website
      * removes from `docs/testing.md` any information that's not related to
        testing, because non-testing information is already better covered by
        the root-level `README.md`
      * moves information about unit tests from the root-level `README` into
        `docs/testing.md`, to consolidate all testing info in one page
      
      Signed-off-by: Lingkai Dong's avatarLingkai Dong <lingkai.dong@arm.com>
      0401a55f
    • Lingkai Dong's avatar
      docs: Consolidate repository README.md and docs/index.md · f36c6731
      Lingkai Dong authored and Hugues Kamba Mpiana's avatar Hugues Kamba Mpiana committed
      
      
      The page `docs/index.md` was copy of the Open IoT SDK repository's top-
      level `README.md` with minor improvements. To avoid duplication, update
      the top-level `README.md` to bring in those improvements and convert
      `docs/index.md` into an alias of `README.md`.
      
      Signed-off-by: Lingkai Dong's avatarLingkai Dong <lingkai.dong@arm.com>
      f36c6731
  3. Apr 13, 2023
  4. Apr 11, 2023
  5. Mar 31, 2023
  6. Mar 27, 2023
  7. Mar 24, 2023
  8. Mar 13, 2023
  9. Aug 04, 2022
    • Lingkai Dong's avatar
      templates: Introduce template framework for examples and tests · f02b4f29
      Lingkai Dong authored
      
      
      We want each example and test to work on all supported reference
      platforms (currently Corstone-300) as well as RTOSes that are compatible
      with any given example. Also, we would like each example to work like a
      typical user project which targets one particular platforms and one
      particular RTOS (or none, if the app runs on bare metal). This creates a
      large matrix of examples x platforms x RTOSes (or baremetal).
      
      To avoid having to maintain all possible combinations, we introduce a
      mechanism for generating examples (similarly for tests). See updated
      documentation for how to use this mechanism.
      
      When the main branch is updated (i.e. an MR is merged), publish newly
      generated examples to the repository that hosts full, ready-to-use
      examples for users' convenience.
      
      In CI runs, all flavors (RTOSes) of the same example are grouped into
      the same pipeline to minimize the number of required runners, while
      different platforms and toolchains are put into their own pipelines
      as before because each of our Docker images contains only one toolchain
      or FVP.
      
      Signed-off-by: Lingkai Dong's avatarLingkai Dong <lingkai.dong@arm.com>
      f02b4f29
  10. May 13, 2022
  11. Mar 22, 2022
  12. Mar 21, 2022
  13. Feb 07, 2022
  14. Jan 20, 2022
  15. Jan 19, 2022
  16. Oct 20, 2021
Loading