Skip to content

CI: use EngFlow Opal for remote caching#213

Merged
jayconrod merged 9 commits intomainfrom
remote-cache
Apr 13, 2026
Merged

CI: use EngFlow Opal for remote caching#213
jayconrod merged 9 commits intomainfrom
remote-cache

Conversation

@jayconrod
Copy link
Copy Markdown
Collaborator

For #31

For #31

Signed-off-by: Jay Conrod <jay@engflow.com>
Signed-off-by: Jay Conrod <jay@engflow.com>
Signed-off-by: Jay Conrod <jay@engflow.com>
Signed-off-by: Jay Conrod <jay@engflow.com>
Signed-off-by: Jay Conrod <jay@engflow.com>
Signed-off-by: Jay Conrod <jay@engflow.com>
Signed-off-by: Jay Conrod <jay@engflow.com>
Signed-off-by: Jay Conrod <jay@engflow.com>
Signed-off-by: Jay Conrod <jay@engflow.com>
@jayconrod jayconrod marked this pull request as ready for review April 7, 2026 21:33
@jayconrod
Copy link
Copy Markdown
Collaborator Author

@mateusz-olczyk I enabled remote caching only for now. I had trouble getting CI Runners working, so the actual build jobs still run on GitHub hosted runners, and they'll run build commands locally, but they'll only do so if the results are not available in the remote cache.

I can turn on remote execution next, but let's get this piece in first.

@mateusz-olczyk mateusz-olczyk linked an issue Apr 13, 2026 that may be closed by this pull request
@jayconrod jayconrod merged commit b00c447 into main Apr 13, 2026
16 checks passed
@jayconrod jayconrod deleted the remote-cache branch April 13, 2026 14:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Preserve Bazel cache between CI runs

2 participants