Lines Matching +full:bazel +full:- +full:cache

1 .. _docs-github:
12 well-supported within Google but complicated to deploy, so Pigweed has support
13 for `GitHub Actions <github-actions>`_ as well.
15 .. _github-actions: https://docs.github.com/en/actions
17 Bazel  chapter
19 Configuring a Bazel builder that runs on pull requests is straightforward.
20 There are four steps: `checkout`_, `get Bazel`_, build, and test. There
21 are good community-managed actions for the first two steps, and the last two
25 .. _get Bazel: https://github.com/marketplace/actions/setup-bazel-environment
27 The Bazel version retrieved is configured through a ``.bazelversion`` file in
30 .. code-block:: yaml
33    run-name: presubmit run triggered by ${{ github.actor }}
40      bazel-build-test:
41        runs-on: ubuntu-latest
43          - name: Checkout
46              fetch-depth: 0
48          - name: Get Bazel
49            uses: bazel-contrib/setup-bazel@0.8.1
51              # Avoid downloading Bazel every time.
52              bazelisk-cache: true
53              # Store build cache per workflow.
54              disk-cache: ${{ github.workflow }}
55              # Share repository cache between workflows.
56              repository-cache: true
57          - name: Bazel Build
58            run: bazel build ...
59          - name: Bazel Test
60            run: bazel test ...
64 Configuring a builder that uses `pw_env_setup <module-pw_env_setup>`_ and
65 `pw_presubmit <module-pw_presubmit>`_ is also relatively simple. When run
77 … https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-a…
79 For Pigweed itself, the only ``pw_presubmit``-based action runs lintformat. To
83 .. code-block:: yaml
92      bazel-build-test:
93        runs-on: ubuntu-latest
95          - name: Checkout
98              fetch-depth: 0
100          - name: Bootstrap
102          - name: python_format
103            run: pw presubmit --program lintformat --keep-going