juergbi commented on PR #1926: URL: https://github.com/apache/buildstream/pull/1926#issuecomment-2210334228
> It looks like `ci.buildgrid.yml` is using nightly buildbox from `registry.gitlab.com/buildgrid/buildgrid.hub.docker.com/buildbox:nightly` That's used for the worker container, which is not relevant to this PR. buildbox-casd used by BuildStream CI on the client side is taken from https://gitlab.com/BuildStream/buildstream-docker-images/, which uses the latest release from https://gitlab.com/BuildGrid/buildbox/buildbox-integration/. However, BuildStream CI uses a manually updated version from buildstream-docker-images, so this is actually still running with an old version of BuildBox. I'll push a commit to update the image for CI. (I did run the BuildStream BuildGrid tests locally with both older and updated BuildBox). > Should we EOL the older codepaths eventually and just have a hard dependency on BuildBox 1.2.6+ ? Maybe in 6 months ? I think so, yes. I'd like to require BuildBox 1.2.8+ after some grace period to also ensure [buildbox-run-bubblewrap drops all Linux capabilities](https://gitlab.com/BuildGrid/buildbox/buildbox/-/merge_requests/625) (only relevant when running bst as privileged user) and include support for access tokens. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
