hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-11220) Jenkins should verify "mvn site" if the patch contains *.apt.vm changes
Date Mon, 27 Oct 2014 16:31:35 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-11220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14185328#comment-14185328
] 

Colin Patrick McCabe commented on HADOOP-11220:
-----------------------------------------------

I know it's frustrating when docs build regressions happen, but have you measured how much
time running {{mvn site}} would add to each Jenkins run?  It has to be at least a few minutes,
based on my own experiences.  Docs build issues are also relatively easy to fix... they aren't
the sort of things that hold up a release, although they are obviously annoying.

Perhaps we could just have a nighly {{mvn site}} build that emails the list when breakage
happens?

> Jenkins should verify "mvn site" if the patch contains *.apt.vm changes
> -----------------------------------------------------------------------
>
>                 Key: HADOOP-11220
>                 URL: https://issues.apache.org/jira/browse/HADOOP-11220
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Zhijie Shen
>
> It's should be good to make Jenkins verify "mvn site" if the patch contains *.apt.vm
changes to avoid some obvious build failure, such as YARN-2732.
> It's not the first time that the similar issues have been raised. Having an automative
verification can inform us an alert before us encounter an actual build failure which involves
"site" lifecycle.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message