Skip to content

build: cronjob to run tests against mdc snapshot builds #16668

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

@devversion devversion commented Aug 2, 2019

Sets up a new cronjob that runs tests against the material-components-web
repository HEAD. This allows us to validate that our MDC components work
properly with upcoming MDC releases.

@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 2, 2019
@devversion devversion force-pushed the build/snapshot-cronjob-mdc-master branch 6 times, most recently from 01730d9 to 846962b Compare August 2, 2019 17:39
@devversion devversion force-pushed the build/snapshot-cronjob-mdc-master branch from 846962b to c387230 Compare August 2, 2019 18:00
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Aug 2, 2019
@devversion devversion marked this pull request as ready for review August 3, 2019 06:02
@devversion devversion requested a review from jelbourn as a code owner August 3, 2019 06:02
@devversion devversion force-pushed the build/snapshot-cronjob-mdc-master branch from c387230 to 5a1fa33 Compare August 7, 2019 09:31
@mmalerba
Copy link
Contributor

mmalerba commented Aug 7, 2019

LGTM, but it might be good if @jelbourn takes a look, I don't really know what I'm looking at 😅

environment:
GCP_DECRYPT_TOKEN: *gcp_decrypt_token
MDC_REPO_URL: "https://github.com/material-components/material-components-web.git"
MDC_REPO_BRANCH: "master"
Copy link
Member

Choose a reason for hiding this comment

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

I found out on Friday that MDC's development HEAD is actually a branch called develop instead of master, so I believe we should test that

cc @abhiomkar

Copy link
Member Author

Choose a reason for hiding this comment

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

Yeah this document describes that develop includes breaking-changes. Though I'm not sure which one we want to pick. It looks like both do not really intersect. e.g. a non-breaking change is not merged into both master and develop (based on my observation on the repo)

name: "Installing dependencies for MDC repository"
# MDC repository does not use Yarn for node dependencies, so in order to respec the
# lock-file we need to use "npm" when installing dependencies.
command: cd ${MDC_REPO_TMP_DIR} && npm install
Copy link
Member

Choose a reason for hiding this comment

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

@abhiomkar have you all considered switching to yarn? We've generally found that the locking mechanism works better (especially WRT remote caching and the bazel stuff we do)

Sets up a new cronjob that runs tests against the `material-components-web`
repository HEAD. This allows us to validate that our MDC components work
properly with upcoming MDC releases.
@devversion devversion force-pushed the build/snapshot-cronjob-mdc-master branch from 5a1fa33 to b29c03f Compare August 14, 2019 12:52
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 labels Aug 20, 2019
@jelbourn jelbourn merged commit 258ca59 into angular:master Aug 20, 2019
andrewseguin pushed a commit that referenced this pull request Aug 26, 2019
Sets up a new cronjob that runs tests against the `material-components-web`
repository HEAD. This allows us to validate that our MDC components work
properly with upcoming MDC releases.

(cherry picked from commit 258ca59)
@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 20, 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.

4 participants