Open p0deje opened 4 months ago
Is the dist/main/
directory included by accident? Many files seem duplicate between .
and dist/main/
, for example, dist/main/remote-cache-server.js
is in both paths.
@chickenandpork It's included intentionally, so I could test the branch in GHA directly. This however is not intended to be used directly as it's not really working stable. Are you interested in taking over and finishing this PR?
@chickenandpork It's included intentionally, so I could test the branch in GHA directly. This however is not intended to be used directly as it's not really working stable.
OK, I understand; it looked like an error of duplicate code!
Are you interested in taking over and finishing this PR?
I don't think my javascript is sufficient. I only worked javascript (and coffeescript!) briefly around 2020. Sorry :(
Personally I use a local buchgr cache and I set up the same in ephemeral build clusters.
@chickenandpork It's included intentionally, so I could test the branch in GHA directly. This however is not intended to be used directly as it's not really working stable. Are you interested in taking over and finishing this PR?
I'm interested in picking this up. What's not stable? What else is outstanding?
@JohnAmican The summary is in https://github.com/bazel-contrib/setup-bazel/issues/18#issuecomment-2143683673, the stability is the main issue as on large projects the REST API calls to the GHA cache get rate limited.
Related to #18
This pull request introduces a significant enhancement to the setup-bazel action by implementing a remote cache server for Bazel build outputs, aiming to improve build performance and cache utilization.
remote-cache-server.js
that creates an HTTP server compatible with Bazel's remote caching API. This server handlesGET
andPUT
requests to store and retrieve cache objects, leveraging@actions/cache
for underlying storage.index.js
to start the remote cache server as a detached process during the action's execution. The server's URL is then added to.bazelrc
to enable Bazel to use it for caching.config.js
to include settings for the remote cache server's URL and log file path, ensuring that these new features are configurable.post.js
to stop the remote cache server gracefully at the end of the action's execution and logs the server's output for debugging purposes.package.json
to include the remote cache server in the build process, ensuring that all necessary components are compiled and ready for use.For more details, open the Copilot Workspace session.