Skip to content
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

Include Bazel version information in profile metadata. #17562

Closed
wants to merge 1 commit into from

Conversation

meisterT
Copy link
Member

This is helpful when building tools on top of the JSON profile which might to need to distinguish with what Bazel version the profile was written to be able to parse or interpret it correctly.

This is helpful when building tools on top of the JSON profile which might to
need to distinguish with what Bazel version the profile was written to be able
to parse or interpret it correctly.
@meisterT
Copy link
Member Author

cc @saraadams

@saraadams
Copy link
Contributor

cc @saraadams

Thank you!

@brentleyjones
Copy link
Contributor

@meisterT Nice! This isn't a breaking change, right? Can it go into 6.1?

@meisterT
Copy link
Member Author

If we do other cherry picks anyway, this should be easy to add.

@brentleyjones
Copy link
Contributor

Thanks. I assume we will for #17561 and #17557 at a minimum.

@keertk
Copy link
Member

keertk commented Feb 23, 2023

@bazel-io flag

@bazel-io bazel-io added the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Feb 23, 2023
@ShreeM01
Copy link
Contributor

@bazel-io fork 6.1.0

@bazel-io bazel-io removed the potential release blocker Flagged by community members using "@bazel-io flag". Should be added to a release blocker milestone label Feb 23, 2023
@keertk keertk removed the awaiting-review PR is awaiting review from an assigned reviewer label Feb 26, 2023
keertk pushed a commit that referenced this pull request Feb 28, 2023
This is basically the same as
https://github.com/bazelbuild/bazel/pull/17562/files before we did the JSON
trace profile refactoring.

---

This is helpful when building tools on top of the JSON profile which might to need to distinguish with what Bazel version the profile was written to be able to parse or interpret it correctly.

Closes #17562.

PiperOrigin-RevId: 511761823
Change-Id: I9c31494bfc07be898250d75821dd080e5b68b6db
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Performance Issues for Performance teams
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants