5 Commits

Author	SHA1	Message	Date
Andrey Lushnikov	d58a57c4b2	devops: fix docker publishing (#2939) ... - Repository name has to start with `public/` to be exported to dockerhub. - Remove `DOCKER_USERNAME` to avoid unnecessary masking in our logs. - Publish dev versions of Docker image only when changes to docker file happen. (this is why NPM publishing and Docker publishing for dev releases are now separate). - Release publishing in two separate jobs to make them independent. References #2926	2020-07-13 17:15:10 -07:00
Andrey Lushnikov	b7d68d1cdb	devops: automate Docker image publishing (#2937) ... This starts publishing our Docker images using Github Actions: - on every commit, a new image will be pushed, tagged with a SHA of the commit, e.g. `mcr.microsoft.com/playwright:sha-fe997eca88d6de48378b05133dadfe032bd8b0ea` - on every release, a new image will be pushed, tagged with the release version, e.g. `mcr.microsoft.com/playwright:v1.2.1` **Note:** today we don't version our images and instead push them all as `bionic`. This patch retains the tag - along with `latest`. Both `bionic` and `latest` tags will point to the latest release.	2020-07-13 16:18:51 -07:00
Dmitry Gozman	5c4751d5dd	chore: generate protocol during browser roll (#2719) ... We now commit protocol.ts files during the roll. New utils/roll_browser.js helps with that. This makes our installation very shallow: - build installer; - download browsers.	2020-07-01 15:22:29 -07:00
Andrey Lushnikov	0b7f789de4	devops: try using another Github Actions event to trigger releases (#1931) ... The [official documentation](https://help.github.com/en/actions/language-and-framework-guides/publishing-nodejs-packages#publishing-packages-to-the-npm-registry) suggests using `created` event, but it didn't work for us. As someone mentioned on [github community](https://github.community/t5/GitHub-Actions/Workflow-set-for-on-release-not-triggering-not-showing-up/m-p/53236#M8758), it looks like the `created` event is actually issued when release draft is first created. Try using [`published`](https://help.github.com/en/actions/reference/events-that-trigger-workflows#release-event-release) event instead.	2020-04-22 22:52:32 -07:00
Andrey Lushnikov	0f338eced7	devops: introduce release publishing workflow (#1894) ... This workflow is based on the Github Actions docs: [publishing node.js packages](https://help.github.com/en/actions/language-and-framework-guides/publishing-nodejs-packages) It should be triggered once we create a github release. It's unclear how to test this workflow, so I tried to re-use as much code from `publish_canary.yml` as possible.	2020-04-21 15:10:00 -07:00