| /openbmc/openbmc/poky/documentation/test-manual/ |
| H A D | reproducible-builds.rst | 89 To run our automated selftest, as we use in our CI on the Autobuilder, you can
|
| /openbmc/qemu/.gitlab-ci.d/ |
| H A D | buildtest.yml | 222 # but often the CI system is the only way to trigger the failures.
630 # GitLab publishes from any branch that triggers a CI pipeline
|
| /openbmc/linux/Documentation/sound/designs/ |
| H A D | midi-2.0.rst | 15 - MIDI-CI for property and profile configurations
26 MIDI-CI is a high-level protocol that can talk with the MIDI device
31 the encoding/decoding of MIDI protocols on UMP, while MIDI-CI is
|
| /openbmc/docs/designs/mctp/ |
| H A D | mctp-userspace.md | 146 be run in CI on both host and BMC.
|
| /openbmc/docs/ |
| H A D | meta-layer-guidelines.md | 156 either via the autobump script in CI, which can be requested on the mailing
|
| H A D | hw-vendor-repos-policy.md | 150 The OpenBMC project has a fairly extensive CI process, it has many great code
|
| /openbmc/docs/designs/ |
| H A D | psu-monitoring.md | 146 CI testing could be impacted if a system being used for testing is in an
|
| H A D | device-tree-gpio-naming.md | 225 during CI.
|
| H A D | hw-fault-monitor.md | 193 There is no significant impact expected with regards to CI testing, but we do
|
| H A D | voltage-regulator-configuration.md | 250 - CI tests that boot a system will indirectly test this application.
|
| /openbmc/linux/Documentation/rust/ |
| H A D | coding-guidelines.rst | 33 otherwise), for instance for a CI, with::
|
| /openbmc/openbmc/meta-arm/ |
| H A D | .gitlab-ci.yml | 87 # Set the CI variable CI_CLEAN_REPOS=1 to refetch the respositories from scratch
|
| /openbmc/linux/Documentation/translations/it_IT/process/ |
| H A D | stable-kernel-rules.rst | 216 sistema di CI)
|
| /openbmc/qemu/docs/about/ |
| H A D | deprecated.rst | 223 cross-compilation CI tests of the architecture. As we no longer have
224 CI coverage support may bitrot away before the deprecation process
|
| /openbmc/phosphor-logging/extensions/openpower-pels/registry/ |
| H A D | README.md | 41 either during a bitbake build or during CI, or eventually possibly both.
624 registry as part of CI testing.
|
| /openbmc/linux/Documentation/process/ |
| H A D | stable-kernel-rules.rst | 228 used for testing purposes (e.g. to be consumed by CI systems).
|
| /openbmc/linux/drivers/net/ethernet/huawei/hinic/ |
| H A D | hinic_hw_cmdq.c | 722 HINIC_CMDQ_CTXT_BLOCK_INFO_SET(atomic_read(&wq->cons_idx), CI); in cmdq_init_queue_ctxt()
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-dbs/mysql/ |
| H A D | mariadb.inc | 183 # mini-benchmark used for Gitlab-CI to run on every commit to catch
|
| /openbmc/libpldm/ |
| H A D | CHANGELOG.md | 409 CI purposes. `oem-ibm` is still disabled by default in the `libpldm` bitbake
|
| /openbmc/phosphor-logging/ |
| H A D | README.md | 262 - Should cater for continuous integration (CI) build, bitbake image build, and
265 ### Continuous Integration (CI) build
|
| /openbmc/linux/drivers/media/usb/dvb-usb/ |
| H A D | Kconfig | 309 the TechnoTrend CT-3650 CI DVB-C/T USB2.0 receiver. The
|
| /openbmc/u-boot/ |
| H A D | .travis.yml | 4 # build U-Boot on Travis CI - https://travis-ci.org/
|
| /openbmc/openbmc/poky/documentation/migration-guides/ |
| H A D | migration-3.4.rst | 225 configuration). If in your CI system you need to have the original
|
| /openbmc/linux/Documentation/gpu/rfc/ |
| H A D | xe.rst | 61 which needs to be demonstrated by CI results.
|
| /openbmc/docs/architecture/code-update/ |
| H A D | emmc-storage-design.md | 220 be added to the CI pool.
|