Home
last modified time | relevance | path

Searched full:ci (Results 1 – 25 of 319) sorted by relevance

12345678910>>...13

/openbmc/openbmc-build-scripts/jenkins/
H A Duserid-validation18 -p 29418 jenkins-openbmc-ci@gerrit.openbmc.org gerrit \
53 aimvalley/ci-authorized \
54 akamai/ci-authorized \
55 alibaba/ci-authorized \
56 amd/ci-authorized \
57 ami/ci-authorized \
58 ampere/ci-authorized \
59 arm/ci-authorized \
60 aspeed/ci-authorized \
61 asus/ci-authorized \
[all …]
H A DREADME.md8 | 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 | |
15 | ci-openbmc | build-setup.sh | |
16 | ci-repository | run-unit-test-docker.sh | |
/openbmc/qemu/.gitlab-ci.d/cirrus/
H A DREADME.rst1 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/docs/designs/
H A Dci-authorization.md11 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.
61 group: `openbmc/ci-authorized`
63 group: `xyzcorp/ci-authorized`
65 group: `abccorp/ci-authorized`
67 The openbmc/ci-authorized group can contain users that are not associated with
[all …]
/openbmc/qemu/.gitlab-ci.d/
H A Dqemu-project.yml12 - local: '/.gitlab-ci.d/base.yml'
13 - local: '/.gitlab-ci.d/stages.yml'
14 - local: '/.gitlab-ci.d/opensbi.yml'
15 - local: '/.gitlab-ci.d/containers.yml'
16 - local: '/.gitlab-ci.d/crossbuilds.yml'
17 - local: '/.gitlab-ci.d/buildtest.yml'
18 - local: '/.gitlab-ci.d/static_checks.yml'
19 - local: '/.gitlab-ci.d/custom-runners.yml'
20 - local: '/.gitlab-ci.d/cirrus.yml'
21 - local: '/.gitlab-ci.d/windows.yml'
H A Dcirrus.yml1 # Jobs that we delegate to Cirrus CI because they require an operating
5 # The Cirrus CI configuration is generated by replacing target-specific
7 # when the GitLab CI job is defined, others are taken from a shell
11 # special care, because we can't just override it at the GitLab CI job
16 image: registry.gitlab.com/libvirt/libvirt-ci/cirrus-run:latest
21 # as there's often a 5-10 minute delay before Cirrus CI
26 - source .gitlab-ci.d/cirrus/$NAME.vars
28 - cirrus-vars <.gitlab-ci.d/cirrus/build.yml >.gitlab-ci.d/cirrus/$NAME.yml
29 - cat .gitlab-ci.d/cirrus/$NAME.yml
30 - cirrus-run -v --show-build-log always .gitlab-ci.d/cirrus/$NAME.yml
H A Dstatic_checks.yml7 - .gitlab-ci.d/check-patch.py
20 script: .gitlab-ci.d/check-dco.py
55 - source scripts/ci/gitlab-ci-section
81 - source scripts/ci/gitlab-ci-section
93 - .gitlab-ci.d/check-units.py build/compile_commands.json
H A Dcustom-runners.yml1 # The CI jobs defined here require GitLab runners installed and
3 # versions and architectures. This is in contrast to the other CI
32 - local: '/.gitlab-ci.d/custom-runners/ubuntu-22.04-s390x.yml'
33 - local: '/.gitlab-ci.d/custom-runners/ubuntu-22.04-aarch64.yml'
34 - local: '/.gitlab-ci.d/custom-runners/ubuntu-22.04-aarch32.yml'
/openbmc/qemu/docs/devel/testing/
H A Dci-jobs.rst.inc3 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.
15 https://docs.gitlab.com/ee/ci/variables/#add-a-cicd-variable-to-a-project
27 git push -o ci.variable="QEMU_CI_EXAMPLE_VAR=value" myrepo mybranch
37 CI configurations. For example define an alias for triggering CI:
41 git config --local alias.push-ci "push -o ci.variable=QEMU_CI=1"
42 git config --local alias.push-ci-now "push -o ci.variable=QEMU_CI=2"
48 git push-ci
[all …]
H A Dci-runners.rst.inc4 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::
18 .gitlab-ci.d/custom-runners.yml
21 currently deployed in the QEMU GitLab CI and their maintainers, please
29 under ``scripts/ci/setup``, such as this::
44 The ``scripts/ci/setup/$DISTRO/build-environment.yml`` Ansible
54 cd scripts/ci/setup
[all …]
H A Dci.rst3 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>`_.
25 .. include:: ci-jobs.rst.inc
26 .. include:: ci-runners.rst.inc
/openbmc/openbmc/meta-arm/documentation/
H A Dcontinuous-integration-and-kas.md1 # **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 …CI is constantly being expanded to provide increased coverage of the software and hardware support…
13 …ould be wise to run kas locally to verify everything works prior to pushing to the CI build system.
33 $ SSTATE_DIR=/builds/persist/sstate DL_DIR=/builds/persist/downloads kas build ci/qemuarm64.yml:ci/…
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 …
[all …]
/openbmc/qemu/
H A D.gitlab-ci.yml2 # This is the GitLab CI configuration file for the mainstream QEMU
10 # you need to set the location of your custom yml file at "custom CI/CD
11 # configuration path", on your GitLab CI namespace:
12 # https://docs.gitlab.com/ee/ci/pipelines/settings.html#custom-cicd-configuration-path
16 # QEMU CI jobs are based on templates. Some templates provide
19 # See https://qemu-project.gitlab.io/qemu/devel/ci.html#custom-ci-cd-variables
24 - local: '/.gitlab-ci.d/qemu-project.yml'
/openbmc/openbmc/meta-arm/
H A D.gitlab-ci.yml43 BB_LOGCONFIG: $CI_PROJECT_DIR/ci/logging.yml
70 - KASFILES=$(./ci/jobs-to-kas "$CI_JOB_NAME" $EXTRA_KAS_FILES):lockfile.yml
74 - ./ci/check-warnings $KAS_BUILD_DIR/warnings.log
75 - kas shell ci/base.yml:lockfile.yml --command "$CI_PROJECT_DIR/ci/junit.sh $KAS_WORK_DIR/build"
89 # Set the CI variable CI_CLEAN_REPOS=1 to refetch the respositories from scratch
105 flock --verbose --timeout 60 $KAS_REPO_REF_DIR --command ./ci/update-repos || exit_code=$?
115 …kas dump --lock --update ci/qemuarm64.yml:ci/meta-openembedded.yml:ci/clang.yml:ci/meta-virtualiza…
155 …- kas shell --update --force-checkout ci/base.yml:ci/meta-openembedded.yml:lockfile.yml --command \
236 - ./ci/check-machine-coverage
245 - kas shell --update --force-checkout ci/base.yml --command \
[all …]
/openbmc/docs/testing/
H A Dlocal-ci-build.md1 # 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/phosphor-host-ipmid/docs/
H A Dtesting.md26 it all to go, and clone the CI scripts:
29 mkdir openbmc-ci-tests
30 cd openbmc-ci-tests
46 `run-unit-test-docker.sh`, you can't run the CI with untracked changes anyways,
55 git worktree add /path/to/openbmc-ci-tests/phosphor-host-ipmid
58 Now, if you `cd /path/to/openbmc-ci-tests`, you should see a directory
66 up `/path/to/openbmc-ci-tests/openbmc-build-scripts/run-unit-test-docker.sh` and
94 cd openbmc-ci-tests
99 git remote add /path/to/openbmc-ci-tests/phosphor-host-ipmid ci
100 git push ci
[all …]
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/fbida/files/
H A Dsupport-jpeg-turbo.patch129 + int ci, offset_y;
136 + for (ci = 0; ci < dstinfo->num_components; ci++) {
137 + compptr = dstinfo->comp_info + ci;
143 + ((j_common_ptr) srcinfo, dst_coef_arrays[ci], dst_blk_y,
146 + ((j_common_ptr) srcinfo, src_coef_arrays[ci],
169 int ci, k, offset_y;
180 for (ci = 0; ci < dstinfo->num_components; ci++) {
181 compptr = dstinfo->comp_info + ci;
187 ((j_common_ptr) srcinfo, src_coef_arrays[ci], blk_y,
225 + int ci, k, offset_y;
[all …]
/openbmc/qemu/scripts/ci/
H A Dgitlab-ci-section4 # gitlab-ci-section: This is a shell script fragment which defines
7 # section" in a CI job log. See
8 # https://docs.gitlab.com/ee/ci/yaml/script.html#expand-and-collapse-job-log-sections
11 # a CI config; the section_start and section_end functions will
/openbmc/openbmc/meta-arm/ci/
H A Dcorstone1000-common.yml6 - ci/base.yml
7 - ci/meta-openembedded.yml
8 - ci/meta-secure-core.yml
H A Dsgi575.yml6 - ci/base.yml
7 - ci/fvp.yml
11 # Allow the use of the pregen keys as this is CI so safe
H A Djobs-to-kas18 # First, parse the GitLab CI job name (CI_JOB_NAME via $1) and accumulate a list
24 FILES="ci/$(echo $JOBNAME | cut -d ':' -f 1).yml"
35 FILES+=":ci/$i.yml"
40 FILES+=":ci/$i.yml"
/openbmc/openbmc/meta-raspberrypi/.github/workflows/docker-images/dco-check/
H A DDockerfile7 # Run under normal user called 'ci'
8 RUN useradd --create-home --uid 1000 --shell /usr/bin/bash ci
9 USER ci
/openbmc/openbmc/meta-raspberrypi/.github/workflows/docker-images/yocto-builder/
H A DDockerfile36 # Run under normal user called 'ci'
37 RUN useradd --create-home --uid 1000 --shell /usr/bin/bash ci
38 USER ci
39 WORKDIR /home/ci
/openbmc/phosphor-debug-collector/
H A DREADME.md22 Tests can be run in the CI docker container, refer
23 [local-ci-build](https://github.com/openbmc/docs/blob/master/testing/local-ci-build.md)
/openbmc/u-boot/fs/ubifs/
H A Dorphan.c815 struct check_info *ci = priv; in dbg_orphan_check() local
820 if (inum != ci->last_ino) { in dbg_orphan_check()
825 ci->last_ino = inum; in dbg_orphan_check()
826 ci->tot_inos += 1; in dbg_orphan_check()
827 err = ubifs_tnc_read_node(c, zbr, ci->node); in dbg_orphan_check()
832 if (ci->node->nlink == 0) in dbg_orphan_check()
834 if (!dbg_find_check_orphan(&ci->root, inum) && in dbg_orphan_check()
838 ci->missing += 1; in dbg_orphan_check()
841 ci->leaf_cnt += 1; in dbg_orphan_check()
845 static int dbg_read_orphans(struct check_info *ci, struct ubifs_scan_leb *sleb) in dbg_read_orphans() argument
[all …]

12345678910>>...13