Around about 21/06/12 00:36, phil swenson typed ...
I am setting up a new jenkins server and am running into a problem.
when synching my svn repo I get this error on the externals:
Caused by: org.tmatesoft.svn.core.SVNCancelException: svn: E200015: No
credential to try. Authentication failed
Around about 21/06/12 09:03, Neil Bird typed ...
Or it was something along those lines, it was a while ago.
And I forgot what was pertinent: I also had to get the checkout working
properly on the jenkins master's command line as the jenkins daemon user
(cert. acceptance, etc.).
--
[ne
Hello World,
Since yesterday afternoon, Jenkins can no longer connect to the SVN
server (error log see below). It sounds like a cliché, but "we didn't do
anything", at least nothing that we know or remember of.
We tried to restart Jenkins, we tried to restart the SVN server, but
nothing help
Unfortunately I have to stay with this Hudson version. How can I get only
this patch?
On Wednesday, June 20, 2012 6:00:33 PM UTC+2, Andrey Myatlyuk wrote:
>
> Hi!
>
> This issue was resolved in Jenkins version 1.401
>
> What's new in 1.401 (2011/03/13)
>
>- Fix for JENKINS-8711 breaks dep
I guess I didn't explain very well. I am setting up a job on a new
Jenkins server that points to a particular SVN Url. This SVN repo has
several externals. The job runs on one specific node that is in
Germany, but the Jenkins Server and the SVN repo are both in the US
(not sure if that could mat
It seems likely that to resolve the externals, svn needs credentials for
the US instance.
You may be able to resolve this by logging into the o/s as the user which
does the checkout, and doing any checkout from the US svn.
You should be prompted to enter credentials, and svn will cache them in
~/
Hi,
Is there any way to see stats or a graph of numbers of failures per test
across multiple builds?
We have some tests that fail occasionally, maybe one build in 10 or so. I'd
like to see cumulative failure counts for each test over a set of builds,
so that we can target the tests that are fa
Hi all,
One of our nightly builds has started regularly failing due to a hang. It gets
stuck at the very beginning of the job attempting to clean up the workspace.
When look at the console output, it's just got the spinning progress wheel.
The job in question is configured with the "Always chec
Hello,
I am using Jenkins 1.71 with 5 executors.
I have setup a multi job project with about 10 jobs. When I kick off this multi
job, only 2 jobs defined start, rest of the jobs are correctly showed in the
build queue.
After these 2 are done, nothing gets built and build queue is still intact,
I have determined why I could not use the Web interface from other
systems. I did mention that I had the Jenkins service installed on a
windows VM, the problem was that I had the Network connection as NAT. When
I changed it to Bridged, I could use the Web interface to acces the Jenkins
servi
I figured it out. The external was on a different server. Apparently
the svn client that jenkins uses isn't smart enough to apply the
credentials to a different server. The native client/tortoise do
handle this case.
So I had to enter a second svn url for the external and then enter the
credenti
I have compiled 1.389 with just this change for you. You can take it from
here:
https://dl.dropbox.com/u/290671/hudson.war
Or you can build it yourself as well, just take the source from github,
apply the change and build the server.
$ git checkout hudson-1_389
-- apply the change from
https://g
Hi All,
I'm trying to configure Jenkins and ssh/scp plugins to deploy artifacts to
the server using jump box.
Ideally, I'd like Jenkins to read my ssh_config file, I saw some threads
mentioning /var/lib/jenkins/.ssh/config file (RHEL), but I haven't found
proof that Jenkins is really reading that
I am getting frustrated with this and will really appreciate any help
We set up jenkins for our CI environment on Mac OSX for building our xcode
project. Configured everything with SVn so that it syncs and all but when
it comes to build
Code Sign error : There are no valid certificate/private
Considering the frustration it is creating to run Jenkins under the daemon
user, you might consider running it under your user account instead. That may
not be as elegant as running it under the daemon user, but it seems like it
would let you start with an environment where you know the signing
I just installed Jenkins 1.466 and ci-game 1.18. All the other plugins I
installed are more recent than what's listed in the requirements, but every
build says it's worth 0 points and that there were no players. I
configured my job to run all the plugins (mvn install checkstyle:checkstyle
pmd
I hope following gets fixed sooner
https://github.com/dblock/jenkins-ansicolor-plugin/issues/11
B
On Wednesday, June 6, 2012 8:55:44 AM UTC+5:45, Daniel Doubrovkine wrote:
>
> Jenkins AnsiColor 0.3.0, eliminating boring output since its very first
> release is out with some awesome contributio
On 06/22/2012 04:00 AM, RShoemaker wrote:
> I just installed Jenkins 1.466 and ci-game 1.18. All the other
> plugins I installed are more recent than what's listed in the
> requirements, but every build says it's worth 0 points and that there
> were no players. I configured my job to run all the
18 matches
Mail list logo
