no, the workflow wouldn't be applicable with Jenkins: IMHO, such workflow
should
be published on Mahout website, with svnpubsub and extpaths.txt to avoid
javadoc disappearing on each CMS change
Regards,
Hervé
Le vendredi 16 mai 2014 23:28:59 Martin Desruisseaux a écrit :
> Hello Andrew
>
> T
since every committer can have an authenticated access to Jenkins, this seems
reasonable to me
notice I don't really get what is "the archive artifacts functionality": any
pointer appreciated, and I'll try to add explanations to our Jenkins best
practices [1]
> am going to contact the Maven te
+1
--
Olivier
On May 17, 2014 5:00 AM, "Andrew Bayer" wrote:
> So from https://issues.jenkins-ci.org/browse/JENKINS-23056 it sounds like
> at least one of the problems we're having with Jenkins hanging is because
> of attempts to access the workspace of jobs through the UI - when a slave
> is sl
On Thu, May 15, 2014 at 4:55 PM, Andrew Bayer wrote:
> So from https://issues.jenkins-ci.org/browse/JENKINS-23056 it sounds like at
> least one of the problems we're having with Jenkins hanging is because of
> attempts to access the workspace of jobs through the UI - when a slave is
> slow or hang
Le mercredi 7 mai 2014 11:35:29 Olivier Lamy a écrit :
> Hi Guys,
> I did some upgrade today.
> Align jdk for ubuntu nodes to be the same as the master.
>
> Install the Jenkins monitoring plugin: https://builds.apache.org/monitoring?
FYI, Jenkins admins are the only one who have access to the resu
So from https://issues.jenkins-ci.org/browse/JENKINS-23056 it sounds like
at least one of the problems we're having with Jenkins hanging is because
of attempts to access the workspace of jobs through the UI - when a slave
is slow or hanging and that kind of request is made, it can lock up the
whole
Jobs Killed:
flume-trunk build #634 killed was stuck at over 8 hours.
dir-groovy-ldap-deploy-site build #1241 killed was stuck at over 7 hours.
maven-scm-windows build #117 was stuck at over 9 hours.
NPanday-it-runner build #423 was stuck at 9 hours.
Jobs Killed and Disabled:
--
Hello,
I had a problem on one of my Jenkins job (MINA-trunk-jdk1.7-ubuntu) whose
cause wa related to Maven installation on the slave.
But since, the job is not more scheduled even if new commits have been
pushed to Git (
https://builds.apache.org/job/MINA-trunk-jdk1.7-ubuntu/scmPollLog)
Thanks
Je
Hello Andrew
Thanks for looking at this issue. On my side, I use the javadoc
generated by Jenkins build every days. I often fix formatting issues and
wait for the next Jenkins build for seeing if the fix worked. This is
especially useful in class javadoc having tables, matrices or
mathematical for
Yeah, there's some problem with maven project jobs on some slaves. I'm
investigating.
On May 15, 2014 11:46 PM, "Gavin McDonald" wrote:
> Jobs Killed:
>
>
> flume-trunk build #634 killed was stuck at over 8 hours.
> dir-groovy-ldap-deploy-site build #1241 killed was stuck at ove
Hey Mahout devs -
So as you may know, builds.apache.org has been having a lot of stability
and performance problems lately. It turns out that at least one of the
reasons for that is that it's getting hit with attempts to download files
from job workspaces on slaves, and those slaves aren't always
11 matches
Mail list logo
