Home
last modified time | relevance | path

Searched +full:ci +full:- +full:build (Results 1 – 25 of 1190) sorted by relevance

12345678910>>...48

/external/wayland/
D.gitlab-ci.yml1 # This file uses the freedesktop ci-templates to build Wayland and run our
2 # tests in CI.
4 # ci-templates uses a multi-stage build process. First, the base container
6 # all our build dependencies. This container is aggressively cached; if a
9 # reused for the build. This gives us predictability of build and far
12 # the current date as well as a unique build identifier.
15 # previously used), the build stage executes within this container.
21 # Apart from the 'variables', 'include', and 'stages' top-level anchors,
23 # be executed as part of CI, unless the rules specify that it should not be
28 # by the ci-templates.
[all …]
/external/sdv/vsomeip/third_party/boost/process/
DREADME.md1 # [Boost Process (Boost.Process)](https://github.com/klemens-morgenstern/boost-process)
8 ----------------|-------|-----|---------| ------------- |--------|
9 …Build Status](https://travis-ci.org/klemens-morgenstern/boost-process.svg?branch=develop&env=BADGE…
10 …Build Status](https://travis-ci.org/klemens-morgenstern/boost-process.svg?branch=master&env=BADGE=…
13 [Open Issues](https://github.com/klemens-morgenstern/boost-process/issues)
15 [Latest developer documentation](http://klemens-morgenstern.github.io/process/)
/external/webrtc/infra/config/
Dcr-buildbucket.cfg1 # Auto-generated by lucicfg.
5 # https://luci-config.appspot.com/schemas/projects:buildbucket.cfg
8 name: "ci"
14 group: "project-webrtc-ci-schedulers"
19 swarming_host: "chromium-swarm.appspot.com"
20 swarming_tags: "vpython:native-python-wrapper"
21 dimensions: "cpu:x86-64"
23 dimensions: "pool:luci.webrtc.ci"
25 cipd_package: "infra/recipe_bundles/chromium.googlesource.com/chromium/tools/build"
31 ' "$build/goma": {'
[all …]
/external/mesa3d/.gitlab-ci/container/
Dlava_build.sh6 # .gitlab-ci/image-tags.yml tags:
9 set -e
10 set -o xtrace
17 S3_PATH="${S3_HOST}/mesa-lava/$1/${DISTRIBUTION_TAG}/${DEBIAN_ARCH}"
18 if curl -L --retry 4 -f --retry-delay 60 -s -X HEAD \
20 echo "Remote files are up-to-date, skip rebuilding them."
28 . .gitlab-ci/container/container_pre_build.sh
30 # Install rust, which we'll be using for deqp-runner. It will be cleaned up at the end.
31 . .gitlab-ci/container/build-rust.sh
34 GCC_ARCH="aarch64-linux-gnu"
[all …]
/external/mesa3d/
D.gitlab-ci.yml1 # Types of CI pipelines:
3 # |----------------------|-----------|-------------------------------------------------------------|
5 # | pre-merge pipeline | mesa/mesa | same as above, except its status doesn't affect the MR |
6 # | post-merge pipeline | mesa/mesa | pipeline immediately after merging |
9 # | direct-push pipeline | mesa/mesa | when commits are pushed directly to mesa/mesa, bypassing Mar…
19 # Pre-merge pipelines contain the exact same jobs as merge pipelines.
20 # Post-merge pipelines contain *only* the `pages` job that deploys the new
23 # Scheduled pipelines only contain the container+build jobs, and some extra
24 # test jobs (typically "full" variants of pre-merge jobs that only run 1/X
26 # Direct-push pipelines contain the same jobs as merge pipelines.
[all …]
/external/mesa3d/.gitlab-ci/container/debian/
Dx86_64_test-base.sh5 # .gitlab-ci/image-tags.yml tags:
8 set -e
9 set -o xtrace
13 apt-get install -y ca-certificates gnupg2 software-properties-common
15 sed -i -e 's/http:\/\/deb/https:\/\/deb/g' /etc/apt/sources.list.d/*
17 …b.freedesktop.org/gfx-ci/ci-deb-repo/-/raw/${PKG_REPO_REV}/ ${FDO_DISTRIBUTION_VERSION%-*} main" |…
30 "clang-${LLVM_VERSION}"
32 glslang-tools
34 libasound2-dev
35 libcap-dev
[all …]
Dx86_64_test-vk.sh6 set -e
7 set -o xtrace
11 apt-get install -y libelogind0 # this interfere with systemd deps, install separately
18 glslang-tools
19 libexpat1-dev
21 libdrm-dev
22 libgbm-dev
23 libgles2-mesa-dev
24 liblz4-dev
25 libpciaccess-dev
[all …]
/external/mesa3d/docs/ci/
Dindex.rst4 GitLab CI
5 ---------
8 We use it to test merge requests (MRs) before merging them (pre-merge testing),
9 as well as post-merge testing, for everything that hits ``main``
11 and even then the MR CI runs in the forked repository, which might have been
14 The CI runs a number of tests, from trivial build-testing to complex GPU rendering:
16 - Build testing for a number of configurations and platforms
17 - Sanity checks (``meson test``)
18 - Most drivers are also tested using several test suites, such as the
19 `Vulkan/GL/GLES conformance test suite <https://github.com/KhronosGroup/VK-GL-CTS>`__,
[all …]
/external/libyuv/infra/config/
Dcr-buildbucket.cfg1 # Auto-generated by lucicfg.
5 # https://luci-config.appspot.com/schemas/projects:buildbucket.cfg
8 name: "ci"
11 group: "project-libyuv-admins"
19 swarming_host: "chromium-swarm.appspot.com"
20 swarming_tags: "vpython:native-python-wrapper"
22 dimensions: "cpu:x86-64"
23 dimensions: "os:Ubuntu-18.04"
24 dimensions: "pool:luci.flex.ci"
26 cipd_package: "infra/recipe_bundles/chromium.googlesource.com/chromium/tools/build"
[all …]
/external/aws-crt-java/.github/workflows/
Dci.yml1 name: CI
5 branches-ignore:
6 - 'main'
7 - 'docs'
13 PACKAGE_NAME: aws-crt-java
14 LINUX_BASE_IMAGE: ubuntu-18-x64
15 RUN: ${{ github.run_id }}-${{ github.run_number }}
19 AWS_REGION: us-east-1
20 AWS_DEVICE_FARM_REGION: us-west-2 # Device Farm only available in us-west-2 region
23 linux-compat:
[all …]
/external/jazzer-api/
D.bazelrc2 startup --host_jvm_args=-DBAZEL_TRACK_SOURCE_DIRECTORIES=1
3 build --incompatible_strict_action_env
4 build --sandbox_tmpfs_path=/tmp
5 build --enable_platform_specific_config
6 build -c opt
8 build --nozip_undeclared_test_outputs
11 # GCC is supported on a best-effort basis.
12 common --repo_env=CC=clang
13 build --incompatible_enable_cc_toolchain_resolution
14 # Required by abseil-cpp.
[all …]
/external/bazelbuild-rules_go/
D.bazelrc1 common --enable_platform_specific_config
5 build:windows --cpu=x64_windows
6 build:windows --compiler=mingw-gcc
9 build:windows --extra_toolchains=@local_config_cc//:cc-toolchain-x64_windows_mingw
10 build:windows --host_platform=@io_bazel_rules_go//go/toolchain:windows_amd64_cgo
11 build:windows --platforms=@io_bazel_rules_go//go/toolchain:windows_amd64_cgo
12 build:windows --incompatible_enable_cc_toolchain_resolution
14 build:check --all_incompatible_changes
16 common:ci --color=no
17 build:ci --verbose_failures
[all …]
/external/libusb/.github/workflows/
Dlinux.yml10 # This workflow contains a single job called "build"
11 build:
12 runs-on: ubuntu-latest
16 # Checks-out your repository under $GITHUB_WORKSPACE, so your job
18 - uses: actions/checkout@v3
20 - name: setup prerequisites
23 sudo apt install autoconf automake libtool libudev-dev m4
25 - name: bootstrap
28 - name: netlink
29 # Disable tests for netlink as it doesn't seem to work in the CI environment.
[all …]
/external/perfetto/infra/luci/recipes/perfetto.expected/
Dunofficial.json9 "-u",
11 "--json-output",
13 "ensure-directory",
14 "--mode",
21 "name": "perfetto:ci"
25 "name": "invocations/build:8945511751514863184",
45 "name": "perfetto:ci"
49 "name": "invocations/build:8945511751514863184",
64 "--tags",
72 "name": "perfetto:ci"
[all …]
Dci_mac.json9 "-u",
11 "--json-output",
13 "ensure-directory",
14 "--mode",
21 "name": "perfetto:ci"
25 "name": "invocations/build:8945511751514863184",
45 "name": "perfetto:ci"
49 "name": "invocations/build:8945511751514863184",
64 "--tags",
72 "name": "perfetto:ci"
[all …]
Dci_win.json9 "-u",
11 "--json-output",
13 "ensure-directory",
14 "--mode",
21 "name": "perfetto:ci"
25 "name": "invocations/build:8945511751514863184",
45 "name": "perfetto:ci"
49 "name": "invocations/build:8945511751514863184",
64 "--tags",
72 "name": "perfetto:ci"
[all …]
/external/libdrm/
D.gitlab-ci.yml1 # This is the tag of the docker image used for the build jobs. If the
8 # versions of gcc/clang or other packages, which might break the build
15 …_sha 567700e483aabed992d0a4fea84994a0472deff6 # see https://docs.gitlab.com/ee/ci/yaml/#includefile
18 - project: 'freedesktop/ci-templates'
21 - '/templates/debian.yml'
22 - '/templates/freebsd.yml'
23 - '/templates/ci-fairy.yml'
30 - "Base container"
31 - "Build"
33 .ci-rules:
[all …]
/external/perfetto/docs/design-docs/
Dcontinuous-integration.md1 # Perfetto CI design document
3 This CI is used on-top of (not in replacement of) AOSP's TreeHugger.
12 ![Architecture diagram](/docs/images/continuous-integration.png)
22 whole CI.
26 The Controller orchestrates the CI. It's the most trusted piece of the system.
32 It uses a non-privileged gmail account and has no meaningful voting power.
36 - It periodically (every 5s) polls Gerrit for CLs updated in the last 24h.
37 - It checks the list of CLs against the list of already known CLs in the DB.
38 - For each new CL it enqueues `N` new jobs in the database, one for each
39 configuration defined in [config.py](/infra/ci/config.py) (e.g. `linux-debug`,
[all …]
/external/mesa3d/.gitlab-ci/build/
Dgitlab-ci.yml2 .build-common:
3 extends: .container+build-rules
6 # Build jobs don't take more than 1-3 minutes. 5-8 min max on a fresh runner
18 - _build/meson-logs/*.txt
19 - _build/meson-logs/strace
20 - shader-db
21 - artifacts
24 .build-linux:
25 extends: .build-common
32 - !reference [default, before_script]
[all …]
/external/angle/infra/
DREADME.md4 the tree. We scale our pre-commit and post-commit testing to many machines
6 existing work in Chromium. We also run compile-only
11 ## Pre-Commit Testing
13 See the pre-commit try waterfall here:
15 [`https://ci.chromium.org/p/chromium/g/tryserver.chromium.angle/builders`](https://ci.chromium.org/…
17 We currently run pre-commit tests on:
19 * Windows 32-bit AMD and Windows 64-bit Intel and NVIDIA GPUs
20 * Linux 64-bit NVIDIA and Intel GPUs
25 Looking at an example build shows how tests are split up between machines. See for example:
27 [`https://ci.chromium.org/ui/p/angle/builders/ci/mac-rel/8123/overview`](https://ci.chromium.org/ui…
[all …]
/external/mockito-kotlin/.github/workflows/
Dci.yml2 # CI build that assembles artifacts and runs tests.
5 # - skipping CI: add [skip ci] to the commit message
6 # - skipping release: add [skip release] to the commit message
8 name: CI
13 - main
14 tags-ignore:
15 …- v* # release tags are automatically generated after a successful CI build, no need to run CI aga…
18 - main
23 # SINGLE-JOB
26 runs-on: ubuntu-latest
[all …]
/external/drm_hwcomposer/
DMakefile3 DOCKER_BIN := $(shell command -v docker 2> /dev/null)
4 NPROCS:=$(shell grep -c ^processor /proc/cpuinfo)
6 DOCKERFILE := .ci/Dockerfile
11 GIT_IS_SYMLINK:=$(shell test -L .git && echo true)
16 $(warning $$ sudo usermod -aG docker $$USER)
21 .PHONY : help prepare shell ci_fast ci ci_cleanup build_deploy bd local_presubmit local_cleanup
25 …@awk 'BEGIN {FS = ":.*?## "} /^[a-zA-Z_-]+:.*?## / {printf " \033[36m%-15s\033[0m %s\n", $$1, $$2…
30 mkdir -p $(dir $@)
31 $(DOCKER_BIN) build -t local/build-env -f $(DOCKERFILE) .;
34 …$(DOCKER_BIN) run -itd --name $(IMAGE_NAME) --network="host" -v $(shell pwd):/home/user/drm_hwcomp…
[all …]
/external/libbpf/.github/actions/vmtest/
Daction.yml2 description: 'Build + run vmtest'
20 - name: Setup environment
21 uses: libbpf/ci/setup-build-env@main
25 - name: Get checkpoint commit
28 cat CHECKPOINT-COMMIT
29 echo "CHECKPOINT=$(cat CHECKPOINT-COMMIT)" >> $GITHUB_ENV
30 - name: Get kernel source at checkpoint
31 uses: libbpf/ci/get-linux-source@main
33 repo: 'https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git'
36 - name: Patch kernel source
[all …]
/external/trusty/arm-trusted-firmware/docs/process/
Dcontributing.rst7 - Make sure you have a Github account and you are logged on both
10 - If you plan to contribute a major piece of work, it is usually a good idea to
20 - Clone `Trusted Firmware-A`_ on your own machine as described in
23 - Create a local topic branch based on the `Trusted Firmware-A`_ ``master``
29 - Ensure commits adhere to the the project's :ref:`Commit Style`.
31 - Make commits of logical units. See these general `Git guidelines`_ for
34 - Keep the commits on topic. If you need to fix another bug or make another
37 - Split the patch in manageable units. Small patches are usually easier to
40 - Avoid long commit series. If you do have a long series, consider whether
43 - Follow the :ref:`Coding Style` and :ref:`Coding Guidelines`.
[all …]
/external/sdv/vsomeip/third_party/boost/smart_ptr/
DREADME.md4 ---------|--------|---------
5 …Build Status](https://travis-ci.org/boostorg/smart_ptr.svg?branch=develop)](https://travis-ci.org/…
6 …Build Status](https://travis-ci.org/boostorg/smart_ptr.svg?branch=master)](https://travis-ci.org/b…

12345678910>>...48