[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087265#comment-16087265
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user asfgit closed the pull request at:

https://github.com/apache/metron/pull/633


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087257#comment-16087257
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user ottobackwards commented on the issue:

https://github.com/apache/metron/pull/633
  
+1


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16087239#comment-16087239
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/633
  
@ottobackwards Do you have any objections to the current state of the PR?  
At this point, I think this is a pretty focused, incremental change.  I'm +1 on 
it, but I want to make sure you have a chance to chime in.


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075499#comment-16075499
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user jjmeyer0 commented on the issue:

https://github.com/apache/metron/pull/633
  
Quote from @justinleet 
> I'd be inclined towards avoiding splitting the build if we were only 
getting a couple minutes out of it. I'm a little worried about being able to 
get three slots on the occasionally stretched Apache setup. Integration tests 
and building are the long poles in the tent, so splitting out the other tests 
doesn't really save us much time here, unfortunately.

I agree, I have reverted this.



Quote from @ottobackwards 
> I'm going to be honest. Now that we have the builds kind of working 
again, I'm a little hesitant to change them for anything but an absolute 
certainty of a return, that we completely understand.
> 
> I think the travis build strategy should be a longer living branch maybe.

I reverted the multiple env changes, as I agree, it's not worth the small 
chunk of time that was shaved off. However, I think the rest of these changes 
can be helpful for the following reasons:

* moving the license verification to an earlier step can help the build 
fail fast. Forgetting to update the dependency file can be a common mistake. 
Failing earlier might save time and travis resources.
* I believe moving to trusty was recommended by travis-ci
* using travis' install step for the `mvn install`. No benefit that I know 
of. I just believe `mvn install` should happen here.




> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075368#comment-16075368
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user jjmeyer0 closed the pull request at:

https://github.com/apache/metron/pull/632


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075359#comment-16075359
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/632
  
@JonZeolla ahh, I thought you were just making a note, so everyone knew 
that recommendation.  Sorry about that.


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075352#comment-16075352
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user jjmeyer0 commented on the issue:

https://github.com/apache/metron/pull/632
  
@JonZeolla that was a squashed commit that was probably a typo. I'll remove 
it.


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075353#comment-16075353
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user ottobackwards commented on the issue:

https://github.com/apache/metron/pull/632
  
I'm going to be honest.  Now that we have the builds kind of working again, 
I'm a little hesitant to change them for anything but an absolute certainty of 
a return, that we completely understand.

I think the travis build strategy should be a longer living branch maybe.


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075346#comment-16075346
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user JonZeolla commented on the issue:

https://github.com/apache/metron/pull/632
  
I was addressing "Testing sudo as false." In the body of the message above.


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075337#comment-16075337
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/632
  
I'd be inclined towards avoiding splitting the build if we were only 
getting a couple minutes out of it.  I'm a little worried about being able to 
get three slots on the occasionally stretched Apache setup.  Integration tests 
and building are the long poles in the tent, so splitting out the other tests 
doesn't really save us much time here, unfortunately.


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075328#comment-16075328
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user justinleet commented on the issue:

https://github.com/apache/metron/pull/632
  
@JonZeolla Completely counterintuitively, `sudo: required` is the 
counterpart of `sudo: false`.  So this already got taken care of as part of 
METRON-1004.  See: https://docs.travis-ci.com/user/trusty-ci-environment.

If you check out the Travis build 
(https://travis-ci.org/apache/metron/jobs/250503026, for example), it says it's 
running the Trusty as expected.


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075322#comment-16075322
 ] 

ASF GitHub Bot commented on METRON-1008:


GitHub user jjmeyer0 reopened a pull request:

https://github.com/apache/metron/pull/632

METRON-1008: Updating travis to use trusty

….npm to cache.

Added some more cacheing from 1004 ticket.

Revert some changes.

Reverted environment and put maven opts in the correct spot.

Testing sudo as false.

Trying multiple vm build.

Revert back to two threads on maven install.

## Contributor Comments
I made travis use trusty. On top of this the following were added before 
1004 was made, but I thought some things were worth keeping:

* Call to verify license is made right away to get quicker failures. 
* Cache $HOME/.npm; After bringing in METRON-1004 it looks like this may 
not be needed anymore?
* Set MAVEN_OPTS to set `-Xmx2g` out of curiosity
* Out of curiosity, multiple environments were added to see if build times 
would dramatically increase. I know this may be undesirable, but I thought I'd 
leave it in to discuss some. I'm leaning towards reverting this back as it only 
seems to get it down to ~23 minutes. Any thoughts?


## Pull Request Checklist

Thank you for submitting a contribution to Apache Metron.  
Please refer to our [Development 
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
 for the complete guide to follow for contributions.  
Please refer also to our [Build Verification 
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
 for complete smoke testing guides.  


In order to streamline the review of the contribution we ask you follow 
these guidelines and ask you to double check the following:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? If not one needs to 
be created at [Metron 
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
 
- [ ] Does your PR title start with METRON- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?


### For code changes:
- [ ] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
- [ ] Have you included steps or a guide to how the change may be verified 
and tested manually?
- [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root incubating-metron folder via:
  ```
  mvn -q clean integration-test install && build_utils/verify_licenses.sh 
  ```

- [ ] Have you written or updated unit tests and or integration tests to 
verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered by building and verifying the site-book? If not then run 
the following commands and the verify changes via 
`site-book/target/site/index.html`:

  ```
  cd site-book
  mvn site
  ```

 Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up 
for your personal repository such that your branches are built there before 
submitting a pull request.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jjmeyer0/incubator-metron METRON-1008

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/metron/pull/632.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #632


commit cc9f234fd51493684767c854fc52d0fba7856496
Author: JJ 
Date:   2017-06-29T22:43:58Z

METRON-1008: Updating travis to use trusty, increase heap, and added .npm 
to cache.

Added some more cacheing from 1004 ticket.

Revert some changes.

Reverted environment and put maven opts in the correct spot.

Testing sudo as false.

Trying multiple vm build.

Revert 

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075288#comment-16075288
 ] 

ASF GitHub Bot commented on METRON-1008:


Github user jjmeyer0 closed the pull request at:

https://github.com/apache/metron/pull/632


> 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)

[jira] [Commented] (METRON-1008) Migrate Travis build to use Trusty

[ASF GitHub Bot (JIRA)]

[ 
https://issues.apache.org/jira/browse/METRON-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16075280#comment-16075280
 ] 

ASF GitHub Bot commented on METRON-1008:


GitHub user jjmeyer0 opened a pull request:

https://github.com/apache/metron/pull/632

METRON-1008: Updating travis to use trusty

….npm to cache.

Added some more cacheing from 1004 ticket.

Revert some changes.

Reverted environment and put maven opts in the correct spot.

Testing sudo as false.

Trying multiple vm build.

Revert back to two threads on maven install.

## Contributor Comments
I made travis use trusty. On top of this the following were added before 
1004 was made, but I thought some things were worth keeping:

* Call to verify license is made right away to get quicker failures. 
* Cache $HOME/.npm; After bringing in METRON-1004 it looks like this may 
not be needed anymore?
* Set MAVEN_OPTS to set `-Xmx2g` out of curiosity
* Out of curiosity, multiple environments were added to see if build times 
would dramatically increase. I know this may be undesirable, but I thought I'd 
leave it in to discuss some. I'm leaning towards reverting this back as it only 
seems to get it down to ~23 minutes. Any thoughts?


## Pull Request Checklist

Thank you for submitting a contribution to Apache Metron.  
Please refer to our [Development 
Guidelines](https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=61332235)
 for the complete guide to follow for contributions.  
Please refer also to our [Build Verification 
Guidelines](https://cwiki.apache.org/confluence/display/METRON/Verifying+Builds?show-miniview)
 for complete smoke testing guides.  


In order to streamline the review of the contribution we ask you follow 
these guidelines and ask you to double check the following:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? If not one needs to 
be created at [Metron 
Jira](https://issues.apache.org/jira/browse/METRON/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel).
 
- [ ] Does your PR title start with METRON- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.
- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?


### For code changes:
- [ ] Have you included steps to reproduce the behavior or problem that is 
being changed or addressed?
- [ ] Have you included steps or a guide to how the change may be verified 
and tested manually?
- [ ] Have you ensured that the full suite of tests and checks have been 
executed in the root incubating-metron folder via:
  ```
  mvn -q clean integration-test install && build_utils/verify_licenses.sh 
  ```

- [ ] Have you written or updated unit tests and or integration tests to 
verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] Have you verified the basic functionality of the build by building 
and running locally with Vagrant full-dev environment or the equivalent?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered by building and verifying the site-book? If not then run 
the following commands and the verify changes via 
`site-book/target/site/index.html`:

  ```
  cd site-book
  mvn site
  ```

 Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.
It is also recommended that [travis-ci](https://travis-ci.org) is set up 
for your personal repository such that your branches are built there before 
submitting a pull request.



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/jjmeyer0/incubator-metron METRON-1008

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/metron/pull/632.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #632


commit cc9f234fd51493684767c854fc52d0fba7856496
Author: JJ 
Date:   2017-06-29T22:43:58Z

METRON-1008: Updating travis to use trusty, increase heap, and added .npm 
to cache.

Added some more cacheing from 1004 ticket.

Revert some changes.

Reverted environment and put maven opts in the correct spot.

Testing sudo as false.

Trying multiple vm build.

Revert