Unfortunately, it looks like we need to build in order
to be able to lint. This makes sense since some
projects will lint imports from others that haven't
been built yet.
This adds support for using the `pnpm utils ci-jobs` command in our `ci.yml` file. One of the bigger benefits to this change too is that we're now distributing a bundled version of the utils tool. This lets us run it without actually having to install the repo and will let us speed up any workflows that currently do.
* Try sharding e2e tests
* Update reporter for merge
* Add changelog
* Change to trigger CI
* Update job name to match existing run
* Install with dependencies
* Set working directory
* Only run 2 workers at a time on CI
* Try single run, but 6 shards
* Simplify welcome modal closing util helper
* Switch to more simpler way of closing welcome modal
* Fix flakiness in create shipping zone test
* Try 10 shards
* Drop CI retries to 2 from 4
* Update path to reports
* Fix syntax error in GH file
* Remove working directory
* Update directories
* Path again
* Use Allure dir
* Fix merge step
* Install dependencies
* Setup repo in report merge
* Commands to merge reports
* Set working directory
* Update actions
* Name upload artifacts
* Just numbers for shards
* Update matrix
* Need to redeclare env variables
* Update file paths for merge step
* Remove working directory for merge step
* Try absolute paths
* Missed a path
* Put all artifacts in single download folder
* Tweak download action
* Might not have to merge reports
* Fix typo
* Update path for summary report
* Update results paths
* Tweak condition
* Add step to check success of matrix run
* Remove ternary per feedback
---------
Co-authored-by: Jon Lane <jon.lane@automattic.com>
Co-authored-by: Veljko <veljano@yahoo.com>
* Bump pnpm version in the release-code-freeze.yml workflow to fix issue that impeded the creation of new WooCommerce zip packages.
* Update code freeze workflow to automatically get the pnpm version from the root package.json file.
* Improve reusability of the method to retrieve the pnpm version in the Code Freeze workflow.
* First pass at Playwright test migration
* Set working directory
* Remove exec
* Configure the environment before testing
* Remove filter
* Update paths for tests
* Try explicitly stating working-directory
* Change tests directory
* Try running all tests
* Uncommented project
* Update commands to run tests
* Comment out env config
* Uncomment
* Changelog
* Set up multiple test configurations
* Update failing test
* Update paths for artifacts
* Update path to artifacts
* Path to results
* remove unnecessary file
* Skip translation E2E tests
Skipping translation tests until we fix the missing translations issues after we changed the domain to "woocommerce"
* Update the artifacts path
* Fix lint errors
---------
Co-authored-by: Jon Lane <jon.lane@automattic.com>
Co-authored-by: Luigi Teschio <gigitux@gmail.com>
Co-authored-by: Saad Tarhi <saad.trh@gmail.com>
* Migrate Puppeteer test action from Blocks repo
* Update file path
* Use pnpm
* Use npm
* Updates based on feedback
* Comment out paths for testing
* Fix paths with working directory
* Use pnpm
* Fix missing pnpms
* npm instead
* Do use pnpm
* Update command
* Blocks wp-env config
* Update paths, config files
* Run test commands from blocks
* Config update
* Uncomment paths so that e2e checks only run on Blocks
---------
Co-authored-by: Jon Lane <jon.lane@automattic.com>
* Update action for API tests
* Changelog
* Update e2e tests
* Rename WooCommerce Payments to WooPayments
---------
Co-authored-by: Jon Lane <jon.lane@automattic.com>
This makes some adjustments for consistency in style as well as making
improvements to usability and performance. It also updates all of the
pinned hashes to pull in any fixes that have been made.
* Add new workflow to ping Slack every time a certain team is assigned as PR reviewer or tagged in a PR comment.
* Fix workflow after getting feedback from review.
* Fix test-assistant-pr-review workflow so that it also triggers on PR review comments.
* Remove the pull_request trigger from test-assistant-pr-review.yml as it was added only to improve testability.
* Run daily smoke tests on wp-env
* Add changelog
* Add step to install playwright to e2e tests
* Run k6 containers as e2e
* Get build first for k6
* Tweak for API report
* Change k6 tests back to non-local
---------
Co-authored-by: Jon Lane <jon.lane@automattic.com>
* use latest commit of stalebot action, tweak configuration accordingly
* remove stalebot.js
* use default operations per run
---------
Co-authored-by: Ron Rennick <ronald.rennick@automattic.com>
* Increase a couple of timeouts
* Remove duplicate update to nightly
* Add changelog
* Install Playwright
* Handle Playwright setup
* Add in build name
* Add in check in e2e tests for daily run
* Reverse check
* Rookie mistake
* Use ternary operator instead
---------
Co-authored-by: Jon Lane <jon.lane@automattic.com>
* Ensure HPOS is disabled if ENABLE_HPOS is set to '0'
* update spacing and changelog
* log ENABLE_HPOS value for GitHub action
* remove log ENABLE_HPOS value for GitHub action
* updates to HPOS using REST API
* update spacing
* code tidy up
* workflow and global-setup updates after review
* update workflow for api tests
* workflow updates
* delete .github/workflows/pr-build-and-e2e-tests-non-hpos.yml
* update workflow
* update api setup for HPOS
* updates to workflows for api references and setup updates
* add in ENABLE_HPOS check
* update API tests BASE_URL
* updates after review
* update error text
* remove extraneous variable names
* Add changelog
* Add dedicated PW config and global setup files
* Add step to download chromium
* Specify config and env var
* Fix trivial whitespaces
* Disable Slack notif for now
* Re-enable Slack summary
* Simplify getting major, minor version numbers
* Use single line for response wait