The hosted version of travis only uses 32-bit Ubuntu, which is a reasonable baseline target for an open source project. If your production environment is different enough, you would need to run your own CI and not use the hosted version of travis.
I guess my point is "travis-ci should represent the minimal reasonable testing effort" for an open source project you expect others to depend on. If it's not a simple, automated process to get your project installed on something as mainstream as ubuntu, you should fix that. Ted On Oct 11, 2012, at 3:49 PM, Bradley Meck <[email protected]> wrote: > Just beware of Travis CI failing for situations that are beyond your control. > Missing C libraries, OS issues, and external resource needs can all be > problematic. Also I have noted at least in the past sometimes travis fails to > provision VMs appropriately. Running tests in your environment is the best > way to test a module. > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
