travis build #1
Merged
travis build #1
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
till
requested changes
Mar 23, 2017
.travis.yml
Outdated
| - pear uninstall xml_util structures_graph archive_tar console_getopt pear | ||
| - which pear | ||
| - ./run-installer.sh | ||
| - find ~ -name pear -print |
There was a problem hiding this comment.
I think everything up until this line should be in an install: target.
There was a problem hiding this comment.
Does that make a difference on how the shell runs them?
There was a problem hiding this comment.
@ashnazg yeah, by not utilizing the targets, Travis-CI will execute its defaults. Needless roundtrips and cycles wasted. That's all! :)
till
approved these changes
Mar 31, 2017
|
@ashnazg I just saw your other questions (sorry for the slow response). Is that still a problem? My guess is that the |
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
run-installer.shscript works for me on Ubuntu Trusty using PHP 5.5 and 5.6. It successfully runs thego-pear.pharinstallation without requiring user input.What I cannot figure out is why Travis appears to run it cleanly, but then doesn't have the PEAR installation available.
Right now, the invocation of the
run-installer.shshould be doing the install. The laterphp go-pear.pharis solely to show you the paths it defaults to, which is presumably where the first invocation should have installed it. Note the build will get stuck here, waiting for user input, so it must be manually canceled or else wait until Travis time-limits the build and kills it.@kenguest , @till , @cweiske , could you guys try out the
run-installer.shscript locally to confirm it works in your environments?More importantly, who could shed some light on why Travis is behaving like it does? I don't understand why the PEAR installation doesn't properly appear in
/home/travis/pear, based on the default pathing shown.