Searched +full:build +full:- +full:local +full:- +full:artifacts (Results 1 – 25 of 143) sorted by relevance
123456
| /third_party/rust/crates/bindgen/.github/workflows/ |
| D | release.yml | 1 # Copyright 2022-2023, axodotdev 2 # SPDX-License-Identifier: MIT or Apache-2.0 7 # * builds artifacts with cargo-dist (archives, installers, hashes) 8 # * uploads those artifacts to temporary workflow zip 9 # * on success, uploads the artifacts to a Github Release 20 # like "1.0.0", "v0.1.0-prerelease.1", "my-app/0.1.0", "releases/v1.0.0", etc. 23 # must be a Cargo-style SemVer Version (must have at least major.minor.patch). 26 # package (erroring out if it doesn't have the given version or isn't cargo-dist-able). 29 # (cargo-dist-able) packages in the workspace with that version (this mode is 30 # intended for workspaces with only one dist-able package, or with all dist-able [all …]
|
| /third_party/grpc/src/csharp/ |
| D | build_nuget.sh | 8 # http://www.apache.org/licenses/LICENSE-2.0 16 set -ex 20 mkdir -p ../../artifacts 22 # Collect protoc artifacts built by the previous build step 23 mkdir -p protoc_plugins 24 cp -r "${EXTERNAL_GIT_ROOT}"/input_artifacts/protoc_* protoc_plugins || true 31 # it difficult to support a local build of the nuget. 32 # To allow simple local builds (restricted to a single platform), 33 # we provide a way of building "partial" nugets that only include artifacts 35 # contain placeholders (empty files) for artifacts that normally need [all …]
|
| /third_party/mesa3d/ |
| D | .gitlab-ci.yml | 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. 31 - if: $CI_COMMIT_BRANCH && $CI_OPEN_MERGE_REQUESTS && $CI_PIPELINE_SOURCE == "push" [all …]
|
| /third_party/grpc/tools/internal_ci/linux/ |
| D | grpc_publish_packages.sh | 8 # http://www.apache.org/licenses/LICENSE-2.0 16 set -ex 18 shopt -s nullglob 22 GRPC_VERSION=$(grep -e "^ *version: " build_handwritten.yaml | head -n 1 | sed 's/.*: //') 24 INPUT_ARTIFACTS=$KOKORO_GFILE_DIR/github/grpc/artifacts 27 BUILD_ID=${KOKORO_BUILD_ID:-$(uuidgen)} 29 BUILD_GIT_COMMIT=${KOKORO_GIT_COMMIT:-unknown} 30 BUILD_TIMESTAMP=$(date -Iseconds) 31 BUILD_RELPATH=$(date "+%Y/%m")/$BUILD_GIT_COMMIT-$BUILD_ID/ 38 LOCAL_STAGING_TEMPDIR=$(mktemp -d) [all …]
|
| /third_party/skia/third_party/externals/tint/kokoro/linux/ |
| D | build.sh | 9 # http://www.apache.org/licenses/LICENSE-2.0 17 set -e # Fail on any error. 23 # We do this so that the docker script can be tested in a local development 24 # checkout, without having the build litter the local checkout with artifacts. 27 if [ -d "/tmpfs" ]; then 34 # --privileged is required for some sanitizer builds, as they seem to require PTRACE privileges 35 docker run --rm -i \ 36 --privileged \ 37 --volume "${ROOT_DIR}:${ROOT_DIR}" \ 38 --volume "${TMP_DIR}:/src" \ [all …]
|
| /third_party/rust/rust/src/ci/ |
| D | run.sh | 3 set -e 5 if [ -n "$CI_JOB_NAME" ]; then 11 useradd --shell /bin/bash -u $LOCAL_USER_ID -o -c "" -m user 22 echo -e '[safe]\n\tdirectory = *' > /home/user/gitconfig 24 exec su --preserve-environment -c "env PATH=$PATH \"$0\"" user 29 if [ -f /proc/sys/kernel/core_pattern ]; then 30 ulimit -c unlimited 33 # There was a bad interaction between "old" 32-bit binaries on current 64-bit 35 # address and then block it for being below `vm.mmap_min_addr` -> `EACCES`. 36 # This is probably a kernel bug, but setting `ulimit -Hs` works around it. [all …]
|
| /third_party/mesa3d/src/microsoft/ci/ |
| D | gitlab-ci.yml | 2 - local: 'src/microsoft/ci/gitlab-ci-inc.yml' 4 test-spirv2dxil-windows: 6 - .use-windows_test_msvc 7 - .spirv2dxil-test-rules 8 stage: layered-backends 10 - windows-msvc 12 - windows-msvc 13 - windows_test_msvc 14 - !reference [.required-for-hardware-jobs, needs] 16 GIT_STRATEGY: none # testing doesn't build anything from source [all …]
|
| /third_party/skia/third_party/externals/angle2/src/tests/restricted_traces/ |
| D | restricted_trace_gold_tests.py | 4 # Use of this source code is governed by a BSD-style license that can be 10 # Requires vpython to run standalone. Run with --help for usage instructions. 38 # Handle the Chromium-relative directory as well. As long as one directory 83 group.add_argument('--git-revision', help='Revision being tested.', default=None) 85 '--gerrit-issue', help='For Skia Gold integration. Gerrit issue ID.', default='') 87 '--gerrit-patchset', 91 '--buildbucket-id', help='For Skia Gold integration. Buildbucket build ID.', default='') 93 '--bypass-skia-gold-functionality', 101 '--local-pixel-tests', 104 help='Specifies to run the test harness in local run mode or not. When ' [all …]
|
| /third_party/grpc/tools/interop_matrix/ |
| D | README.md | 8 ## Step-by-step instructions for adding a AR docker image for a new release for compatibility test 11 When a gRPC developer creates a new gRPC release, s/he is also responsible to add the just-released… 13 - Add (or update) an entry in `./client_matrix.py` file to reference the github tag for the release. 14 - Build new client docker image(s). For example, for C and wrapper languages release `v1.9.9`, do 15 …- `tools/interop_matrix/create_matrix_images.py --git_checkout --release=v1.9.9 --upload_images --… 16 - Verify that the new docker image was built successfully and uploaded to AR. For example, 17 …- `gcloud artifacts docker images list us-docker.pkg.dev/grpc-testing/testing-images-public` lists… 18 …- `gcloud artifacts docker images list us-docker.pkg.dev/grpc-testing/testing-images-public/grpc_i… 19 …- images can also be viewed in https://pantheon.corp.google.com/artifacts/docker/grpc-testing/us/t… 20 - Verify the just-created docker client image would pass backward compatibility test (it should). … [all …]
|
| /third_party/grpc/tools/bazelify_tests/ |
| D | build_defs.bzl | 7 # http://www.apache.org/licenses/LICENSE-2.0 107 """Execute an run_tests.py-harness style test under bazel. 145 # Enable ccache by default. This is important for speeding up the C++ cmake build, 147 # Even though only the local disk cache is enabled (local to the docker container, 149 # the C++ build significantly. 156 …"""Execute bazel distribtest under bazel (an entire bazel build/test will run in a container as a … 249 """Execute a build artifact task and a corresponding 'build test'. 251 The artifact is built by a genrule that always succeeds (Even if the underlying build fails) 252 and an sh_test (with "_build_test" suffix) that presents the result of the artifact build 253 in the result UI (by displaying the the build status, the log, and artifacts produced). [all …]
|
| D | README.md | 1 # Non-Bazel native tests 3 This directory contains logic that wraps builds and tests from the non-bazel realm to make them run… 5 Examples: cmake builds, run_tests.py tests, artifacts, distribtests etc. 16 …ch a way so that it behaves "reasonably" from bazel's perspective (always re-runs if commit SHAs h… 20 (e.g. run the run_tests.py test harness, run cmake build etc). 25 …rt a docker container for each action when [docker sandbox](https://bazel.build/remote/sandbox) is… 29 (e.g. by RBE toolchain or by setting `--experimental_docker_image` flag) or explicitly for each act… 35 # "--genrule_strategy=remote,local" allows fallback to local execution if action doesn't support ru… 37 tools/bazel --bazelrc=tools/remote_build/linux.bazelrc test --genrule_strategy=remote,local --works… 43 tools/bazel --bazelrc=tools/remote_build/linux_docker_sandbox.bazelrc test --workspace_status_comma…
|
| /third_party/skia/m133/infra/debugger-app/ |
| D | BUILD.bazel | 3 # Modify the debugger-app container by injecting the artifacts from this 7 base_image = "@debugger-app-base//image", 9 "/usr/local/share/debugger-app/": [ 11 # This brings in all the build files. 25 entrypoint = "/usr/local/bin/debugger-app", 26 repository = "skia-public/debugger-app-final",
|
| /third_party/icu/docs/processes/release/tasks/ |
| D | release-build.md | 1 --- 3 title: Release Build 7 --- 9 <!-- 12 --> 14 # Release Build 18 {: .no_toc .text-delta } 23 --- 36 * Java Runtime Environment 7 (used as bootclasspath for cross-compilation) 43 * Maven Ant Tasks 2.1.3 (GA only) \[<http://maven.apache.org/ant-tasks>\] [all …]
|
| /third_party/grpc/tools/dockerfile/grpc_artifact_python_manylinux2014_x86/ |
| D | Dockerfile | 7 # http://www.apache.org/licenses/LICENSE-2.0 15 # Docker file for building gRPC manylinux Python artifacts. 17 # AUTO-GENERATED FROM `$REPO_ROOT/templates/tools/dockerfile/grpc_artifact_python_manylinux2014_x86… 19 FROM quay.io/pypa/manylinux2014_i686:2024-09-09-f386546 25 RUN yum update -y && yum install -y curl-devel expat-devel gettext-devel openssl-devel zlib-devel 28 # Install Python build requirements 29 RUN /opt/python/cp38-cp38/bin/pip install --upgrade 'cython<4.0.0rc1' 30 RUN /opt/python/cp39-cp39/bin/pip install --upgrade 'cython<4.0.0rc1' 31 RUN /opt/python/cp310-cp310/bin/pip install --upgrade 'cython<4.0.0rc1' 32 RUN /opt/python/cp311-cp311/bin/pip install --upgrade 'cython<4.0.0rc1' [all …]
|
| /third_party/grpc/tools/dockerfile/grpc_artifact_python_manylinux2014_x64/ |
| D | Dockerfile | 7 # http://www.apache.org/licenses/LICENSE-2.0 15 # Docker file for building gRPC manylinux Python artifacts. 17 # AUTO-GENERATED FROM `$REPO_ROOT/templates/tools/dockerfile/grpc_artifact_python_manylinux2014_x64… 19 FROM quay.io/pypa/manylinux2014_x86_64:2024-09-09-f386546 25 RUN yum update -y && yum install -y curl-devel expat-devel gettext-devel openssl-devel zlib-devel 28 # Install Python build requirements 29 RUN /opt/python/cp38-cp38/bin/pip install --upgrade 'cython<4.0.0rc1' 30 RUN /opt/python/cp39-cp39/bin/pip install --upgrade 'cython<4.0.0rc1' 31 RUN /opt/python/cp310-cp310/bin/pip install --upgrade 'cython<4.0.0rc1' 32 RUN /opt/python/cp311-cp311/bin/pip install --upgrade 'cython<4.0.0rc1' [all …]
|
| /third_party/libabigail/ |
| D | README-DOCKER.md | 3 Libabigail comes with two Dockerfile in [docker](docker) to build each of: 5 - a Fedora base image (recommended) 6 - an Ubuntu base image. 12 Here is how to build the containers. Note that we build so it belongs to the same 15 Docker images and other OCI artifacts. 18 $ docker build -f docker/Dockerfile.fedora -t ghcr.io/woodard/libabigail-fedora . 21 $ docker build -f docker/Dockerfile.ubuntu -t ghcr.io/woodard/libabigail-ubuntu-22.04 . 31 $ docker run -it ghcr.io/woodard/libabigail-ubuntu-22.04 bash 38 /opt/abigail-env/.spack-env/view/bin/abidiff 42 You can go to the environment in `/opt/abigail-env` and (given you [all …]
|
| /third_party/curl/docs/ |
| D | INSTALL.md | 1 <!-- 4 SPDX-License-Identifier: curl 5 --> 13 package. This document describes how to compile, build and install curl and 22 ./bootstrap-vcpkg.sh 33 the `GIT-INFO.md` file in the root directory for specific instructions on how 41 ./configure --with-openssl [--with-gnutls --with-wolfssl] 52 ./configure --help 54 If you want to install curl in a different file hierarchy than `/usr/local`, 57 ./configure --prefix=/path/to/curl/tree [all …]
|
| /third_party/vulkan-loader/ |
| D | BUILD.md | 1 # Build Instructions 7 - [Build Instructions](#build-instructions) 8 - [Table Of Contents](#table-of-contents) 9 - [Contributing to the Repository](#contributing-to-the-repository) 10 - [Repository Content](#repository-content) 11 - [Installed Files](#installed-files) 12 - [Build Requirements](#build-requirements) 13 - [Test Requirements](#test-requirements) 14 - [Repository Set-Up](#repository-set-up) 15 - [Display Drivers](#display-drivers) [all …]
|
| /third_party/libabigail/doc/website/ |
| D | mainpage.txt | 10 manipulating, serializing and de-serializing ABI-relevant artifacts. 11 The set of artifacts that we are interested in is made of 18 differences and help build tools to infer interesting conclusions 51 …https://spdx.org/licenses/Apache-2.0.html">Apache version 2 license</a> with the <a href="https://… 58 http://mirrors.kernel.org/sourceware/libabigail/libabigail-2.1.tar.gz. 60 You can also get the source code in a read-only manner from our <a 69 out in read-write by doing: 83 \li <a href="http://www.freedesktop.org/wiki/Software/pkg-config/">pkg-config</a> 87 \li <a href="http://www.sphinx-doc.org/en/stable/">python-sphinx</a> 89 \subsection compile-from-tarball Compiling the code from the tarball [all …]
|
| /third_party/icu/docs/processes/release/tasks/publish/ |
| D | index.md | 1 --- 7 --- 9 <!-- 12 --> 18 {: .no_toc .text-delta } 23 --- 30 --- 36 Build the icu-demos module following the README's. Update code and/or docs as 37 needed. "Reference" platforms for icu-demos are: RedHat Linux and win32. On Linux, 38 icu-demos is built against the "make install "'ed ICU. So, run ICU4C's configure [all …]
|
| /third_party/rust/rust/src/bootstrap/ |
| D | flags.rs | 1 //! Command-line interface of the rustbuild build system. 3 //! This module implements the command-line parsing of the build system which 13 use crate::{Build, DocTests}; 45 /// use verbose output (-vv for very verbose) 46 pub verbose: u8, // each extra -v after the first is passed to Cargo 51 /// TOML configuration file for build 54 /// Build directory, overrides `build.build-dir` in `config.toml` 57 #[arg(global(true), long, value_hint = clap::ValueHint::Other, value_name = "BUILD")] 58 /// build target of the stage0 compiler 59 pub build: Option<String>, field [all …]
|
| /third_party/protobuf/java/bom/ |
| D | pom.xml | 1 <?xml version="1.0" encoding="UTF-8"?> 2 …01/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 … 6 <artifactId>protobuf-bom</artifactId> 12 <url>https://developers.google.com/protocol-buffers/</url> 32 <name>BSD-3-Clause</name> 33 <url>https://opensource.org/licenses/BSD-3-Clause</url> 43 <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> 48 <id>sonatype-nexus-staging</id> 52 <id>sonatype-nexus-staging</id> 53 <url>https://oss.sonatype.org/service/local/staging/deploy/maven2/</url> [all …]
|
| /third_party/skia/m133/third_party/externals/libwebp/infra/ |
| D | common.sh | 32 echo "[$(date +'%Y-%m-%dT%H:%M:%S%z')]: $*" >&2 36 # Create build directory. Build directory will be deleted if it exists. 43 if [[ "$#" -ne 1 ]]; then 47 local build_dir 49 rm -rf "${build_dir}" 50 mkdir -p "${build_dir}" 54 # Cleanup files from the build directory. 58 # $1 build directory. 61 # $1 is not completely removed to allow for binary artifacts to be 63 find "${1:?"Build directory not defined"}" \ [all …]
|
| /third_party/grpc/src/python/grpcio/ |
| D | commands.py | 7 # http://www.apache.org/licenses/LICENSE-2.0 45 # https://bitbucket.org/pypa/pypi/issues/120/binary-wheels-for-linux-are-not-supported 49 If we can retrieve a pre-compiled bdist from online, uses it. Else, emits a 56 # the custom wheels that we build/upload to GCS. 72 # Our chosen local bdist path. 101 import sphinx.cmd.build 104 target_dir = os.path.join(GRPC_STEM, "doc", "build") 105 exit_code = sphinx.cmd.build.build_main( 106 ["-b", "html", "-W", "--keep-going", source_dir, target_dir] 117 description = "build grpcio project metadata files" [all …]
|
| /third_party/qrcodegen/java/ |
| D | pom.xml | 1 <?xml version="1.0" encoding="UTF-8"?> 2 …//www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http:/… 10 <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> 14 <build> 19 <artifactId>maven-compiler-plugin</artifactId> 23 <id>default-compile</id> 29 <id>java8-compile</id> 37 <exclude>module-info.java</exclude> 46 <artifactId>maven-release-plugin</artifactId> 56 <artifactId>maven-source-plugin</artifactId> [all …]
|
123456