I'm trying to debug an issue with one of Mahout's builds. Is there a way I can
get access to
/zonestorage/hudson_solaris/home/hudson/hudson-slave/workspace/Mahout-Quality/ ?
Thanks,
Grant
Do we have any convention/policy on how long a job can run before it's killed,
so as to play nice with others? I've got some long running tests that I want
to run once a week on Saturday morning (early, US time).For now they would
be on the main build servers, since Mahout doesn't have it's
Can you kick it again? Seems to have gotten stuck again.
On May 8, 2011, at 10:38 AM, Niklas Gustavsson wrote:
> On Sat, May 7, 2011 at 6:42 PM, Uwe Schindler wrote:
>> Any ideas what's wrong?
>
> Not really. But the node has been restarted now.
>
> /niklas
I started a Wiki page on this at: http://wiki.apache.org/general/PreCommitBuilds
On May 17, 2011, at 1:15 AM, Nigel Daley wrote:
> It was just temporarily disabled while we worked out some changes. It's back
> on now.
>
> Cheers,
> Nige
>
> On May 16, 2011, at 2:55
I'm going to set up the Hadoop patch stuff for Lucene and thought I would
document it somewhere. Should I just use the General ASF wiki or does Builds
have a specific space for documentation?
-Grant
mmit-MAPREDUCE-Build/
> https://builds.apache.org/hudson/job/PreCommit-HDFS-Build/
>
> Let me know if you have questions or can't see these job configs.
>
> Cheers,
> Nige
>
> On Mar 30, 2011, at 8:37 AM, Grant Ingersoll wrote:
>
>> Over in Lucene, we interested in
Over in Lucene, we interested in setting up a patch testing framework for
Lucene similar to what Hadoop does. That is, when a new patch comes in, we
would like to apply it to the trunk, test it and check it if it meets our
requirements and then post a comment on the JIRA issue giving it a preli
Over in Lucene, we interested in setting up a patch testing framework for
Lucene similar to what Hadoop does. That is, when a new patch comes in, we
would like to apply it to the trunk, test it and check it if it meets our
requirements and then post a comment on the JIRA issue giving it a preli
On Feb 23, 2010, at 4:35 PM, Kristian Waagan wrote:
> Den 23.02.2010 18:50, skrev Grant Ingersoll:
>> I'm a bit confused why Derby is using the Lucene Zone to begin with.
>> Doesn't Derby have it's own Zone? I don't necessarily have a problem with
>&g
I'm a bit confused why Derby is using the Lucene Zone to begin with. Doesn't
Derby have it's own Zone? I don't necessarily have a problem with it, but it
would be nice if the Lucene PMC was asked before our resources are utilized.
I'm sure it was just assumed b/c the Lucene Zone shows up in H
The Lucene PMC would like Uwe Schindler (vote occurred on priv...@l.a.o) to be
given a Hudson account so that he may support the Lucene project there. Uwe is
a longtime committer but not yet on the Lucene PMC, but he is experienced with
Hudson.
Uwe's Apache account id is uschindler
Thanks,
G
On Jan 27, 2010, at 1:45 PM, Uwe Schindler wrote:
> Hi Grant,
>
> that would be an option, but during our work, Mike and me only activated the
> "start new build" button in the GUI, everything else was and had to be done
> in the shell:
> - Updating lucene's private SVN tools for the new lucen
Perhaps there is an in-between here, too. Can't we give access to Hudson
itself w/o giving access to the machine? That way, Uwe could run and configure
the jobs (which is the most common task) w/o necessarily needing to deal w/ the
machine level stuff.
-Grant
On Jan 27, 2010, at 11:04 AM, Ti
Per https://issues.apache.org/jira/browse/INFRA-2326, is it possible for a PMC
to designate committers who are allowed hudson access?
14 matches
Mail list logo
