Skip to content

Switch from Travis CI and AppVeyor to GitHub Actions - #1150

Merged
ste93cry merged 5 commits into
masterfrom
php8-support-with-github-actions
Dec 15, 2020
Merged

ste93cry merged 5 commits into
masterfrom
php8-support-with-github-actions

Conversation

@Jean85

@Jean85 Jean85 commented Dec 4, 2020

Copy link
Copy Markdown
Contributor

Includes #1087.

@Jean85 Jean85 added this to the 3.1 milestone Dec 4, 2020
@Jean85 Jean85 self-assigned this Dec 4, 2020
@Jean85
Jean85 marked this pull request as ready for review December 4, 2020 21:54
@Jean85
Jean85 requested a review from ste93cry December 4, 2020 21:54
@Jean85

Jean85 commented Dec 4, 2020 •

Copy link
Copy Markdown
Contributor Author

...and that's why I prefer moving to Github Actions. I got a green build in less than 10 minutes of work, build time included.

We could even migrate the Windows build there too, but I don't want to pollute this PR further.
[EDIT] If we really want, #1151 does the trick.

@Jean85 Jean85 linked an issue Dec 4, 2020 that may be closed by this pull request
@ste93cry

ste93cry commented Dec 4, 2020 •

Copy link
Copy Markdown
Contributor

I have nothing against GitHub Actions, but at the same time I would like to remind that nothing cames for free and at some point in the future it's probable that limitations will be put in place, simply because otherwise it would not be sustainable. I said in the past that I don't agree with moving off from Travis not because I'm tied with it, but mainly because it works well for our use-case like AppVeyor does and to be honest I don't see anything that we could benefit from after the change. Said this, it's undoubtful that Travis is having some issues with getting PHP8 work, although they are working on it. I also see that the build is passing, but just because you changed from Xdebug to PCOV which is less accurate and is less active in the development, so we can say that you worked around the issue rather than solving it. Anyway, subjective opinions aside, I suggest to wait until the next week to see if situation improves on Travis, otherwise let's do the switch to GA and release this long awaited update to support PHP 8. I don't think that neither the weekend nor a few more days of wait will change the life of people

We could even migrate the Windows build there too, but I don't want to pollute this PR further

I would prefer to make the changes in the original PR. Also, please, let's avoid in the future the opening of more PR with the same changes as it makes more difficult for people to follow the development, and code reviews may get splitted among different places

@ste93cry
ste93cry force-pushed the php8-support-with-github-actions branch 6 times, most recently from 510ecdf to 32863f6 Compare December 8, 2020 14:50
@ste93cry

ste93cry commented Dec 8, 2020

Copy link
Copy Markdown
Contributor

Situation on Travis improved as expected and PHP 8 builds are fine, however we hit the OSS credits limit and I honestly didn't expected it at all since we are not a project with a lot of builds. Anyway, in addition to this, since a while AppVeyor builds fail because of rate limiting on Chocolatey (it's so damn low!), so let's make this switch to GitHub Actions to be happy

@HazAT can you please disable both Travis and AppVeyor? For the latter the checks still run despite me deleting the config file

@ste93cry
ste93cry force-pushed the php8-support-with-github-actions branch from 32863f6 to 4446187 Compare December 8, 2020 16:36
@Jean85

Jean85 commented Dec 8, 2020

Copy link
Copy Markdown
Contributor Author

I had permissions on Appveyor, I probably fixed it (but it will stop working on other branches :( )

PHPStan is probably failing due to different function signatures under PHP 8, where they come from core and no longer from the polyfill. Should we switch back to 7.4 for the time being?

@ste93cry

ste93cry commented Dec 8, 2020

Copy link
Copy Markdown
Contributor

but it will stop working on other branches :(

I'm not worried about this, we are going to switch to GitHub actions for all branches of all versions aren't we?

PHPStan is probably failing due to different function signatures under PHP 8, where they come from core and no longer from the polyfill

They look more like regressions or bugs. I opened phpstan/phpstan#4203 to track the issue with the get_include_path function for now

@Jean85

Jean85 commented Dec 9, 2020

Copy link
Copy Markdown
Contributor Author

I've also opened phpstan/phpstan#4205 for the same reason.

Jean85 added a commit that referenced this pull request Dec 9, 2020
Jean85 added a commit that referenced this pull request Dec 9, 2020
Port of #1150 to 2.x

Force PHP 7.4 max in CI

Use Pcov for coverange since Xdebug is interfering with CI

Bump minimum PHPUnit version

Use Pcov and add clobber

Go back to Xdebug but avoid 3.0

Limit symfony/phpunit-bridge to latest version only

Address CR issues
@ste93cry ste93cry changed the title Php8 support with GitHub actions Switch from Travis CI and AppVeyor to GitHub Actions Dec 10, 2020
@ste93cry
ste93cry merged commit 9f734af into master Dec 15, 2020
@ste93cry
ste93cry deleted the php8-support-with-github-actions branch December 15, 2020 17:54
ste93cry added a commit to jarstelfox/sentry-php that referenced this pull request Dec 29, 2020
Co-authored-by: Stefano Arlandini <sarlandini@alice.it>
soundsgoodsofar pushed a commit to soundsgoodsofar/sentry-php that referenced this pull request Jan 8, 2021
Co-authored-by: Stefano Arlandini <sarlandini@alice.it>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PHP 8 Support

2 participants