Skip to content

bazel: introduce a new nonogo config, update dev script#73689

Merged
craig[bot] merged 1 commit intocockroachdb:masterfrom
rickystewart:nonogo
Dec 10, 2021
Merged

bazel: introduce a new nonogo config, update dev script#73689
craig[bot] merged 1 commit intocockroachdb:masterfrom
rickystewart:nonogo

Conversation

@rickystewart
Copy link
Copy Markdown
Collaborator

The introduction of nogo actually makes building the full dev binary
rather heavyweight, which vastly increases the surface area of possible
build failures. Add a new lightweight nonogo config and reference it
in an error message so that people can debug their way around the issue.

Close #73656.

Release note: None

@rickystewart rickystewart requested a review from rail December 10, 2021 17:13
@cockroach-teamcity
Copy link
Copy Markdown
Member

This change is Reviewable

@rickystewart rickystewart requested review from jlinder and removed request for rail December 10, 2021 17:13
Copy link
Copy Markdown
Collaborator

@jlinder jlinder left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed 4 of 4 files at r1, all commit messages.
Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @rickystewart)

The introduction of `nogo` actually makes building the full `dev` binary
rather heavyweight, which vastly increases the surface area of possible
build failures. Add a new lightweight `nonogo` config and reference it
in an error message so that people can debug their way around the issue.

Close cockroachdb#73656.

Release note: None
@rickystewart
Copy link
Copy Markdown
Collaborator Author

bors r=jlinder

@craig
Copy link
Copy Markdown
Contributor

craig bot commented Dec 10, 2021

Build succeeded:

@craig craig bot merged commit b145aba into cockroachdb:master Dec 10, 2021
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.

dev: dev doctor can fail due to misconfigured Bazel

3 participants