Brandon Duffany

Remove podman overhead when rapidly recycling runners

1

(Context: https://buildbuddy-corp.slack.com/archives/C057TAUAQ7P/p1716579465393109?thread_ts=1716243012.902439&cid=C057TAUAQ7P) When runner recycling is enabled, we currently have significant overhead introduced by podman due to running `podman unpause`, `podman exec`, and `podman pause` for each execution. `pause` and...

cli: support passing `--config` options in tools/bazel

1

**Related issues**: Fixes https://github.com/buildbuddy-io/buildbuddy/issues/6466

**Related issues**: N/A

More automated CLI login flow

1

Running `bb login` now opens a web auth flow that is fully automated in the "happy path" (already logged in to bb, only a member of one org, org has...

Roll-forward 'Fix container stats baseline for recycled runners (#7080)'

3

Context: https://buildbuddy-corp.slack.com/archives/C06N9AHA4JX/p1722370297422949 **Related issues**: N/A

This is helpful for debugging in situations where we don't have the action for display in the UI, which is where we normally get the snapshot ID. For example, we...

Running the executor with `--executor.delete_build_root_on_startup` deletes the contents of `--executor.build_root_directory`. This is where temporary files are stored (action workspaces, firecracker chroot dirs, etc.). Unfortunately, this is also where cached firecracker...

This is preventing us from tracking execution usage when setting `--remote_exec_header=x-buildbuddy-platform.use-self-hosted-executors=false`

Make firecracker CoW tests run on CI

1

**Related issues**: N/A

This PR turned out to be much larger than expected so I'll probably try to find a way to split this into smaller PRs. Just putting this here for reference...