Skip to content

build: ensure build-packages-dist script works on macOS #17247

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

Merged

Conversation

devversion
Copy link
Member

The build-packages-dist script does not seem to work on MacOS
because the cp --no-preserve flag is not supported by default.

This commit switches to a simple chmod call in order to make it
work in all Bash environments. Additionally the script has been updated
to clean previous npm_package outputs. This ensures that the version
placeholder is properly replaced in the release output.

This is necessary due to a bug in rules_nodejs. Read more here:
bazel-contrib/rules_nodejs#1219

@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Oct 1, 2019
@devversion devversion requested a review from a team as a code owner October 1, 2019 09:45
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Oct 1, 2019
@devversion devversion changed the title build: ensure build-packages-dist script works in macOS build: ensure build-packages-dist script works on macOS Oct 1, 2019
The `build-packages-dist` script does not seem to work on MacOS
because the `cp --no-preserve` flag is not supported by default.

This commit switches to a simple `chmod` call in order to make it
work in all Bash environments. Additionally the script has been updated
to clean previous `npm_package` outputs. This ensures that the version
placeholder is properly replaced in the release output.

This is necessary due to a bug in `rules_nodejs`. Read more here:
bazel-contrib/rules_nodejs#1219
@devversion devversion force-pushed the build/ensure-clean-release-output branch from 09346cf to 6ef4985 Compare October 1, 2019 10:10
@devversion devversion added this to the 9.0.0 milestone Oct 1, 2019
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

We should add an item to the devinfra backlog for something like a bash lint that could catch this type of problem

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Oct 1, 2019
@jelbourn jelbourn merged commit c2562fb into angular:master Oct 1, 2019
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Nov 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants