docs/process/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
232    for placing all the test scripts which will be executed by the CI Jobs.
273 We have CI jobs which run a set of test configurations on every TF-A patch
312 For a more elaborate explanation of the TF-A CI scripts internals, including how
314 CI scripts overview`_ section of the OpenCI documentation.
347 .. _TF-A CI scripts overview: https://tf-ci-users-guide.readthedocs.io/en/latest/#tf-a-ci-scripts-o…
349 .. _TF-A CI static checks job: https://ci.trustedfirmware.org/job/tf-a-static-checks/