Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add PHP 7.0 - 7.3 on Travis CI #35

Closed
wants to merge 4 commits into from
Closed

Add PHP 7.0 - 7.3 on Travis CI #35

wants to merge 4 commits into from

Conversation

sodabrew
Copy link

Also switch distribution from Trusty to Xenial as mentioned here travis-ci/travis-ci#9717 (comment)

@sodabrew
Copy link
Author

Hm, I assumed due to presence of a .travis.yml that https://travis-ci.org/php/pecl-networking-ssh2 would be an active build. Is this something an admin would like to enable? Are you building this code on a different build/test service?

@sodabrew
Copy link
Author

CC @langemeijer @remicollet ☝️

@mhagstrand
Copy link
Contributor

I added the .travis.yml a while back in this PR: #25. I was hoping it would get enabled. I figured it would make development a little easier.

@sodabrew
Copy link
Author

@langemeijer merged the Travis CI config file but didn't enable Travis CI for the repo, which isn't a useful combination. Strongly request enabling the service.

@nikic nikic closed this Jan 2, 2019
@nikic nikic reopened this Jan 2, 2019
@nikic
Copy link
Member

nikic commented Jan 2, 2019

I've enabled Travis for this repository. Will leave merging this to a maintainer...

@sodabrew
Copy link
Author

sodabrew commented Jan 2, 2019

Tests passing on all versions of PHP 7.x!

.travis.yml Outdated
@@ -1,8 +1,11 @@
sudo: required

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- sudo: required

Travis is deprecating the sudo keyword and moves everything to the same infrastructure (sudo really selects between two infrastructures).

See: https://blog.travis-ci.com/2018-11-19-required-linux-infrastructure-migration

@@ -1,8 +1,11 @@
sudo: required
dist: trusty
dist: xenial

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

- dist: xenial

I think you can remove dist at all

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The default is still trusty.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

xenial has no 7.3 support on travis https://docs.travis-ci.com/user/reference/xenial/#php-support

So it should switch to bionic and drop 7.0 https://docs.travis-ci.com/user/reference/bionic/#php-support

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you can use different dist per versions. this example uses different dist for 5.3:

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

however, you linked doc says:

The following PHP versions are preinstalled

it doesn't mean the other versions are not supported, they just are downloaded on demand. at least I've seen downloading x.y version messages in build logs.

@andypost
Copy link
Contributor

Is there a way to create new release? Trying to package extension to Alpinelinux without success alpinelinux/aports#6226

@frederikbosch
Copy link

I would also be interested in a new release. Is there anything anyone, including myself, can do to make it happen?

@andypost
Copy link
Contributor

And it still require #36 for 7.3 compatibility

@glensc
Copy link

glensc commented Aug 16, 2019

btw, can someone update pecl Homepage property to point to this repo instead of libssh2 homepage?

@glensc
Copy link

glensc commented Aug 16, 2019

also, can someone push tags for created releases? so far only some legacy tags are present:

  • RELEASE_0_4
  • RELEASE_0_4_1
  • RELEASE_0_5
  • RELEASE_0_6
  • RELEASE_0_7
  • RELEASE_0_8
  • RELEASE_0_9
  • RELEASE_0_10
  • RELEASE_0_11_0
  • RELEASE_0_11_1
  • RELEASE_0_11_2
  • RELEASE_0_11_3
  • RELEASE_0_12
  • RELEASE_1_0_4

if needed I can dig up the commit hashes for someone to create lightweight tags.

as I'm trying to build this for php 7.3, and apparently applying only #36 is not enough, and not known what is the baseline from the last release as git tags are missing from the repository.

Copy link
Contributor

@andypost andypost left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Already merged as #36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants