I think it would be good to incitate all the frameworks and projects using
Travis CI to add nightly to their testing matrix so as to catch bugs in the
upcoming PHP 7 version by testing real code and also so as to have as much
real code as possible getting ready for PHP 7.
I think this is an excellent idea. This is something that will benefit the
internals greatly for catching rogue bugs that pop up in obsecure applications
running in the wild and lower that barrier many people have when attempting to
test development builds.
It would also mean that PHP officially endorses travis.
I don't think it would be seen like this - many tools and frameworks are using
Travis CI and not all of them are seen as an endorsement.
One thing I would like to see is on a successful build, that we store that build
artifact somewhere within the PHP.net infrastructure and allow Travis CI (or
adventerous people in user land) benefit from having a nightly snapshot. Travis
CI generously host it within their S3 bucket at the moment however it would be
good to help out if we can.
On Thu, 26 Feb 2015, Pascal Chevrel wrote:
Le 25/02/2015 23:25, Florian Margaine a écrit :
Hi,
Pascal Chevrel <pascal.chevrel@free.fr> writes:
Hi people,
I hope this is not too much off topic but I saw today that Travis now
supports nightly builds as a possible PHP version, they documented it here:
http://docs.travis-ci.com/user/languages/php/#PHP-nightly-builds
I think it would be good to incitate all the frameworks and projects
using Travis CI to add nightly to their testing matrix so as to catch
bugs in the upcoming PHP 7 version by testing real code and also so as
to have as much real code as possible getting ready for PHP 7.
It would also mean that PHP officially endorses travis.
Hi Florian,
What would be the problem for PHP.net to say that Travis CI, which is free for all open source projects, allows developpers to run their integration tests on Nightly builds?
The PHP source itself runs tests on Travis (https://github.com/php/php-src/blob/master/.travis.yml), that's already as official an endorsement as it can be :D
To be honest, I don't see what endorsing problem there is in asking PHP projects already on travis to add PHP 7 to their testing matrix, it's a great opportunity for getting feedback, improving real codebases to be PHP 7 compatible before PHP 7 is release and actually growing momentum about the upcoming release.
HHVM weren't more than happy to announce Travis support for them when it happened in 2013:
http://hhvm.com/blog/2393/hhvm-2-3-0-and-travis-ci
Here are a few prominent project travis.yml file:
https://github.com/zendframework/zf2/blob/master/.travis.yml
https://github.com/symfony/symfony/blob/2.7/.travis.yml
https://github.com/sebastianbergmann/phpunit/blob/master/.travis.yml
https://github.com/atoum/atoum/blob/master/.travis.yml
https://github.com/composer/composer/blob/master/.travis.yml
What do they all have in common? They test that they work on hhvm and/or hhvm-nightly but not on the upcoming php 7.
Cheers,
Pascal
-- PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php