Skip to content

build: deploy screenshot functions #4698

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

  • Deploys the screenshot functions for push builds
  • Runs deploying & publishing in parallel

* Deploys the screenshot functions for push builds
* Runs deploying & publishing in parallel
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label May 20, 2017
# before it can collect all functions and deploy them.
(cd tools/screenshot-test/functions; npm install)

if [ -z ${MATERIAL2_SCREENSHOT_ACCESS_TOKEN} ]; then
Copy link
Member

Choose a reason for hiding this comment

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

Created MATERIAL2_SCREENSHOT_FIREBASE_DEPLOY_TOKEN for this

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks!

@@ -30,8 +33,10 @@ publishPackage() {
repoUrl="https://github.com/angular/${packageRepo}.git"
repoDir="tmp/${packageRepo}"

# Create a release of the current repository.
$(npm bin)/gulp ${packageName}:build-release:clean
if [[ ! ${COMMAND_ARGS} == *--no-build* ]]; then
Copy link
Member

Choose a reason for hiding this comment

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

What is this flag needed for?

Copy link
Member Author

@devversion devversion May 22, 2017

Choose a reason for hiding this comment

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

This allows us to decide whether the script itself should build or if we want to build the output before on our own.

This allows us to run publishing & deploying in parallel.

You can still run the script without any flag to build it as usual.

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

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs review labels May 22, 2017
@tinayuangao tinayuangao merged commit ecea23c into angular:master May 22, 2017
@devversion devversion deleted the build/deploy-screenshot-functions branch November 11, 2017 10:20
@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 Sep 7, 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
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants