/openbmc/openpower-hw-diags/ |
H A D | meson.build | 145 # When running GCOV reports, the Jenkins CI script explicitly ignores any
|
/openbmc/docs/development/ |
H A D | dev-environment.md | 26 this is the system tested for each CI job, which means it's the most stable. 52 for a reference on the script CI uses to build an appropriate docker
|
/openbmc/openbmc/meta-openembedded/meta-oe/classes/ |
H A D | signing.bbclass | 18 # widespread, testing code signing in CI is not simple. To solve this at the 21 # keys in CI), they are imported into SoftHSM (a HSM emulation library).
|
/openbmc/libpldm/docs/checklists/ |
H A D | changes.md | 166 - [ ] If I've updated the ABI dump, then I've used the OpenBMC CI container to 173 - [ ] Enter the OpenBMC CI Docker container
|
/openbmc/webui-vue/docs/guide/coding-standards/ |
H A D | accessibility.md | 40 built into the CI process, integrated with code editors, and run using browser
|
/openbmc/docs/architecture/ |
H A D | optionality.md | 67 CI will generally enable all developer opt-in features to ensure the most
|
/openbmc/qemu/.gitlab-ci.d/ |
H A D | crossbuilds.yml | 115 # allow_failure so as not to block CI.
|
H A D | windows.yml | 132 # so let's exclude the qtests from CI for now.
|
/openbmc/openbmc/poky/documentation/test-manual/ |
H A D | intro.rst | 37 As a result, it can be used by any Continuous Improvement (CI) system 40 …independent of any CI system, which means the code can work `Buildbot <https://docs.buildbot.net/c… 66 on a per-project basis. The layer is CI system-agnostic and contains a 75 (CI) system such as :wikipedia:`Jenkins <Jenkins_(software)>`
|
/openbmc/linux/Documentation/admin-guide/media/ |
H A D | bttv.rst | 654 - 50689 TV SAT DVB-S CARD CI PCI (SAA7146AH, SU1278?) = "KNC1 TV Station DVB-S" 709 - DTV3000 PV-DTV3000P+ DVB-S CI = Twinhan VP-1030 1238 - Galaxis DVB Card S CI 1239 - Galaxis DVB Card C CI 1242 - Galaxis plug.in S [neuer Name: Galaxis DVB Card S CI 1252 - WinTV NOVA-CI "SDVBACI" 1315 -546 WinTV Nova-S CI 1474 - Standard PCI (DVB-S) w/ CI 1563 - DST-CI Card (DVB Satellite) VP-1030
|
/openbmc/docs/designs/ |
H A D | firmware-update-via-usb.md | 65 - It is recommended to run a local CI run and analyze & avoid potential
|
H A D | design-template.md | 117 How will this be tested? How will this feature impact CI testing?
|
/openbmc/linux/arch/arm/boot/dts/nxp/imx/ |
H A D | imx6dl-eckelmann-ci4x10.dts | 14 model = "Eckelmann CI 4X10 Board";
|
/openbmc/linux/sound/soc/sof/ |
H A D | Kconfig | 124 It is intended for SOF CI/releases and not for users or distros. 126 If you are not involved in SOF releases and CI development,
|
/openbmc/openbmc/meta-raspberrypi/docs/ |
H A D | contributing.md | 90 them in a GitHub pull request that will take the patches through the CI
|
/openbmc/docs/designs/oem/google/ |
H A D | root_of_trust.md | 118 Testing will be done in Google internally. This feature should not impact CI
|
/openbmc/qemu/docs/system/devices/ |
H A D | canokey.rst | 46 Also since this is a virtual card, it can be easily used in CI for testing
|
/openbmc/linux/Documentation/maintainer/ |
H A D | maintainer-entry-profile.rst | 28 - Any bots or CI infrastructure that watches the list, or automated
|
/openbmc/phosphor-psu-code-mgmt/ |
H A D | README.md | 17 - Run it in OpenBMC CI, refer to [local-ci-build.md][1]
|
/openbmc/qemu/qga/ |
H A D | meson.build | 183 # the leak detector in build-oss-fuzz Gitlab CI test. we should re-enable
|
/openbmc/linux/Documentation/bpf/ |
H A D | bpf_devel_QA.rst | 47 Q: How do I run BPF CI on my changes before sending them out for review? 49 A: BPF CI is GitHub based and hosted at https://github.com/kernel-patches/bpf. 53 The following steps lay out how to start a CI run for your patches: 64 Shortly after the pull request has been created, the CI workflow will run. Note 71 This behavior can result in a CI run being aborted and restarted with the new
|
/openbmc/linux/arch/arc/boot/dts/ |
H A D | abilis_tb100.dtsi | 89 pctl_ciplus: pctl-ciplus { /* CI+ interface */
|
H A D | abilis_tb101.dtsi | 89 pctl_ciplus: pctl-ciplus { /* CI+ interface */
|
/openbmc/docs/ |
H A D | CONTRIBUTING.md | 85 If a repository has a setup.cfg file present in its root directory, then CI will 195 turn trigger a new CI build. Ideally, changes from the entire patchset could be 202 in the same stack before you push, in order to minimize CI and notification
|
/openbmc/linux/Documentation/userspace-api/media/dvb/ |
H A D | intro.rst | 82 Conditional Access (CA) hardware like CI adapters and smartcard slots
|