Opened 4 years ago
Closed 17 months ago
#52615 closed enhancement (maybelater)
Squash.io integration?
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | normal | |
| Severity: | normal | Version: | |
| Component: | Build/Test Tools | Keywords: | |
| Focuses: | Cc: |
Description
Hello WordPress Community!
I'm with Squash.io and we wanted to support the WordPress project by providing on-demand test environments for each Pull Request (i.e: a complete staging environment for each branch of code, running your full stack). Our service is free for Open Source projects like WordPress and we would be able to increase our standard limits as needed to provide great user experience for WordPress developers and contributors.
Here is how it works, you push a branch of code, create a Pull Request (for instance, in your GitHub project https://github.com/WordPress/wordpress-develop) and Squash automatically posts a comment with a unique URL where you can test the branch changes in isolation (it usually takes just a few minutes for an environment to spin up):
Squash can also spin up a new environment for each commit within a PR, and give you a pass or fail if it can receive a success HTTP response. You can also run any existing front-end tests (Selenium, TestCafe, etc.) on top of this Squash environment.
Squash setup
Let me know if you like the idea of using Squash on this project. If so, we would be happy to attach a Squash YAML for WordPress file so you don't have to invest any time on this.
Trac integration
We can also explore a native Trac integration if that interests you, just let me know.
Hi @emiquelito,
Welcome to Trac! Apologies that this took so long to receive a response, and thank you for offering to help set this up for use with WordPress.
As much as possible, the project tries to lean on open source solutions. Even if you and other Squash.io team members offer to help implement this service, we still have to consider the long term implications of adding an integration for a new external service.
At this time, I personally feel that the WordPress Playground project is a better tool for the overall community to use for testing proposed changes. There are many additional applications for that project that are relevant to the community and benefit greatly from more usage and testing.
As a Build/Test Tool component maintainer and someone who performs a good amount of the required maintenance for the project's current tools month to month, I'm going to close this request out as
maybelater. However, discussion can always continue on a closed ticket and it can be reopened in the future should factors change. Additionally, if there are any issues that you encounter making it difficult to implement WordPress test environments for any of your customers, those can definitely be evaluated on a case by case basis.