Test with Travis CI #10
Merged
Conversation
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
Fatal error: Can't use method return value in write context in /Users/derhasi/WebSandboxes/drupal-parse-composer/src/ReleaseInfo.php on line 30
- winmillwill/packagist-bundle was removed due to, massive dependencies running into memory issues in DependencyResolver
- @todo: recreate the test in drupal-packagist
|
Just added the repo to Travis CI: https://travis-ci.org/drupal-composer/drupal-parse-composer Anyone wanna do a quick review on the PR? ;) |
webflo
added a commit
that referenced
this pull request
Jan 21, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I added some files to make testing on Travis CI possible. This branch is successfully implemented on https://travis-ci.org/derhasi/drupal-parse-composer.
Once the PR is merged I would add the original Repository to Travis CI.
Currently the test runs quite long, so this would be some tasks to investigate in a different issue.