Home
last modified time | relevance | path

Searched full:monorepo (Results 1 – 25 of 214) sorted by relevance

123456789

/external/google-cloud-java/.github/workflows/
Dmerge_repository.yaml26 working-directory: generation/monorepo/google-cloud-java-merged
29 working-directory: generation/monorepo/google-cloud-java-merged
31 - name: Push monorepo to branch
34 cd generation/monorepo/google-cloud-java-merged
35 …git remote add monorepo https://${{ github.actor }}:${{ github.token }}@github.com/${{ github.repo…
36 git push -f monorepo main:bootstrap_output
39 cd generation/monorepo/diff
40 …git remote add monorepo https://${{ github.actor }}:${{ github.token }}@github.com/${{ github.repo…
41 git push -f monorepo main:bootstrap_output_diff_${{ github.event_name }}
Dnewclient.yaml69 …git remote add monorepo https://${{ github.actor }}:${{ github.token }}@github.com/${{ github.repo…
70 git fetch -q --unshallow monorepo
71 git push -f monorepo newclient_output_${{ github.event_name }}
/external/google-cloud-java/generation/
Dmerge_repository.sh15 # cd generation/monorepo/google-cloud-java-merged
26 rm -rf monorepo
27 mkdir monorepo
29 cp merge_repository.sh monorepo
30 cp repos.txt monorepo
32 cd monorepo
49 # setup owlbot files correctly to match monorepo configuration
57 # In monorepo, the staging directory structure tells the destination module to
79 # cwd: monorepo/google-cloud-java-merged
141 # create a monorepo/diff repo
DREADME.md8 ## Merge repository into the monorepo
12 The script creates a new Git repository in `monorepo/google-cloud-java` by merging
17 cd monorepo/google-cloud-java
23 The file `repos.txt` lists all the split repos to include in the aggregation into the monorepo.
Dapply_current_versions.sh4 # pom.xml files in this monorepo.
9 # # Run this script at the root of the monorepo
Dset_owlbot_config.sh4 # that the paths correctly reference the files under the modules in this monorepo.
44 # In monorepo, the staging directory structure tells the destination module to
Dgenerate_root_versions_txt.sh4 # This should be run during addition of a new-module to the monorepo
/external/google-cloud-java/owl-bot-postprocessor/
Dcloudbuild.yaml11 '-t', 'gcr.io/cloud-devrel-public-resources/owlbot-java-monorepo:$SHORT_SHA',
12 '-t', 'gcr.io/cloud-devrel-public-resources/owlbot-java-monorepo:latest',
16 - gcr.io/cloud-devrel-public-resources/owlbot-java-monorepo:$SHORT_SHA
17 - gcr.io/cloud-devrel-public-resources/owlbot-java-monorepo:latest
DREADME.md4 monorepo. The Cloud Build in the repo-automation-bots GCP project publishes
5 `gcr.io/cloud-devrel-public-resources/owlbot-java-monorepo` image.
14 This separation allows us to focus on monorepo-specific postprocessor logic in
15 this `owlbot-java-monorepo` image, without interfering the split repositories.
/external/cronet/stable/third_party/libc++/src/utils/ci/
Drun-buildbot-container10 # This script must be run from within the LLVM monorepo. Furthermore, the
11 # monorepo will be mounted as `/llvm` inside the container. Be careful, the
26 … echo "Was unable to find the root of the LLVM monorepo; are you running from within the monorepo?"
/external/cronet/tot/third_party/libc++/src/utils/ci/
Drun-buildbot-container10 # This script must be run from within the LLVM monorepo. Furthermore, the
11 # monorepo will be mounted as `/llvm` inside the container. Be careful, the
26 … echo "Was unable to find the root of the LLVM monorepo; are you running from within the monorepo?"
/external/bazelbuild-rules_python/gazelle/python/testdata/monorepo/
DREADME.md1 # Monorepo chapter
4 to simulate a monorepo.
/external/google-cloud-java/
D.gitignore59 # Monorepo repository generation
60 monorepo
/external/google-cloud-java/.kokoro/
Dcreate_commits_from_googleapis_commits.sh5 # to google-cloud-java monorepo.
7 # monorepo (usually "origin/master").
8 # This script creates Git commits to this google-cloud-java monorepo that
/external/cronet/tot/third_party/libc++/src/utils/ci/vendor/android/
Drun-buildbot-container10 … echo "Was unable to find the root of the LLVM monorepo; are you running from within the monorepo?"
/external/cronet/stable/third_party/libc++/src/utils/ci/vendor/android/
Drun-buildbot-container10 … echo "Was unable to find the root of the LLVM monorepo; are you running from within the monorepo?"
/external/google-cloud-java/owl-bot-postprocessor/synthtool/languages/
Djava.py491 # to monorepo. The owlbot.py in the monorepo sets monorepo=True.
492 monorepo = kwargs.get("monorepo", False)
493 split_repo = not monorepo
496 # Special libraries that are not GAPIC_AUTO but in the monorepo
508 "monorepo: {}, split_repo: {}, library_type: {},"
510 monorepo,
/external/pigweed/pw_protobuf_compiler/
Dnanopb_proto_library.bzl40 When using nanopb_proto_library from a monorepo in which nanopb is not an
47 # Monorepo case
/external/cronet/stable/third_party/libc++abi/src/src/demangle/
DREADME.txt19 this comes from before the monorepo, and both [sub]projects need to
48 FIXME: Now that LLVM is a monorepo, it should be possible to
/external/cronet/tot/third_party/libc++abi/src/src/demangle/
DREADME.txt19 this comes from before the monorepo, and both [sub]projects need to
48 FIXME: Now that LLVM is a monorepo, it should be possible to
/external/swiftshader/third_party/llvm-16.0/llvm/include/llvm/Demangle/
DREADME.txt19 this comes from before the monorepo, and both [sub]projects need to
48 FIXME: Now that LLVM is a monorepo, it should be possible to
/external/crosvm/hypervisor/src/gunyah/gunyah_sys/
Dbindgen.sh14 # use local copy until gunyah.h is available in chromium monorepo
/external/google-cloud-java/java-notification/
Dowlbot.py21 java.common_templates(monorepo=True, excludes=[
/external/google-cloud-java/java-aiplatform/
Dowlbot.py24 java.common_templates(monorepo=True, excludes=[
/external/google-cloud-java/java-memcache/
Dowlbot.py24 java.common_templates(monorepo=True, excludes=[

123456789