-
Notifications
You must be signed in to change notification settings - Fork 50
Reduced the number of travis builds. #149
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
Merged
Merged
Changes from 4 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
2e00824
Reduced the number of travis builds.
Nyholm a5e90fd
Syntax fix
Nyholm a530f76
Update .travis.yml
Nyholm 339b82c
Be clearer in Travis GUI
Nyholm 5176010
updated according to feedback
Nyholm 145e754
Add tests for sf 3.1
Nyholm ca2dd68
Re lved
Nyholm 32b6f43
Use the symfony phpunit bridge
Nyholm de5fd63
Added missing deps
Nyholm d9b5985
Use strings instead of constants
Nyholm d52663f
Added legacy annotation
Nyholm 55c9f81
Merge branch 'master' into Nyholm-patch-1
Nyholm 23a64a6
merge fix
Nyholm 01fc201
Fix
Nyholm e076a32
Require finder
Nyholm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think I would by default not enforce any Symfony version at all. And by the way, 2.8 should be handled fine by the job using the
--prefer-lowest
flag.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.
We have to do one by default. Otherwise
composer require symfony/symfony:
will fail, right?I used 2.8 because it is the only LTS we support.
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.
Oh well, I would run
composer require symfony/symfony
only if$SYMFONY_VERSION
is defined and not empty.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.
okey, but that would be the same as setting
SYMFONY_VERSION=3.2.*
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.
I would maybe also set
minimum-stability
in thecomposer.json
file todev
so that you would get a build with the latest Symfony development version for free ("normal" builds could use the--prefer-stable
flag).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.
Testing against Symfony 3.3 would be nice. We just have to allow it to fail.
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.
@Nyholm it is not the same than setting
SYMFONY_VERSION=3.2.*
:My own rule for the Travis matrix is this one:
With such config, I only need to change the build matrix when the list of supported LTS versions is changing (every 2 years)
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.
See https://github.com/Incenteev/IncenteevTranslationCheckerBundle/blob/169c90a9bfc9c7475883521a0edfee30c1c141a0/.travis.yml for an example of such setup (with too much supported PHP versions)
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.
I like the approach @stof recommends.