Skip to content

Build in devcontainers in CI - #371

Open
bdice wants to merge 2 commits into
rapidsai:mainfrom
bdice:build-devcontainer-in-ci
Open

Build in devcontainers in CI#371
bdice wants to merge 2 commits into
rapidsai:mainfrom
bdice:build-devcontainer-in-ci

Conversation

@bdice

@bdice bdice commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

This enables devcontainer builds in CI for verification of builds.

@bdice
bdice requested a review from a team as a code owner July 12, 2026 15:29
@bdice
bdice requested a review from karthikeyann July 12, 2026 15:29

@mattgara mattgara left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One issue related to credentials exposure, but otherwise LGTM.

Comment thread .github/workflows/pr.yaml
imageTag: cuda${{ matrix.cuda }}-${{ matrix.arch }}
cacheFrom: ghcr.io/rapidsai/velox-testing/devcontainer:latest-cuda${{ matrix.cuda }}
env: |
AWS_ACCESS_KEY_ID=${{ env.AWS_ACCESS_KEY_ID }}

@mattgara mattgara Jul 22, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks to pass a 12-hour AWS session plus an sccache auth token into code from the PR checkout. I'm not sure in what context the dev containers are supposed to be used, but could we consider moving this credentialed build behind a manually dispatched workflow on main and a protected trusted-pr-build environment, with a manually maintained trusted team as required reviewers? This is mostly to prevent someone accessing said credentials in their PR's container unbeknownst to us.

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.

2 participants