Build Invocation Data not Shareable Across Docker containers even when stored in S3
nickden3 opened this issue · comments
Describe the bug
Using the config setting: storage.aws_s3: build data should be shareable between buildbuddy containers when looking at the same invocation id.
To Reproduce
Steps to reproduce the behavior:
Start a buildbuddy container with storage.aws_s3 setting configured. Run a bazel build and note the inovcation ID. Verify the data lands in S3 for that ID. Restart the buildbuddy container and go to http://localhost:8080/invocation/ of the ID you just verified in S3 and buildbuddy returns a 404.
Expected behavior
I would expect any buildbuddy container that is configured to use S3 as data storage to be able to see invocation data of a build, given it exists in S3.
Screenshots
Desktop (please complete the following information):
- OS: macOs 14.3
- Browser Chrome
Hey @nickden3 - are you configuring a MySQL database?
https://www.buildbuddy.io/docs/config-database
Invocation metadata is stored in the database, so that'd have to be shared in order to work across BuildBuddy servers.
I am currently testing locally and believe I configured the sqllite db correctly, is there a way to confirm?
Our SQLite implementation is only intended to support a single BuildBuddy instance. If you're trying to support multiple BuildBuddy instances, you'd need to use MySQL or PostegreSQL.