-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remote_coverage_tools / coverage_output_generator-v2.6.zip lacks provenance, instructions to build from source #15459
Comments
cc @c-mita |
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 1+ years. It will be closed in the next 90 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team ( |
This is still valid today. |
I believe the coverage output generator jar is built from here: https://github.com/bazelbuild/bazel/blob/master/tools/test/CoverageOutputGenerator/java/com/google/devtools/coverageoutputgenerator/Main.java |
Just for reference, seems the build instructions are here, and looks like building it is a manual process:
|
Includes a README.md file to the final .zip file providing the commit hash, timestamp, and build command to produce the file. Fixes bazelbuild#15459
Description of the bug:
Inside each of the java_tools distribution artifacts is a README.md including instructions to rebuild the artifacts from source.
Example from https://github.com/bazelbuild/java_tools/releases/download/java_v11.7.1/java_tools_linux-v11.7.1.zip
However remote_coverage_tools / coverage_output_generator-v2.6.zip lacks comparable information. As a result, end users have no idea where these bits came from or how to patch and compile this artifact from source.
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Observe that there is no README. Additionally there are no breadcrumbs in the included
all_lcov_merger_tools_deploy.jar
. (I see no hints of build stamping.)Which operating system are you running Bazel on?
Linux (CentOS 8)
What is the output of
bazel info release
?release 5.1.1
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?No response
Have you found anything relevant by searching the web?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: