You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, when I was learning to build a buildfarm server by docker, I found that the image bazelbuild/buildfarm-server:2.8.0 seems nerver load my custom config file correctly no matter how I adjust my command.
Then I decided to do an experiment in bazel-buildfarm/examples.
I changed the redisUri to "redis://localhost:6377".
In my expectation, bf-run will failed. But in fact nothing really happened.
Then, I changed bf-run to use environemnt viariable just as below.
It finally works: the bf-run failed.
I also tried to delete the -d option to see more detailed error info, and it did indicated that the CLI arguement do not work. But I forgot to take a screen shot.
So my question is, at least in image bazelbuild/buildfarm-server:2.8.0, the config file CLI arguement seems never work. I do belie you can reproduce this easily. If not, I'm glad to try providing more evidence.
The text was updated successfully, but these errors were encountered:
Hello, when I was learning to build a buildfarm server by docker, I found that the image bazelbuild/buildfarm-server:2.8.0 seems nerver load my custom config file correctly no matter how I adjust my command.
Then I decided to do an experiment in bazel-buildfarm/examples.
I changed the redisUri to "redis://localhost:6377".
In my expectation, bf-run will failed. But in fact nothing really happened.
Then, I changed bf-run to use environemnt viariable just as below.
It finally works: the bf-run failed.
I also tried to delete the -d option to see more detailed error info, and it did indicated that the CLI arguement do not work. But I forgot to take a screen shot.
So my question is, at least in image bazelbuild/buildfarm-server:2.8.0, the config file CLI arguement seems never work. I do belie you can reproduce this easily. If not, I'm glad to try providing more evidence.
The text was updated successfully, but these errors were encountered: