Skip to content

build: do not accidentally cache undesired files in github action #23875

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

This commit fixes that the Github actions currently may cache undesired
files. e.g. when Bazel runs the dist/ folder is populated and
symlinked with the execroot, where another clone of the node_modules
would be cached accidentally then. We use an explicit path instead of a
pattern as it has been recommended by the Github action documentation.

Additionally, we fix that the dev-app building on RBE occurs with 2
concurrent jobs due to the host containers only having 2 cores. We can
run more jobs in the RBE containers.

@google-cla google-cla bot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Nov 2, 2021
This commit fixes that the Github actions currently may cache undesired
files. e.g. when Bazel runs the `dist/` folder is populated and
symlinked with the execroot, where another clone of the `node_modules`
would be cached accidentally then. We use an explicit path instead of a
pattern as it has been recommended by the Github action documentation.

Additionally, we fix that the dev-app building on RBE occurs with 2
concurrent jobs due to the host containers only having 2 cores. We can
run more jobs in the RBE containers.
@devversion devversion force-pushed the build/improvements-dev-app-build branch from 53908fc to ae8fbbc Compare November 2, 2021 21:37
@devversion devversion added the dev-app preview When applied, previews of the dev-app are deployed to Firebase label Nov 2, 2021
@github-actions
Copy link

github-actions bot commented Nov 2, 2021

@devversion devversion added merge safe target: patch This PR is targeted for the next patch release labels Nov 2, 2021
@devversion devversion marked this pull request as ready for review November 2, 2021 21:45
@devversion devversion requested a review from a team as a code owner November 2, 2021 21:45
Copy link
Member

@josephperrott josephperrott left a comment

Choose a reason for hiding this comment

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

LGTM

@devversion devversion added the action: merge The PR is ready for merge by the caretaker label Nov 2, 2021
@amysorto amysorto merged commit acd5ee1 into angular:master Nov 4, 2021
amysorto pushed a commit that referenced this pull request Nov 4, 2021
…3875)

This commit fixes that the Github actions currently may cache undesired
files. e.g. when Bazel runs the `dist/` folder is populated and
symlinked with the execroot, where another clone of the `node_modules`
would be cached accidentally then. We use an explicit path instead of a
pattern as it has been recommended by the Github action documentation.

Additionally, we fix that the dev-app building on RBE occurs with 2
concurrent jobs due to the host containers only having 2 cores. We can
run more jobs in the RBE containers.

(cherry picked from commit acd5ee1)
@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 Dec 5, 2021
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 dev-app preview When applied, previews of the dev-app are deployed to Firebase 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