| /openbmc/qemu/.gitlab-ci.d/cirrus/ |
| H A D | README.rst | 1 Cirrus CI integration
4 GitLab CI shared runners only provide a docker environment running on Linux.
8 To work around this limitation, we take advantage of `Cirrus CI`_'s free
10 CI jobs from GitLab CI jobs so that Cirrus CI job output is integrated into
11 the main GitLab CI pipeline dashboard.
20 * enable the `Cirrus CI GitHub app`_ for your GitHub account;
22 * sign up for Cirrus CI. It's enough to log into the website using your GitHub
25 * grab an API token from the `Cirrus CI settings`_ page;
28 for Cirrus CI to properly recognize the project. You can check whether
29 Cirrus CI knows about your project by navigating to:
[all …]
|
| /openbmc/openbmc-build-scripts/jenkins/ |
| H A D | README.md | 8 | CI-MISC/ci-build-seed | jenkins/build-seed | |
9 | CI-MISC/ci-meta | jenkins/run-meta-ci | Deprecated |
10 | CI-MISC/ci-openbmc-build-scripts | jenkins/run-build-script-ci | |
11 | CI-MISC/ci-repository-ppc64le | run-unit-test-docker.sh | |
12 | CI-MISC/openbmc-node-cleaner | sstate-cache-management.sh | [1] |
13 | CI-MISC/openbmc-userid-validation | jenkins/userid-validation | |
14 | CI-MISC/run-ci-in-qemu | run-qemu-robot-test.sh | |
|
| /openbmc/qemu/docs/devel/testing/ |
| H A D | ci-jobs.rst.inc | 3 Custom CI/CD variables
6 QEMU CI pipelines can be tuned by setting some CI environment variables.
8 Set variable globally in the user's CI namespace
11 Variables can be set globally in the user's CI namespace setting.
37 CI configurations. For example define an alias for triggering CI:
62 The variables used by QEMU's CI configuration are grouped together
70 repository CI settings, or as git push variables, to influence
92 CI configuratio
[all...] |
| H A D | ci.rst | 3 Continuous Integration (CI)
6 Continuous integration (CI) requires the builds of the entire application and
11 Most of QEMU's CI is run on GitLab's infrastructure although a number
12 of other CI services are used for specialised purposes. The most up to
14 `project wiki testing page <https://wiki.qemu.org/Testing/CI>`_.
|
| H A D | ci-runners.rst.inc | 4 Besides the jobs run under the various CI systems listed before, there
6 These use the same GitLab CI's service/framework already used for all
7 other GitLab based CI jobs, but rely on additional systems, not the
10 The architecture of GitLab's CI service allows different machines to
16 The GitLab CI jobs definition for the custom runners are located under::
21 currently deployed in the QEMU GitLab CI and their maintainers, please
73 * CI/CD, then
92 * CI/CD, then
|
| H A D | index.rst | 4 Details about how to test QEMU and how it is integrated into our CI
|
| /openbmc/openbmc/meta-arm/documentation/ |
| H A D | continuous-integration-and-kas.md | 1 # **CI for Yocto Project and meta-arm**
2 # **CI for Yocto Project**
8 # **CI for meta-arm**
9 meta-arm is using the Gitlab CI infrastructure. This is currently being done internal to Arm, but …
11 This CI is constantly being expanded to provide increased coverage of the software and hardware sup…
13 …ould be wise to run kas locally to verify everything works prior to pushing to the CI build system.
38 ## **Locked Revisions in CI with lockfiles**
39 …CI in meta-arm will generate a kas "lock file" when it starts to ensure that all of the builds che…
41 This lock file is saved as an artefact of the update-repos job by the CI, and only generated if it …
56 Commit this lockfile.yml to the top-level of the meta-arm repository and the CI will use it automat…
[all …]
|
| /openbmc/openbmc-build-scripts/ |
| H A D | README.md | 3 Build script for CI jobs in Jenkins.
8 Separately, [some linters are not version-pinned in the CI
12 The combination may result in inconsistent formatting opinions across CI worker
|
| /openbmc/docs/designs/ |
| H A D | ci-authorization.md | 11 The OpenBMC project maintains a number of Jenkins CI jobs to ensure incoming
19 The project already has contributor authorization for CI. This proposal serves
27 team (or a general-developers sub-team), the automated CI processes are
30 project maintainer to trigger the automated CI processes.
49 An alternative authorization method for CI should:
52 authorized for CI.
89 Finally, any Jenkins CI jobs must be updated to test for membership of the
|
| /openbmc/docs/testing/ |
| H A D | local-ci-build.md | 1 # Local CI Build
3 These instructions pertain to running the upstream OpenBMC CI locally.
15 Each repository is built locally within the CI using the bootstrap.sh and
18 ## Download the CI Image
20 Start by making a place for your CI repositories to live, and clone the CI
33 clones and builds phosphor-hwmon directly. The upstream CI will try building
56 ## Run CI on local changed Repo
59 possible to run local CI as well by setting `NO_FORMAT_CODE=1` before running
72 ## Run CI for testing purposes only
|
| /openbmc/bmcweb/docs/ |
| H A D | CLIENTS.md | 22 Status: 100% passing. Integrated with CI to ensure no regressions.
28 Status: 100% of assertions passing. No CI integration.
33 Status: Passing for some machines with CI integration.
62 Status: Compatible. No CI integration.
|
| /openbmc/qemu/scripts/ci/ |
| H A D | gitlab-ci-section | 7 # section" in a CI job log. See
11 # a CI config; the section_start and section_end functions will
|
| /openbmc/webui-vue/docs/guide/coding-standards/ |
| H A D | readme.md | 34 CI tool runs after a push to Gerrit. There is a shell script named
36 script in your CI.
|
| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | testing.md | 7 run during Continuous Integration (CI) testing.
36 CI test environment. Thus, in automated test cases they need to be mocked.
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | testing.md | 7 run during Continuous Integration (CI) testing.
36 CI test environment. Thus, in automated test cases they need to be mocked.
|
| /openbmc/qemu/tests/docker/dockerfiles/ |
| H A D | debian-hexagon-cross.docker | 5 # needs to be able to build QEMU itself in CI we include its
29 # Install QEMU build deps for use in CI
|
| /openbmc/openbmc/poky/meta/recipes-devtools/python/ |
| H A D | python3-sphinx-rtd-theme_3.0.2.bb | 23 export CI = "True"
|
| /openbmc/openbmc/meta-openpower/recipes-phosphor/logging/ |
| H A D | openpower-libhei_git.bb | 21 # Don't build CI tests
|
| /openbmc/qemu/target/ppc/translate/ |
| H A D | misc-impl.c.inc | 103 * - loads from CI memory.
104 * - stores to CI memory.
119 * The end result is that CI memory ordering requires TCG_MO_ALL
|
| /openbmc/openbmc/meta-phosphor/scripts/ |
| H A D | generate-machine-list | 17 covered by [Jenkins](https://jenkins.openbmc.org/job/ci-openbmc/) CI testing.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/rsyslog/rsyslog/ |
| H A D | disable-omfile-outchannel.patch | 18 +# This test fails for x86_64-musl, under GitHub's CI/CD. Disable for now.
|
| /openbmc/libpldm/docs/checklists/ |
| H A D | releases.md | 10 - This must be done from a shell session inside the OpenBMC CI Docker
|
| /openbmc/openbmc-test-automation/ |
| H A D | README.md | 247 Run the QEMU CI test suite:
261 - How to run CI and CT bucket test:
263 Default CI test bucket list:
269 Default CI smoke test bucket list:
310 Run GUI default CI test bucket:
346 - HW CI tox command:
|
| /openbmc/openbmc/meta-openembedded/meta-multimedia/recipes-multimedia/mycroft/files/ |
| H A D | 0003-dev_setup.sh-Remove-the-TERM-dependency.patch | 33 if [[ ! -f .dev_opts.json && -z $CI ]] ; then
|
| /openbmc/phosphor-debug-collector/ |
| H A D | README.md | 22 Tests can be run in the CI docker container, refer
|