Okay, I ve done the 0.23 commit setup.
Builds up and running for common/hdfs and Mapred
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Common-0.23-Commit/
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Hdfs-0.23-Commit/
https://builds.apache.org/view/G-L/view/Hadoop/job/Hadoop-Mapreduce-0.23-Commit/
-Giri
On 10/14/11 12:53 PM, Todd Lipcon wrote:
On Fri, Oct 14, 2011 at 12:39 PM, giridharan kesavan
<gkesa...@hortonworks.com> wrote:
Todd,
I like the idea of setting up commit builds for 23 branch; I can set this
up.
OK. Mind if I manually mvn deploy for now? Some HBase work is blocked on it.
-Todd
On 10/14/11 12:23 PM, Todd Lipcon wrote:
Looks like the Hadoop-*-Commit builds for trunk do a mvn deploy, but
not the 0.23 builds.
It seems we should either (a) add "mvn deploy" to the
Hadoop-*-0.23-Build targets (which run nightly), or (b) add a
cross-project "0.23-commit" build which is triggered on any commit to
0.23 and does a mvn deploy across all the projects, without running
any tests.
Any preferences?
On Fri, Oct 14, 2011 at 12:18 PM, Todd Lipcon<t...@cloudera.com> wrote:
It seems that we're not publishing maven snapshots correctly. I'm not
entirely sure why, but if you look at:
https://repository.apache.org/content/groups/snapshots/org/apache/hadoop/hadoop-common/
you'll see the latest snapshots are from 9/14 or so.
Anyone have any idea what's going on here?
-Todd
--
Todd Lipcon
Software Engineer, Cloudera
--
-Giri
--
-Giri
