Skip to content

[patch port] ci: setup automatic deployment for the docs app #24552

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
merged 2 commits into from
Mar 10, 2022

Conversation

devversion
Copy link
Member

Patch port of #24528

@devversion devversion added the blocked This issue is blocked by some external factor, such as a prerequisite PR label Mar 8, 2022
@devversion devversion force-pushed the patch-port-docs-deployment branch 4 times, most recently from f89c3b6 to 277acaf Compare March 9, 2022 19:52
@devversion devversion added the action: merge The PR is ready for merge by the caretaker label Mar 9, 2022
@devversion devversion force-pushed the patch-port-docs-deployment branch from e17860c to 4930a5c Compare March 9, 2022 21:06
@devversion devversion added target: patch This PR is targeted for the next patch release and removed blocked This issue is blocked by some external factor, such as a prerequisite PR labels Mar 10, 2022
@devversion devversion marked this pull request as ready for review March 10, 2022 15:25
@devversion devversion requested a review from a team as a code owner March 10, 2022 15:25
We currently configure RBE by setting `GOOGLE_APPLICATION_CREDENTIALS`
into the `$BASH_ENV` variable, ensuring RBE is configured everywhere on CI.

This worked nicely but now with automatic docs deployment turned out to
be problematic since it prevents scripts from defining `GOOGLE_APPLICATION_CREDENTIALS`
themselves/overriding it. the reason is that `$BASH_ENV` always runs in new
child processes (like when firebase is initialized) and then overrides the credentials
back to the RBE service key.

We can simplify this code by using a dedicated Bazel flag.
@devversion devversion force-pushed the patch-port-docs-deployment branch from 4930a5c to 40fbdde Compare March 10, 2022 15:29
@zarend zarend merged commit 96b97a3 into angular:13.2.x Mar 10, 2022
@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 Apr 10, 2022
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 target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants