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

bazel: avoid stamping --config=dev builds #75976

Closed

Conversation

irfansharif
Copy link
Contributor

@irfansharif irfansharif commented Feb 3, 2022

When used with a remote build cache, these stamps (despite being marked
as volatile), induce an unnecessary golink step when switching back and
forth between branches. See
bazelbuild/bazel#10075. Opting out here shaves
a few precious seconds if the previously built binary is already
available.

Release note: None

Jira issue: CRDB-14749

When used with a remote build cache, these stamps (despite being marked
as volatile), induce an unnecessary golink step when switching back and
forth between branches. See
bazelbuild/bazel#10075. Opting out here shaves
a few precious seconds if the previously built binary is already
available.

Release note: None
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@@ -46,7 +46,6 @@ build:crosslinuxarm --config=cross
build:devdarwinx86_64 --platforms=//build/toolchains:darwin_x86_64
build:devdarwinx86_64 --config=dev
build:dev --define cockroach_bazel_dev=y
build:dev --stamp --workspace_status_command=./build/bazelutil/stamp.sh
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Two problems with this:

  1. In my testing, cockroach binaries can't start properly if they don't have the various stamped variables. You should be able to trivially reproduce this, but let me know if you can't. You can make this PR mergeable by removing those checks from cockroach (maybe only for dev builds if you need to?)
  2. dev doctor will fail if you delete this line without making any other changes.

@irfansharif
Copy link
Contributor Author

Not having time to follow up, I'll try again some other day.

@irfansharif irfansharif marked this pull request as draft February 17, 2022 16:32
@irfansharif
Copy link
Contributor Author

Subsumed by #79360.

@irfansharif irfansharif closed this Apr 4, 2022
@irfansharif irfansharif deleted the 220203.no-stamp-dev branch April 4, 2022 19:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants