-
-
Notifications
You must be signed in to change notification settings - Fork 132
Travis improvements #74
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
Changes from all commits
d70ec6e
95b459c
54bf45d
bec5e5a
5f9c697
91ffeb1
f986c56
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -5,9 +5,23 @@ php: | |
- 5.5 | ||
- 5.6 | ||
- 7.0 | ||
- 7.1 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure if we have a consensus here yet. Do we really want to add every single future version for all components? Other than that, LGTM 👍 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'd say yes. Since this is a core component, i think we should run the tests against as much versions as possible. But i agree that this change should have probably been introduced in another PR. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Have re-read this now: I think it makes sense for this component. If this makes sense for all components is arguable. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Personally I would prefer testing all versions we support to ensure we don't run into weird issues. We also might want to use the new cron feature to schedule builds, but that only makes sense with |
||
- hhvm | ||
|
||
install: ./travis-init.sh | ||
sudo: false | ||
|
||
addons: | ||
apt: | ||
packages: | ||
- libevent-dev # Used by 'event' and 'libevent' PHP extensions | ||
|
||
cache: | ||
directories: | ||
- $HOME/.composer/cache/files | ||
|
||
install: | ||
- ./travis-init.sh | ||
- composer install | ||
|
||
script: | ||
- ./vendor/bin/phpunit --coverage-text |
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+
nightly
maybe?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe something we can add in another PR since it would probably introduce
allow_failures
also.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes,
allow_failures
is a good idea fornightly
.