[
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16075484#comment-16075484
]
ASF GitHub Bot commented on METRON-1008:
----------------------------------------
Github user jjmeyer0 commented on the issue:
https://github.com/apache/metron/pull/632
Unfortunately I will have to open a new PR. I squashed my commits when this
PR was closed. Github doesn't allow to reopen PRs when force pushes occur when
the PR is closed. @justinleet and @ottobackwards I'll address your comments on
the new PR.
My apologies, I was not aware of this.
> Migrate Travis build to use Trusty
> ----------------------------------
>
> Key: METRON-1008
> URL: https://issues.apache.org/jira/browse/METRON-1008
> Project: Metron
> Issue Type: Bug
> Reporter: Justin Leet
>
> [~zeo...@gmail.com] pinged someone from Travis while we were working on
> METRON-1004. In addition to confirming that we should be using a VM, it was
> also suggested we move to Trusty. This was briefly looked at in during
> METRON-1004, in particular because it (theoretically) has the correct version
> of compilers installed, so we could avoid the hit of setting that up. It
> blew up on `npm install`, possibly from my own ignorance.
> At minimum we should move to Trusty:
> {code}
> https://docs.travis-ci.com/user/trusty-ci-environment/
> {code}
> Ideally, we do some more thorough investigation of the compiler and see if we
> can cut out that step.
> See:
> https://docs.travis-ci.com/user/trusty-ci-environment/
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
