We are using Collabnet to upload the builds. Here is the info of the
environment -
Jenkins version / 1.457
CollabNet Plugin/1.1.6
/usr/lib/jvm/java-1.6. 0-openjdk-1.6.0.0.x86_64
All the way, at the end of the build while trying to upload the build,
it throws the following exception. Thus
That is correct. It does have the appropriate URL and is a working one.
Thanks
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Darryl Bowler
Sent: Tuesday, May 22, 2012 12:54 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: problems with
After much of woes, found out that domainname\username is not acceptable
within Jenkins environment. Just use username for Collabnet
configuration within Jenkins.
Thanks Darryl.
Regards
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Darryl
Referring to https://issues.jenkins-ci.org/browse/JENKINS-11398, I see the
updates posted by Seiji Sogabe (user name:dogfood) and plugins_cobertura#70
is part of 1.463-SNAPSHOT release
(http://ci.jenkins-ci.org/job/plugins_cobertura/70/).
I would like to know when this fix will be
Not sure if any one else has run into this issue. After disk space
addition, the builds stopped working. 'build now' link is not doing
anything.
Appreicate your input. Is there a best practice that one should be
following while doing such a maintenance work ?
The VM where Jenkins CI is
Thanks Mark for that note.
Just curious – what are the plugins that correspond to the following exceptions
(as well as dependency plugins if any) –
Failed to load
hudson.plugins.cobertura.dashboard.CoverageTablePortlet$DescriptorImpl
java.lang.LinkageError: Failed to resolve class
The VM where Jenkins CI is running, was reaching to a point of disk
space being full. Our Admin decided to increase the disk space. After
that the builds stopped working. Both Build Now link as well as
scheduled builds do not work anymore. Here is the exception details in
the log -
Failed to
I have ftp configured using vsftp in linux x86_64 (vm) environment,
running
Red Hat Enterprise Linux Server release 6.2 (Santiago)
POM.xml as follows -
distributionManagement
repository
idftp-repository/id
Tim, we are using apache-maven/3.0.3 both within and outside of Jenkins.
Is there a plug-in (of a particular version) that I am missing ? Please advise.
Not sure if anyone has run into this problem - why maven goals (configured for
ftp) don’t work from within Jenkins ?
thanks
-Original
Not sure about this strange error suddenly. Nothing has changed. It was
a working system. Now when I submit the build thru Jenkins, it throws
up io exception. It checks out everything from svn repo, builds fine but
then throws up this IO exception. Don't have any idea as to what is
going on. Why
Send to Recipient List is not checked for any trigger.
Include Culprits is checked for Failure trigger. In here Recipient
List is empty.
send to Committers is not checked for any trigger.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent:
Sounds like https://issues.jenkins-ci.org/browse/JENKINS-12421
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Slide
Sent: Wednesday, February 22, 2012 5:34 PM
To: jenkinsci-users@googlegroups.com
Subject: RE: email coming to everyone instead of
12 matches
Mail list logo
