Opened 4 years ago
Closed 4 years ago
#8501 closed defect (bug) (fixed)
Remove Travis and update Unit test GH action
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 10.0.0 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Build/Test Tools | Keywords: | has-patch |
Cc: |
Description
Travis-ci.org is now ended. Builds are no more run there, migrating to Travis-ci.com is required. My experience with 2 of my open source plugins with .com wasn't great: after a bunch of builds the service stopped asking me to pay 69$ per month. But I must say that 4 months after I contacted their support team arguing my repository were open source ones they finally replied saying they gave me free credits for their services. I haven't checked if this was true since I removed my Travis-CI.com personal account & the Travis CI authorization on my GitHub account after waiting for a reply for 2 months.
Now that we have a unit tests GH action, doing this migration might not be needed. GitHub is directly free, you don't need to request free credits and wait 4 months or less to get them.
I'm personally more in favor of improving our GH actions (adding new ones) than migrating to Travis-ci.com. That's why the patch is removing the Travis config and tasks. @johnjamesjacoby what's your opinion about it?
About our unit tests GH Action, now that WordPress has created the 5.8 branch, we need to update it (this is also in the attached patch).
Attachments (1)
Change History (8)
#3
@
4 years ago
- Keywords dev-feedback removed
- Resolution fixed deleted
- Status changed from closed to reopened
It looks like wp-env is using WP tags instead of WP branches. The 5.8 tag is not released yet, which explains why the tests are failing. I'm going to edit back the GH action so that it uses 5.7 until 5.8 is released (~ July 20).
We'll need to update it again soon ;)
GitHub actions seems like the way to go. 👍