Allow --config-path to be specified to ember-try commands. #50
Conversation
This file contains 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
This allows groups of configurations to be used with various commands. For example, it would be nice in ember-test-helpers to group "legacy" Ember versions together and run them as a single matrix build with: ``` ember try:testall --config-path=config/legacy-scenarios.js ``` Then we could run current scenarios in another matrix build like: ``` ember try:testall --config-path=config/current-scenarios.js ```
|
@kategengler - Would love your thoughts here... |
|
Sounds (and looks) good to me, thanks! |
kategengler
added a commit
that referenced
this pull request
Feb 1, 2016
Allow --config-path to be specified to ember-try commands.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This allows groups of configurations to be used with various commands.
For example, it would be nice in ember-test-helpers to group "legacy" Ember versions together and run them as a single matrix build with:
Then we could run current scenarios in another matrix build like: