droppping post cache bazel outputs #2267

Merged
mfreeman451 merged 2 commits from refs/pull/2267/head into main 2025-10-04 04:50:49 +00:00
mfreeman451 commented 2025-10-04 04:30:00 +00:00 (Migrated from github.com)
Owner

Imported from GitHub pull request.

Original GitHub pull request: #1693
Original author: @mfreeman451
Original URL: https://github.com/carverauto/serviceradar/pull/1693
Original created: 2025-10-04T04:30:00Z
Original updated: 2025-10-04T04:50:53Z
Original head: carverauto/serviceradar:cicd/dropping_cache
Original base: main
Original merged: 2025-10-04T04:50:49Z by @mfreeman451

PR Type

Other


Description

  • Remove Bazel cache configuration from Docker build workflow

  • Add BuildBuddy API key documentation for remote builds


Diagram Walkthrough

flowchart LR
  A["Docker Build Workflow"] -- "remove" --> B["Bazel Cache Step"]
  C["Release Documentation"] -- "add" --> D["BuildBuddy API Key Info"]

File Walkthrough

Relevant files
Configuration changes
docker-build.yml
Remove Bazel cache step from workflow                                       

.github/workflows/docker-build.yml

  • Remove entire "Cache Bazel outputs" step from workflow
  • Delete cache configuration for ~/.cache/bazel and ~/.cache/bazelisk
  • Remove cache key based on Bazel configuration files
+0/-10   
Documentation
RELEASE_PUBLISHING.md
Add BuildBuddy API key documentation                                         

docs/RELEASE_PUBLISHING.md

  • Add BUILDBUDDY_API_KEY to required secrets list
  • Document API key requirement for remote Bazel authentication
+1/-0     

Imported from GitHub pull request. Original GitHub pull request: #1693 Original author: @mfreeman451 Original URL: https://github.com/carverauto/serviceradar/pull/1693 Original created: 2025-10-04T04:30:00Z Original updated: 2025-10-04T04:50:53Z Original head: carverauto/serviceradar:cicd/dropping_cache Original base: main Original merged: 2025-10-04T04:50:49Z by @mfreeman451 --- ### **PR Type** Other ___ ### **Description** - Remove Bazel cache configuration from Docker build workflow - Add BuildBuddy API key documentation for remote builds ___ ### Diagram Walkthrough ```mermaid flowchart LR A["Docker Build Workflow"] -- "remove" --> B["Bazel Cache Step"] C["Release Documentation"] -- "add" --> D["BuildBuddy API Key Info"] ``` <details> <summary><h3> File Walkthrough</h3></summary> <table><thead><tr><th></th><th align="left">Relevant files</th></tr></thead><tbody><tr><td><strong>Configuration changes</strong></td><td><table> <tr> <td> <details> <summary><strong>docker-build.yml</strong><dd><code>Remove Bazel cache step from workflow</code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </dd></summary> <hr> .github/workflows/docker-build.yml <ul><li>Remove entire "Cache Bazel outputs" step from workflow<br> <li> Delete cache configuration for <code>~/.cache/bazel</code> and <code>~/.cache/bazelisk</code><br> <li> Remove cache key based on Bazel configuration files</ul> </details> </td> <td><a href="https://github.com/carverauto/serviceradar/pull/1693/files#diff-3414847e2ad632333f775cabb810f0dc0df61a570365df34750a08b00912fe82">+0/-10</a>&nbsp; &nbsp; </td> </tr> </table></td></tr><tr><td><strong>Documentation</strong></td><td><table> <tr> <td> <details> <summary><strong>RELEASE_PUBLISHING.md</strong><dd><code>Add BuildBuddy API key documentation</code>&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; </dd></summary> <hr> docs/RELEASE_PUBLISHING.md <ul><li>Add <code>BUILDBUDDY_API_KEY</code> to required secrets list<br> <li> Document API key requirement for remote Bazel authentication</ul> </details> </td> <td><a href="https://github.com/carverauto/serviceradar/pull/1693/files#diff-6ca2ba93be21a4d63c3f8a08ff4889a2979a0c281a4bb70dbe15635bd199bc7e">+1/-0</a>&nbsp; &nbsp; &nbsp; </td> </tr> </table></td></tr></tr></tbody></table> </details> ___
qodo-code-review[bot] commented 2025-10-04 04:30:17 +00:00 (Migrated from github.com)
Author
Owner

Imported GitHub PR comment.

Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/1693#issuecomment-3367884231
Original created: 2025-10-04T04:30:17Z

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢
No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🎫 No ticket provided
  • Create ticket/issue
Codebase Duplication Compliance
Codebase context is not defined

Follow the guide to enable codebase context checks.

Custom Compliance
No custom compliance provided

Follow the guide to enable custom compliance check.

  • Update
Compliance status legend 🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
- Requires Further Human Verification
🏷️ - Compliance label
Imported GitHub PR comment. Original author: @qodo-code-review[bot] Original URL: https://github.com/carverauto/serviceradar/pull/1693#issuecomment-3367884231 Original created: 2025-10-04T04:30:17Z --- ## PR Compliance Guide 🔍 <!-- https://github.com/carverauto/serviceradar/commit/501b3a7f8491715d56d33b5566a7d29ae07675a8 --> Below is a summary of compliance checks for this PR:<br> <table><tbody><tr><td colspan='2'><strong>Security Compliance</strong></td></tr> <tr><td>🟢</td><td><details><summary><strong>No security concerns identified</strong></summary> No security vulnerabilities detected by AI analysis. Human verification advised for critical code. </details></td></tr> <tr><td colspan='2'><strong>Ticket Compliance</strong></td></tr> <tr><td>⚪</td><td><details><summary>🎫 <strong>No ticket provided </summary></strong> - [ ] Create ticket/issue <!-- /create_ticket --create_ticket=true --> </details></td></tr> <tr><td colspan='2'><strong>Codebase Duplication Compliance</strong></td></tr> <tr><td>⚪</td><td><details><summary><strong>Codebase context is not defined </strong></summary> Follow the <a href='https://qodo-merge-docs.qodo.ai/core-abilities/rag_context_enrichment/'>guide</a> to enable codebase context checks. </details></td></tr> <tr><td colspan='2'><strong>Custom Compliance</strong></td></tr> <tr><td>⚪</td><td><details><summary><strong>No custom compliance provided</strong></summary> Follow the <a href='https://qodo-merge-docs.qodo.ai/tools/compliance/'>guide</a> to enable custom compliance check. </details></td></tr> <tr><td align="center" colspan="2"> - [ ] Update <!-- /compliance --update_compliance=true --> </td></tr></tbody></table> <details><summary>Compliance status legend</summary> 🟢 - Fully Compliant<br> 🟡 - Partial Compliant<br> 🔴 - Not Compliant<br> ⚪ - Requires Further Human Verification<br> 🏷️ - Compliance label<br> </details>
qodo-code-review[bot] commented 2025-10-04 04:30:43 +00:00 (Migrated from github.com)
Author
Owner

Imported GitHub PR comment.

Original author: @qodo-code-review[bot]
Original URL: https://github.com/carverauto/serviceradar/pull/1693#issuecomment-3367884524
Original created: 2025-10-04T04:30:43Z

PR Code Suggestions

No code suggestions found for the PR.

Imported GitHub PR comment. Original author: @qodo-code-review[bot] Original URL: https://github.com/carverauto/serviceradar/pull/1693#issuecomment-3367884524 Original created: 2025-10-04T04:30:43Z --- ## PR Code Suggestions ✨ No code suggestions found for the PR.
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
carverauto/serviceradar!2267
No description provided.