Skip to content

target pattern file: allow comments#15903

Closed
sluongng wants to merge 1 commit intobazelbuild:masterfrom
sluongng:sluongng/target-pattern-file-comment
Closed

target pattern file: allow comments#15903
sluongng wants to merge 1 commit intobazelbuild:masterfrom
sluongng:sluongng/target-pattern-file-comment

Conversation

@sluongng
Copy link
Copy Markdown
Contributor

--target_pattern_file could be a great tool assisting migration of a
code base from one Bazel config to another. User could define a list of
targets that can be built with the new configs and incrementally expand
that list with each change that was introduced. Multiple users / teams
could collaborate on such migration by adding / removing their targets
into / from the pattern file.

Having the ability to provide comments to annotate the targets in the
pattern file with extra information during the migration process added a
great value and context for build maintainers to track migration
progress.

Add support for Bash-style comments to the target-pattern file.

@sluongng sluongng force-pushed the sluongng/target-pattern-file-comment branch from 27f6487 to 5681ba2 Compare July 18, 2022 11:18
@sgowroji sgowroji added team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website awaiting-review PR is awaiting review from an assigned reviewer labels Jul 18, 2022
@sluongng sluongng force-pushed the sluongng/target-pattern-file-comment branch from 5681ba2 to aeae3a4 Compare July 19, 2022 09:47
`--target_pattern_file` could be a great tool assisting migration of a
code base from one Bazel config to another.  User could define a list of
targets that can be built with the new configs and incrementally expand
that list with each change that was introduced.  Multiple users / teams
could collaborate on such migration by adding / removing their targets
into / from the pattern file.

Having the ability to provide comments to annotate the targets in the
pattern file with extra information during the migration process added a
great value and context for build maintainers to track migration
progress.

Add support for Bash-style comments to the target-pattern file.
@sluongng sluongng force-pushed the sluongng/target-pattern-file-comment branch from aeae3a4 to 43b4b64 Compare July 19, 2022 10:19
@sluongng
Copy link
Copy Markdown
Contributor Author

unclear why LocalDiffAwarenessIntegrationTest failed on darwin https://buildkite.com/bazel/bazel-bazel-github-presubmit/builds/11687#018215db-540d-4499-a0fc-8724f35afacf

gona rebase on top of latest master to see if it gets better.

@Wyverald
Copy link
Copy Markdown
Member

That's a flaky test, no need to worry :)

@Wyverald Wyverald added awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally and removed awaiting-review PR is awaiting review from an assigned reviewer labels Jul 19, 2022
@brentleyjones
Copy link
Copy Markdown
Contributor

@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 Jul 19, 2022
@sgowroji sgowroji removed the awaiting-PR-merge PR has been approved by a reviewer and is ready to be merge internally label Jul 19, 2022
@sgowroji
Copy link
Copy Markdown
Member

@bazel-io fork 5.3.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 Jul 19, 2022
ckolli5 pushed a commit to ckolli5/bazel that referenced this pull request Jul 19, 2022
`--target_pattern_file` could be a great tool assisting migration of a
code base from one Bazel config to another.  User could define a list of
targets that can be built with the new configs and incrementally expand
that list with each change that was introduced.  Multiple users / teams
could collaborate on such migration by adding / removing their targets
into / from the pattern file.

Having the ability to provide comments to annotate the targets in the
pattern file with extra information during the migration process added a
great value and context for build maintainers to track migration
progress.

Add support for Bash-style comments to the target-pattern file.

Closes bazelbuild#15903.

PiperOrigin-RevId: 461861131
Change-Id: I401f71fcf1e343c8689424979e4f48fb723fba9f
sgowroji added a commit that referenced this pull request Jul 20, 2022
`--target_pattern_file` could be a great tool assisting migration of a
code base from one Bazel config to another.  User could define a list of
targets that can be built with the new configs and incrementally expand
that list with each change that was introduced.  Multiple users / teams
could collaborate on such migration by adding / removing their targets
into / from the pattern file.

Having the ability to provide comments to annotate the targets in the
pattern file with extra information during the migration process added a
great value and context for build maintainers to track migration
progress.

Add support for Bash-style comments to the target-pattern file.

Closes #15903.

PiperOrigin-RevId: 461861131
Change-Id: I401f71fcf1e343c8689424979e4f48fb723fba9f

Co-authored-by: Son Luong Ngoc <[email protected]>
Co-authored-by: Gowroji Sunil <[email protected]>
aranguyen pushed a commit to aranguyen/bazel that referenced this pull request Jul 20, 2022
`--target_pattern_file` could be a great tool assisting migration of a
code base from one Bazel config to another.  User could define a list of
targets that can be built with the new configs and incrementally expand
that list with each change that was introduced.  Multiple users / teams
could collaborate on such migration by adding / removing their targets
into / from the pattern file.

Having the ability to provide comments to annotate the targets in the
pattern file with extra information during the migration process added a
great value and context for build maintainers to track migration
progress.

Add support for Bash-style comments to the target-pattern file.

Closes bazelbuild#15903.

PiperOrigin-RevId: 461861131
Change-Id: I401f71fcf1e343c8689424979e4f48fb723fba9f
aranguyen pushed a commit to aranguyen/bazel that referenced this pull request Jul 20, 2022
`--target_pattern_file` could be a great tool assisting migration of a
code base from one Bazel config to another.  User could define a list of
targets that can be built with the new configs and incrementally expand
that list with each change that was introduced.  Multiple users / teams
could collaborate on such migration by adding / removing their targets
into / from the pattern file.

Having the ability to provide comments to annotate the targets in the
pattern file with extra information during the migration process added a
great value and context for build maintainers to track migration
progress.

Add support for Bash-style comments to the target-pattern file.

Closes bazelbuild#15903.

PiperOrigin-RevId: 461861131
Change-Id: I401f71fcf1e343c8689424979e4f48fb723fba9f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants