PB-1575: in k8s mode, write BUILDKITE_ENV_FILE to /workspace#3683
Merged
PB-1575: in k8s mode, write BUILDKITE_ENV_FILE to /workspace#3683
Conversation
DrJosh9000
approved these changes
Jan 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
$BUILDKITE_ENV_FILEis currently broken in k8s stack as/tmpisn't a shared volume containers in the same pod.This PR updated job_runner so in k8s mode, env files are created in
/workspace, it's the hardcoded workspace location for agent k8s stack.I plan to add the test coverage for this as we upgrade agent version in agent k8s stack.
Context
part of PS-1575
Testing
go test ./...). Buildkite employees may check this if the pipeline has run automatically.go tool gofumpt -extra -w .)Disclosures / Credits
LLM and light baby sitting.