To be exhaustive, we'd also add the various -Drequire options for full inclusion of all optional native components. Unfortunately, that gets tricky because of the various build pre-requisites which would need to be present on the Jenkins hosts. This is where the Dockerfile is helpful, because it encapsulates all of that. Maybe this job would benefit from using the Dockerfile.
--Chris Nauroth On 11/30/15, 3:26 PM, "Andrew Wang" <andrew.w...@cloudera.com> wrote: >I went ahead and turned off JIRA notification for all the "other" jobs I >could find, if you see more than one Hudson email from now on feel free to >ping me or turn it off yourself. The jobs are also still running, just not >JIRA commenting anymore. > >I did also add the native nvn args to Hadoop-trunk-Commit, feel free to >append more stuff as desired. > >On Mon, Nov 30, 2015 at 3:11 PM, Andrew Wang <andrew.w...@cloudera.com> >wrote: > >> >> On Mon, Nov 30, 2015 at 3:04 PM, Allen Wittenauer <a...@altiscale.com> >> wrote: >> >>> >>> > On Nov 30, 2015, at 11:33 AM, Andrew Wang <andrew.w...@cloudera.com> >>> wrote: >>> > >>> > Good point Allen. So I guess the broader question is, do we find the >>> > per-commit tracking build and test useful? With our current flakiness >>> > levels, there isn't much signal from a FAILED on one of these >>> integration >>> > jobs. I think Hadoop-trunk-Commit is still nice as a compilation >>>check. >>> >>> Š except it doesn¹t compile everything ... >>> >>> So I see this in the shell step at the top level: >> >> $MAVEN_HOME/bin/mvn clean install -DskipTests >> >> It's not compiling native code if that was your concern, and I can add >> -Pnative. Anything else to tack on? >>
