Searched refs:CI (Results 1 – 19 of 19) sorted by relevance
| /rk3399_ARM-atf/docs/process/ |
| H A D | contributing.rst | 94 - Ensure that all CI automated tests pass. Failures should be fixed. They might 149 ``Verified+1``. This is usually set by the Continuous Integration (CI) bot 152 the maintainers might (after analysis of the failures) override the CI bot 155 In the event where the CI system lacks proper tests for a patch, the patch 160 be added to the CI system as a follow up task. For example, for a 161 platform-dependent patch where the said platform is not available in the CI 179 Add CI Configurations 182 TF-A uses Jenkins for Continuous Integration and testing activities. Various CI 207 code, it is important to maintain the appropriate TF-A CI scripts. Details of 215 `TF-A CI static checks job`_ might report that these files are not covered. In [all …]
|
| H A D | code-review-guidelines.rst | 40 - ``Verified+1`` vote applied by the automated Continuous Integration (CI) 44 the CI failures and manually override the ``Verified+1`` score. 142 - The patch adheres to the TF-A :ref:`Coding Style`. The CI system should help 146 :ref:`misra-compliance`). The CI system should help catch violations. 154 - All CI automated tests pass. 208 paragraph<copyright-license-guidance>` for more information. The CI system
|
| H A D | faq.rst | 71 ``ci@trustedfirmware.org``) are associated with Continuous Integration (CI) 72 infrastructure. The links published on the comments redirect to the CI web
|
| H A D | commit-style.rst | 66 | ``ci`` | Changes to our CI configuration files and scripts |
|
| /rk3399_ARM-atf/docs/about/ |
| H A D | lts.rst | 97 There are many challenges that may influence the 7 year support from CI 128 #. CI/CD static analysis scans 138 Currently TF.org maintains a CI system to run TF-A automated tests on a 142 the CI system. 158 **CI Scripts** 160 CI Scripts moves forward with TF-A changes, since we need to checkout the 161 corresponding release version of CI scripts for LTS. 163 Though we are unlikely to update CI scripts, but time to time migrating a newer 165 influence updates to CI Scripts. 194 and CI/CD infra is good enough to allow that to happen. [all …]
|
| /rk3399_ARM-atf/docs/plat/arm/fvp/ |
| H A D | index.rst | 11 Please also refer to the TF-A CI scripts under the `model/`_ directory for an
|
| /rk3399_ARM-atf/include/drivers/cadence/ |
| H A D | cdns_sdmmc.h | 113 #define CI 16 macro 114 #define CHECK_CARD BIT(CI)
|
| /rk3399_ARM-atf/docs/threat_model/ |
| H A D | supply_chain_threat_model.rst | 135 machine and are installed within a Docker container in certain CI jobs. At 332 | | CI | 561 | Threat and | | Users of the Node.js tools, including the CI, may be | 577 | | - Execute Node.js tools in the CI only from within a | 584 | | trusted container in CI | 658 | | Gerrit CI. The | level | | 689 | | Services' CI/CD | associated with | static files | 714 | | used by TF CI | stored in | to date | 726 | | | for CI uses | |
|
| /rk3399_ARM-atf/docs/perf/ |
| H A D | psci-performance-n1sdp.rst | 16 configuration in CI.
|
| H A D | psci-performance-juno.rst | 41 configuration in CI.
|
| /rk3399_ARM-atf/docs/design_documents/ |
| H A D | drtm_poc.rst | 54 TF-A CI pipeline already includes coverage for building TF-A with a prebuilt
|
| /rk3399_ARM-atf/docs/ |
| H A D | architecture_features.rst | 548 ``test_smccc_arch_feature_availability`` test in TFTF, otherwise CI will 566 - If the feature is optional, enable it in CI in the "allconfig" fragments.
|
| H A D | change-log.md | 5485 …- remove out-dated information about CI review comments ([74306b2](https://review.trustedfirmware.… 7510 …- enable CI-700 PMU for profiling ([fbfc598](https://review.trustedfirmware.org/plugins/gitiles/TF…
|
| /rk3399_ARM-atf/docs/plat/ |
| H A D | imx8m.rst | 9 imx8mq is dropped in TF-A CI build due to the small OCRAM size, but still actively
|
| H A D | qemu.rst | 184 Linaro's CI documentation, which explains how to trigger a `manual job`_.
|
| /rk3399_ARM-atf/docs/components/ |
| H A D | realm-management-extension.rst | 115 TF-A CI pipeline includes coverage for building TF-A along with TF-RMM and SPM/Hafnium
|
| H A D | el3-spmc.rst | 494 TSP Tests in CI 497 - TSP Tests are exercised in the TF-A CI using prebuilt FF-A Linux Test driver in NWd.
|
| H A D | ras.rst | 126 RAS functionality is regularly tested in TF-A CI using `RAS test group`_ which has multiple
|
| /rk3399_ARM-atf/docs/getting_started/ |
| H A D | prerequisites.rst | 100 CI for feedback on commit message conformance.
|