Skip to content
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

feat: setup continuous deployment #1159

Merged
merged 2 commits into from
Feb 28, 2020

Conversation

aslushnikov
Copy link
Collaborator

@aslushnikov aslushnikov commented Feb 28, 2020

This patch sets continuous deployment of playwright packages
from tip-of-tree. These packages are released under the "@next",
so it should be possible to install tip-of-tree version of Playwright
from NPM using

npm i playwright@next

A few technical details:

  • This uses travis to drive deployments
  • This deploys from master and only if all browsers pass all tests on linux
  • This is an attempt to deploy just two packages: playwright-core and playwright-firefox. If this works out, I'll follow-up with other packages as well

This patch sets continuous deployment of playwright packages
from tip-of-tree. These packages are released under the "@next",
so it should be possible to install tip-of-tree version of Playwright
from NPM using

```
npm i playwright@next
```
@aslushnikov aslushnikov merged commit 9b51feb into microsoft:master Feb 28, 2020
@aslushnikov aslushnikov deleted the continuous-deployment branch February 28, 2020 19:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant