RE: Cannot find parent pom, but it IS there

[Jeff]

The parent POM need not be in the path at all...if the relative path is not
specified and there is no parent POM in the immediate parent (../) folder,
maven will download it just like any other dependency.  The parent version
also need not be related to the child project version at all.

I currently treat my Parent POM as a separate project and version/release
it independently from my 25 other projects.
On Aug 6, 2012 8:22 PM, "Russ Tremain"  wrote:

> well probably what I would do is eliminate jenkins from the mix entirely.
>
> create a tiny pom that references the parent.
>
> then run it on the same machine that jenkins is running on.
>
> does it work?
>
> if so diff it against the pom that is not working.
>
> is it the same?
>
> hard to believe it is a jenkins issue, but I generally avoid the direct
> execution route for maven - I wrap a shell script around it.
>
> sometimes the parent references can be tricky.  the name and version
> elements have to agree exactly.
>
> I usually am referencing these poms with a relative path .. and I don't
> use snapshots for them.  as an example:
>
>
>  
> 
> 
> build-common-dao
> com.iii
> 640.0.0
> ../../../../build-common/dao
> 
>
> I have had instances where the path is correct but the name is wrong, and
> then it balks.
>
> If you are worried about maven updating to snapshots, remove the artifact
> in your local build repository (~/.m2/repository is the default) and force
> it to load again.
>
> good luck!
>
> /r
>
>
>
> At 3:11 PM -0400 8/3/12,  wrote:
> > > this is more of a maven question, I think.
> >>
> >> Try turning -X on in the maven job to find out where it is looking.
> >>
> >
> >Thanks.  I've already done that though.  The output is below.  Note, the
> remote repository where it claims to be looking does indeed hold the
> artifact.  Moreover, other projects on the same build server can access it
> there.
> >
> >It may very well be a maven problem, but how do I fix it.  I'm using a
> private maven repository for the build, as are the others that can
> successfully retrieve the artifact.  From what I understand, I would
> suspect a maven caching issue, but the -U is supposed to resolve that, as
> far as I know.
> >
> >
> >ERROR: Failed to parse POMs
> >org.apache.maven.project.ProjectBuildingException: Cannot find parent:
> com.my.group:project-pom for project:
> com.my.group.service.common:common:pom:1.1.0-SNAPSHOT for project
> com.my.group.service.common:common:pom:1.1.0-SNAPSHOT
> >   at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370)
> >   at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821)
> >   at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
> >   at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:215)
> >   at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:332)
> >   at
> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:871)
> >   at
> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:794)
> >   at hudson.FilePath.act(FilePath.java:753)
> >   at hudson.FilePath.act(FilePath.java:735)
> >   at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:534)
> >   at
> hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:420)
> >   at
> hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
> >   at hudson.model.Run.run(Run.java:1257)
> >   at
> hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306)
> >   at
> hudson.model.ResourceController.execute(ResourceController.java:88)
> >   at hudson.model.Executor.run(Executor.java:127)
> >Caused by: org.apache.maven.project.ProjectBuildingException: POM
> 'com.my.group:project-pom' not found in repository: Unable to download the
> artifact from any repository
> >
> >  com.my.group:project-pom:pom:1.1.0-SNAPSHOT
> >
> >from the specified remote repositories:
> >  nexus (http://myNexus.com:8081/nexus/content/groups/public)
> > for project com.my.group:project-pom
> >   at
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:603)
> >   at
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1366)
> >   ... 15 more
> >Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException:
> Unable to download the artifact from any repository
> >
> >  com.my.group:project-pom:pom:1.1.0-SNAPSHOT
> >
> >from the specified remote repositories:
> >  nexus (http://myNexus.com:8081/nexus/content/groups/public)
> >
> >   at
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212)
> >  

RE: Cannot find parent pom, but it IS there

[Russ Tremain]

well probably what I would do is eliminate jenkins from the mix entirely.

create a tiny pom that references the parent.

then run it on the same machine that jenkins is running on.

does it work?

if so diff it against the pom that is not working.

is it the same?

hard to believe it is a jenkins issue, but I generally avoid the direct 
execution route for maven - I wrap a shell script around it.

sometimes the parent references can be tricky.  the name and version elements 
have to agree exactly.

I usually am referencing these poms with a relative path .. and I don't use 
snapshots for them.  as an example:


 


build-common-dao
com.iii
640.0.0
../../../../build-common/dao


I have had instances where the path is correct but the name is wrong, and then 
it balks.

If you are worried about maven updating to snapshots, remove the artifact in 
your local build repository (~/.m2/repository is the default) and force it to 
load again.

good luck!

/r



At 3:11 PM -0400 8/3/12,  wrote:
> > this is more of a maven question, I think.
>>
>> Try turning -X on in the maven job to find out where it is looking.
>>
>
>Thanks.  I've already done that though.  The output is below.  Note, the 
>remote repository where it claims to be looking does indeed hold the artifact. 
> Moreover, other projects on the same build server can access it there. 
>
>It may very well be a maven problem, but how do I fix it.  I'm using a private 
>maven repository for the build, as are the others that can successfully 
>retrieve the artifact.  From what I understand, I would suspect a maven 
>caching issue, but the -U is supposed to resolve that, as far as I know. 
>
>
>ERROR: Failed to parse POMs
>org.apache.maven.project.ProjectBuildingException: Cannot find parent: 
>com.my.group:project-pom for project: 
>com.my.group.service.common:common:pom:1.1.0-SNAPSHOT for project 
>com.my.group.service.common:common:pom:1.1.0-SNAPSHOT
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:215)
>   at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:332)
>   at 
> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:871)
>   at 
> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:794)
>   at hudson.FilePath.act(FilePath.java:753)
>   at hudson.FilePath.act(FilePath.java:735)
>   at 
> hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:534)
>   at 
> hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:420)
>   at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
>   at hudson.model.Run.run(Run.java:1257)
>   at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306)
>   at hudson.model.ResourceController.execute(ResourceController.java:88)
>   at hudson.model.Executor.run(Executor.java:127)
>Caused by: org.apache.maven.project.ProjectBuildingException: POM 
>'com.my.group:project-pom' not found in repository: Unable to download the 
>artifact from any repository
>
>  com.my.group:project-pom:pom:1.1.0-SNAPSHOT
>
>from the specified remote repositories:
>  nexus (http://myNexus.com:8081/nexus/content/groups/public)
> for project com.my.group:project-pom
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:603)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1366)
>   ... 15 more
>Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: 
>Unable to download the artifact from any repository
>
>  com.my.group:project-pom:pom:1.1.0-SNAPSHOT
>
>from the specified remote repositories:
>  nexus (http://myNexus.com:8081/nexus/content/groups/public)
>
>   at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212)
>   at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74)
>   at 
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:556)
>   ... 16 more
>Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
>download the artifact from any repository
>   at 
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:331)
>   at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200)
>   ... 18

Re: miss changelist number in email-ext plug-in with Perforce

[Slide]

I think he wants to format it similar to how the other items format it
(HTML formatting, etc) not just a direct dump of the changelist.

On Mon, Aug 6, 2012 at 4:40 PM, Rob Petti  wrote:
> P4_CHANGELIST is the environment variable name, so reference it using the
> env token macro.
>
> ${env,var="P4_CHANGELIST"}
>
>
> On Thursday, 2 August 2012 19:36:55 UTC-6, michael chiu wrote:
>>
>> Yes  , I already have my template but if I dont know how to know the
>> property about changelist number in perforce change set? Where can I find
>> this info?
>>
>>
>> 從我的 iPhone 傳送
>>
>> Alex Earl  於 2012/8/3 上午12:41 寫道：
>>
>> spc is just a shortcut for  
>>
>> You may have to roll your own template, there is info on how to do that on
>> the wiki.
>>
>> Sent from my Windows Phone
>> 
>> From: michael chiu
>> Sent: 8/2/2012 8:50 AM
>> To: jenkinsci-users@googlegroups.com
>> Subject: miss changelist number in email-ext plug-in with Perforce
>>
>> Hi ALL,
>>Have anyone use email-ext groovy template to display Perforce
>> changeset info ?
>>I found it missed "changelist number " or is it a bug  in the
>> groovy-html.template.
>>It seem ${spc} don't work. what's the ${spc} mean ?
>>I'm using the lastest email-ext plugins and perforce plugin in
>> Jenkins 1.465 ?
>>
>> Regards,
>> Michael Chiu
>>



-- 
Website: http://earl-of-code.com

Re: miss changelist number in email-ext plug-in with Perforce

[Rob Petti]

P4_CHANGELIST is the environment variable name, so reference it using the 
env token macro.

${env,var="P4_CHANGELIST"}

On Thursday, 2 August 2012 19:36:55 UTC-6, michael chiu wrote:
>
> Yes  , I already have my template but if I dont know how to know the 
> property about changelist number in perforce change set? Where can I find 
> this info?
>
>
> 從我的 iPhone 傳送
>
> Alex Earl  於 2012/8/3 上午12:41 寫道：
>
> spc is just a shortcut for  
>
> You may have to roll your own template, there is info on how to do that on 
> the wiki.
>
> Sent from my Windows Phone
> --
> From: michael chiu
> Sent: 8/2/2012 8:50 AM
> To: jenkinsci-users@googlegroups.com
> Subject: miss changelist number in email-ext plug-in with Perforce
>
> Hi ALL, 
>Have anyone use email-ext groovy template to display Perforce 
> changeset info ? 
>I found it missed "changelist number " or is it a bug  in the 
> groovy-html.template.
>It seem ${spc} don't work. what's the ${spc} mean ? 
>I'm using the lastest email-ext plugins and perforce plugin in 
> Jenkins 1.465 ?
>
> Regards,
> Michael Chiu
>
>
>

Re: Cannot find parent pom, but it IS there

[Nomar Morado]

What is your directory structure? That is where is your parent Pom relative to 
your child project

Printing e-mails wastes valuable natural resources. Please don't print this 
message unless it is absolutely necessary. Thank you for thinking green!

Sent from my iPhone

On Aug 6, 2012, at 5:49 PM, chad.da...@emc.com wrote:

>> this is more of a maven question, I think.
>> 
>> Try turning -X on in the maven job to find out where it is looking.
>> 
> 
> Thanks.  I've already done that though.  The output is below.  Note, the 
> remote repository where it claims to be looking does indeed hold the 
> artifact.  Moreover, other projects on the same build server can access it 
> there.  
> 
> It may very well be a maven problem, but how do I fix it.  I'm using a 
> private maven repository for the build, as are the others that can 
> successfully retrieve the artifact.  From what I understand, I would suspect 
> a maven caching issue, but the -U is supposed to resolve that, as far as I 
> know.  
> 
> 
> ERROR: Failed to parse POMs
> org.apache.maven.project.ProjectBuildingException: Cannot find parent: 
> com.my.group:project-pom for project: 
> com.my.group.service.common:common:pom:1.1.0-SNAPSHOT for project 
> com.my.group.service.common:common:pom:1.1.0-SNAPSHOT
>at 
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370)
>at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821)
>at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
>at 
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:215)
>at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:332)
>at 
> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:871)
>at 
> hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:794)
>at hudson.FilePath.act(FilePath.java:753)
>at hudson.FilePath.act(FilePath.java:735)
>at 
> hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:534)
>at 
> hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:420)
>at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
>at hudson.model.Run.run(Run.java:1257)
>at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306)
>at hudson.model.ResourceController.execute(ResourceController.java:88)
>at hudson.model.Executor.run(Executor.java:127)
> Caused by: org.apache.maven.project.ProjectBuildingException: POM 
> 'com.my.group:project-pom' not found in repository: Unable to download the 
> artifact from any repository
> 
>  com.my.group:project-pom:pom:1.1.0-SNAPSHOT
> 
> from the specified remote repositories:
>  nexus (http://myNexus.com:8081/nexus/content/groups/public)
> for project com.my.group:project-pom
>at 
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:603)
>at 
> org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1366)
>... 15 more
> Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: 
> Unable to download the artifact from any repository
> 
>  com.my.group:project-pom:pom:1.1.0-SNAPSHOT
> 
> from the specified remote repositories:
>  nexus (http://myNexus.com:8081/nexus/content/groups/public)
> 
>at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212)
>at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74)
>at 
> org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:556)
>... 16 more
> Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
> download the artifact from any repository
>at 
> org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:331)
>at 
> org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200)
>... 18 more
> Email was triggered for: Failure

PAge Markup Plugin Dead?

[krishna chaitanya kurnala]

Hello All

I installed, Page Markup Plugin(
http://wiki.hudson-ci.org/display/HUDSON/Page+Markup+Plugin) in Jenkins
1.474, but, Dont see anything in Manage Jenkins Tab.

Want to know if this Plugin is Outdated or still functional ?

What are other Alternatives that you guys are using, for dispalying company
banner etc in Jenkins?

Thanks,
Krishna Chaitanya

Marking Sonar Builds

[krishna chaitanya kurnala]

Hello All

We are using Jenkins + SOnar. I have setup our own rule-sets using Quality
Profiles/ Thresh-holds(Warning and Error) for the same.
I am aware of Build Breaker that Fails the Build if the theresh-holds are
not met. I had a huge backlash due to Failing Builds ;-)

Wondering if there is a fine-grained way to specify the Jenkins Build as
Un-stable etc instead of Failing. Please let me know.

Thanks in Advance,
Krishna Chaitanya

RE: Cannot find parent pom, but it IS there

[Chad.Davis]

> this is more of a maven question, I think.
> 
> Try turning -X on in the maven job to find out where it is looking.
> 

Thanks.  I've already done that though.  The output is below.  Note, the remote 
repository where it claims to be looking does indeed hold the artifact.  
Moreover, other projects on the same build server can access it there.  

It may very well be a maven problem, but how do I fix it.  I'm using a private 
maven repository for the build, as are the others that can successfully 
retrieve the artifact.  From what I understand, I would suspect a maven caching 
issue, but the -U is supposed to resolve that, as far as I know.  


ERROR: Failed to parse POMs
org.apache.maven.project.ProjectBuildingException: Cannot find parent: 
com.my.group:project-pom for project: 
com.my.group.service.common:common:pom:1.1.0-SNAPSHOT for project 
com.my.group.service.common:common:pom:1.1.0-SNAPSHOT
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1370)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:821)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:215)
at hudson.maven.MavenEmbedder.readProject(MavenEmbedder.java:332)
at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:871)
at 
hudson.maven.MavenModuleSetBuild$PomParser.invoke(MavenModuleSetBuild.java:794)
at hudson.FilePath.act(FilePath.java:753)
at hudson.FilePath.act(FilePath.java:735)
at 
hudson.maven.MavenModuleSetBuild$RunnerImpl.parsePoms(MavenModuleSetBuild.java:534)
at 
hudson.maven.MavenModuleSetBuild$RunnerImpl.doRun(MavenModuleSetBuild.java:420)
at hudson.model.AbstractBuild$AbstractRunner.run(AbstractBuild.java:416)
at hudson.model.Run.run(Run.java:1257)
at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:306)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:127)
Caused by: org.apache.maven.project.ProjectBuildingException: POM 
'com.my.group:project-pom' not found in repository: Unable to download the 
artifact from any repository

  com.my.group:project-pom:pom:1.1.0-SNAPSHOT

from the specified remote repositories:
  nexus (http://myNexus.com:8081/nexus/content/groups/public)
 for project com.my.group:project-pom
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:603)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1366)
... 15 more
Caused by: org.apache.maven.artifact.resolver.ArtifactNotFoundException: Unable 
to download the artifact from any repository

  com.my.group:project-pom:pom:1.1.0-SNAPSHOT

from the specified remote repositories:
  nexus (http://myNexus.com:8081/nexus/content/groups/public)

at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:212)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:74)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.findModelFromRepository(DefaultMavenProjectBuilder.java:556)
... 16 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: Unable to 
download the artifact from any repository
at 
org.apache.maven.artifact.manager.DefaultWagonManager.getArtifact(DefaultWagonManager.java:331)
at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:200)
... 18 more
Email was triggered for: Failure

RE: Jenkins Unresponsive

[William Soula]

Is it possible the cobertura plugin is slowing down Jenkins?  I have several 
modules producing cobertura xml reports and then I have a job that gets all the 
coverage.xml files and puts them in folders and the plugin is pointed at these 
folders to pick up all the xml reports.  Would things work better if I instead 
got the .ser files and produced one coverage.xml file?  Below when I said the 
unresponsiveness occurred when clicking the job link of a job, that job was the 
code coverage aggregator job.  I have gone through and disabled a bunch of 
plugins, including cobertura, and now when I click that job it loads super 
quickly like I would expect.

Some more information:
Running under linux using the startup script distributed with Jenkins
Version of Jenkins is 1.459
Cobertura plugin is the latest 1.5

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of William Soula
Sent: Monday, August 06, 2012 9:38 AM
To: jenkinsci-users@googlegroups.com
Subject: Jenkins Unresponsive

Periodically through the day Jenkins decides to peg one of the processors and 
not return requests.  I cannot figure out what is the cause of this issue.  
I've been monitoring the Jenkins log and I see nothing in it around the time it 
hangs.  If I monitor the cpu usage with nmon, I can reliably predict when 
Jenkins is in this weird unresponsive state.  One CPU will be pegged at 100% 
and the other will be doing nothing.  When both cpus start taking work then 
Jenkins is usable again.  This morning everything was going fine and then I 
clicked the link for a job and the issue occurred, with nothing in the log.  A 
big problem with this is that it appears Jenkins gets so into whatever it is 
doing 100% on that one cpu that it drops its ssh connections to the slaves and 
builds fail because of that.  I've taken a look at the Jenkins monitoring 
plugin and can't see anything obviously wrong.  My main question is how do I 
debug this problem?  Where can I get more information about what Jenkins is 
doing when it has entered into this unresponsive state?  Below are the errors 
from the last time it came back and started working again:
Aug 6, 2012 9:34:39 AM winstone.Logger logInternal
SEVERE: Error while serving 
http://[address]/view/RC/job/RC_unit/buildHistory/ajax
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor454.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:485)
at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at 
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:197)
at 
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:171)
at 
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
at 
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at 
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
 

Re: Jenkins and Tomcat

[Pedro Perez]

Ok I figured it out. After it's finished building, Jenkins will destroy 
every process started during that build process. That is a bummer for those 
people like me that want to start Tomcat as part of the build process. If 
you're running Jenkins through Tomcat 7, you can disable it's auto kill 
functionality by adding this line to catalina.sh:

BUILD_ID=dontkillme

That will override the PID Jenkins keeps track of when it starts Tomcat, 
and thus Jenkins won't kill it. Hats off to you guys for your suggestions. 

Thanks for all your help!

Pedro

On Monday, August 6, 2012 11:30:12 AM UTC-7, Pedro Perez wrote:
>
> I tried both suggestions, the deploy plugin works great for me, as well as 
> using an ANT script to deploy it...the only problem is I need to shut 
> Tomcat down completely, manually place the .war, and then start up 
> Tomcat--otherwise Tomcat will remove some DB configuration files i keep in 
> /conf/Catalina/localhost. I wish there was a good way to stop/start/deploy 
> applications from Jenkins (the deploy plugin is nice, but it only 
> deploys...no controls to start and stop). 
>
> I'd be happy if Jenkins would stop automatically killing the Tomcat 
> process I start during the build, but I'm not sure how to disable the 
> auto-kill feature of jenkins when running Jenkins through the Tomcat 
> container...does anybody know how to do this?
>
> P
>
> On Monday, August 6, 2012 10:40:36 AM UTC-7, Jeff Vincent wrote:
>>
>> I tried the Jenkins deploy plugin but it wouldn't work with Tomcat 7 for 
>> some reason.  Maybe I missed something, but for my Maven projects, just 
>> ended up using the maven-tomcat7-plugin in the POM.
>>
>> On Mon, Aug 6, 2012 at 11:34 AM, Chris Marks wrote:
>>
>>> You might also look at the deploy plugin. It creates a post-build step 
>>> that can remotely deploy a war to multiple containers including Tomcat. 
>>>
>>> Topher
>>> On Aug 6, 2012 12:30 PM, "Jeff"  wrote:
>>>

 http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Executing_Manager_Commands_With_Ant
  

 In the <$TOMCAT_HOME>/lib folder there should be a JAR called 
 catalina-ant.jar.  Make sure it is in your ANT classpath.  Import the ant 
 tasks in your ant script:

  
  
  
 >>> classname="org.apache.catalina.ant.ResourcesTask"/> 
  
  
  
 >>> classname="org.apache.catalina.ant.UndeployTask"/>


 Then call it:

  
   <*deploy *
   path="/${app.name}" 
   username="${tomcat.dev.username}" 
   war="file:${package.name}/${war.build.dir}/${app.name}.war" 
   password="${tomcat.dev.pwd}" 
   url="${tomcat.dev.url}"
   /> 
 


 On Mon, Aug 6, 2012 at 11:04 AM, Pedro Perez wrote:

> Thanks for your reply ... I actually am using different Tomcat 
> deployments for Jenkins and my other app...my difficulty was in disabling 
> the process killer from Jenkins when Jenkins is run through Tomcat (there 
> are lots of instructions on how to disable the process killer when 
> Jenkins 
> is run as a java process without Tomcat). 
>
> I should look into that ANT task for deploying a webapp without 
> stopping/starting Tomcat...I don't know much about how to set that up 
> however.
>
> Thanks!
> P
>
>
> On Monday, August 6, 2012 9:50:04 AM UTC-7, Jeff Vincent wrote:
>>
>> I'm a relative n00b to Jenkins but if I were you, I wouldn't run your 
>> application on the same tomcat instance.  You are making your life 
>> harder. 
>>  Why not create another instance for deploying/testing the app?  You can 
>> run multiple versions and/or instances of tomcat on different ports, run 
>> one in a VM or on another system.
>>
>> Regardless, tomcat can undeploy/redeploy an application without 
>> stopping.  There is an ant Task for tomcat to allow deploying 
>> applications 
>> via the management API that do not require stopping or starting tomcat 
>> or 
>> affecting jenkinsunless it blows up or consumes memory, in which 
>> case 
>> it will mess up all applications running in that instance and kill your 
>> build/test processes anyway...so again, I wouldn't do it that way.
>>
>> Also if you were using Maven to build, there is a plugin that allows 
>> you to start a new tomcat instance for testing then shuts it down 
>> afterward.  I've not used it though.  There could be something similar 
>> for 
>> ANT.
>>
>> On Mon, Aug 6, 2012 at 10:20 AM, Pedro Perez wrote:
>>
>>> Hello,
>>>
>>> I'm new to Jenkins and so far I love it...but I have an issue 
>>> integrating with Tomcat. I have Jenkins stopping and starting Tomcat 
>>> via 
>>> ant script. However I've found that Jenkins process-killer shuts down 
>>> tomcat for me after it's finished. I've read 
>>> https://wiki.jenkins-ci.**o

Re: Jenkins and Tomcat

[Pedro Perez]

I tried both suggestions, the deploy plugin works great for me, as well as 
using an ANT script to deploy it...the only problem is I need to shut 
Tomcat down completely, manually place the .war, and then start up 
Tomcat--otherwise Tomcat will remove some DB configuration files i keep in 
/conf/Catalina/localhost. I wish there was a good way to stop/start/deploy 
applications from Jenkins (the deploy plugin is nice, but it only 
deploys...no controls to start and stop). 

I'd be happy if Jenkins would stop automatically killing the Tomcat process 
I start during the build, but I'm not sure how to disable the auto-kill 
feature of jenkins when running Jenkins through the Tomcat container...does 
anybody know how to do this?

P

On Monday, August 6, 2012 10:40:36 AM UTC-7, Jeff Vincent wrote:
>
> I tried the Jenkins deploy plugin but it wouldn't work with Tomcat 7 for 
> some reason.  Maybe I missed something, but for my Maven projects, just 
> ended up using the maven-tomcat7-plugin in the POM.
>
> On Mon, Aug 6, 2012 at 11:34 AM, Chris Marks  wrote:
>
>> You might also look at the deploy plugin. It creates a post-build step 
>> that can remotely deploy a war to multiple containers including Tomcat. 
>>
>> Topher
>> On Aug 6, 2012 12:30 PM, "Jeff"  wrote:
>>
>>>
>>> http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Executing_Manager_Commands_With_Ant
>>>  
>>>
>>> In the <$TOMCAT_HOME>/lib folder there should be a JAR called 
>>> catalina-ant.jar.  Make sure it is in your ANT classpath.  Import the ant 
>>> tasks in your ant script:
>>>
>>>  
>>>  
>>>  
>>> >> classname="org.apache.catalina.ant.ResourcesTask"/> 
>>>  
>>>  
>>>  
>>> >> classname="org.apache.catalina.ant.UndeployTask"/>
>>>
>>>
>>> Then call it:
>>>
>>>  
>>>   <*deploy *
>>>   path="/${app.name}" 
>>>   username="${tomcat.dev.username}" 
>>>   war="file:${package.name}/${war.build.dir}/${app.name}.war" 
>>>   password="${tomcat.dev.pwd}" 
>>>   url="${tomcat.dev.url}"
>>>   /> 
>>> 
>>>
>>>
>>> On Mon, Aug 6, 2012 at 11:04 AM, Pedro Perez  wrote:
>>>
 Thanks for your reply ... I actually am using different Tomcat 
 deployments for Jenkins and my other app...my difficulty was in disabling 
 the process killer from Jenkins when Jenkins is run through Tomcat (there 
 are lots of instructions on how to disable the process killer when Jenkins 
 is run as a java process without Tomcat). 

 I should look into that ANT task for deploying a webapp without 
 stopping/starting Tomcat...I don't know much about how to set that up 
 however.

 Thanks!
 P


 On Monday, August 6, 2012 9:50:04 AM UTC-7, Jeff Vincent wrote:
>
> I'm a relative n00b to Jenkins but if I were you, I wouldn't run your 
> application on the same tomcat instance.  You are making your life 
> harder. 
>  Why not create another instance for deploying/testing the app?  You can 
> run multiple versions and/or instances of tomcat on different ports, run 
> one in a VM or on another system.
>
> Regardless, tomcat can undeploy/redeploy an application without 
> stopping.  There is an ant Task for tomcat to allow deploying 
> applications 
> via the management API that do not require stopping or starting tomcat or 
> affecting jenkinsunless it blows up or consumes memory, in which case 
> it will mess up all applications running in that instance and kill your 
> build/test processes anyway...so again, I wouldn't do it that way.
>
> Also if you were using Maven to build, there is a plugin that allows 
> you to start a new tomcat instance for testing then shuts it down 
> afterward.  I've not used it though.  There could be something similar 
> for 
> ANT.
>
> On Mon, Aug 6, 2012 at 10:20 AM, Pedro Perez wrote:
>
>> Hello,
>>
>> I'm new to Jenkins and so far I love it...but I have an issue 
>> integrating with Tomcat. I have Jenkins stopping and starting Tomcat via 
>> ant script. However I've found that Jenkins process-killer shuts down 
>> tomcat for me after it's finished. I've read https://wiki.jenkins-ci.
>> **org/display/JENKINS/**ProcessTreeKiller
>>  and 
>> have tried to disable it, however I run Jenkins through Tomcat, and I'm 
>> not 
>> sure how to disable the process killer when Jenkins is run as a simple 
>> web 
>> app on Tomcat 7. I tried to simply override the BUILD_ID variable like 
>> this:
>>
>> $BUILD_ID=dontKillMe
>>
>> to no avail. Even if that worked though, I'm wondering if there is a 
>> "cleaner" solution to starting and stopping Tomcat with Jenkins. When 
>> using 
>> ANT to start/stop it usually works, but not 100% every time. I've read 
>> about a tomcat plugin for Jenkins, but I think it doesn't stop/start 
>> Tomcat 
>>

Re: CVS and extssh

[Rodri]

Hi,
After following all the instructions above:

   - Jenkins conf -> CVSROOT = :ext:: 
   - Env var-> CVS_RSH = path to plink.exe
   - Public key copied in the server
   - able to ssh to the server using windows cli and plink without typing 
   the password
   - able to connect to cvs using cli

I'm still getting an error:

cvs checkout -P -r BBB -d workspace XXX 
> ERROR: CVS Authentication failed: 
> nullorg.netbeans.lib.cvsclient.connection.AuthenticationException 
> :
>  SSH connection failed.
>   at 
> org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:141)
>  
> 
>   at org.netbeans.lib.cvsclient.Client$1.run(Client.java:374) 
> 
>   at java.lang.Thread.run(Unknown Source)
> Caused by: com.jcraft.jsch.JSchException: Session.connect: 
> java.net.ConnectException: Connection timed out: connect
>   at com.jcraft.jsch.Session.connect(Session.java:525)
>   at com.jcraft.jsch.Session.connect(Session.java:160)
>   at 
> org.netbeans.lib.cvsclient.connection.SSHConnection.open(SSHConnection.java:139)
>   ... 2 more
> ERROR: Cvs task failedFinished 
> : FAILURE
>
>
Any clue?
Thanks in advance!
Regards
Rodri


El jueves, 26 de julio de 2012 04:43:00 UTC-3, Sascha G. escribió:
>
> Hi,
>
> I had the same problem with the SSH connection for a CVS export with 
> Jenkins-CI.
> The solution was to convert the PuTTy-generated SSH .ppk into an OpenSSH 
> file. After that it works great!
>
> Regards,
> Sascha
>
>
> On Wednesday, May 2, 2012 2:41:13 PM UTC+2, Xavier NOPRE wrote:
>>
>> Hi,
>>
>> I've just installed the last version of Jenkins. I have created a first 
>> job for a Maven project. But my problem is with CVS. In Eclipse, my CVS URL 
>> is with ":extssh:" prefix. But with Jenkins, I have this error : "cvs 
>> checkout: Unknown method (`extssh') in CVSROOT.".
>>
>> My server OS is Windows. I have installed cvs.exe in c:\windows. 
>>
>> How can I solve this problem ? Do I have to install some CVS extension 
>> for the extssh support ?
>>
>> Thanks,
>>
>> Xavier
>>
>>

Re: Jenkins and Tomcat

[Jeff]

I tried the Jenkins deploy plugin but it wouldn't work with Tomcat 7 for
some reason.  Maybe I missed something, but for my Maven projects, just
ended up using the maven-tomcat7-plugin in the POM.

On Mon, Aug 6, 2012 at 11:34 AM, Chris Marks  wrote:

> You might also look at the deploy plugin. It creates a post-build step
> that can remotely deploy a war to multiple containers including Tomcat.
>
> Topher
> On Aug 6, 2012 12:30 PM, "Jeff"  wrote:
>
>>
>> http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Executing_Manager_Commands_With_Ant
>>
>> In the <$TOMCAT_HOME>/lib folder there should be a JAR called
>> catalina-ant.jar.  Make sure it is in your ANT classpath.  Import the ant
>> tasks in your ant script:
>>
>> 
>> 
>> 
>> > classname="org.apache.catalina.ant.ResourcesTask"/>
>> 
>> 
>> 
>> > classname="org.apache.catalina.ant.UndeployTask"/>
>>
>>
>> Then call it:
>>
>> 
>>   <*deploy *
>>   path="/${app.name}"
>>   username="${tomcat.dev.username}"
>>   war="file:${package.name}/${war.build.dir}/${app.name}.war"
>>   password="${tomcat.dev.pwd}"
>>   url="${tomcat.dev.url}"
>>   />
>> 
>>
>>
>> On Mon, Aug 6, 2012 at 11:04 AM, Pedro Perez  wrote:
>>
>>> Thanks for your reply ... I actually am using different Tomcat
>>> deployments for Jenkins and my other app...my difficulty was in disabling
>>> the process killer from Jenkins when Jenkins is run through Tomcat (there
>>> are lots of instructions on how to disable the process killer when Jenkins
>>> is run as a java process without Tomcat).
>>>
>>> I should look into that ANT task for deploying a webapp without
>>> stopping/starting Tomcat...I don't know much about how to set that up
>>> however.
>>>
>>> Thanks!
>>> P
>>>
>>>
>>> On Monday, August 6, 2012 9:50:04 AM UTC-7, Jeff Vincent wrote:

 I'm a relative n00b to Jenkins but if I were you, I wouldn't run your
 application on the same tomcat instance.  You are making your life harder.
  Why not create another instance for deploying/testing the app?  You can
 run multiple versions and/or instances of tomcat on different ports, run
 one in a VM or on another system.

 Regardless, tomcat can undeploy/redeploy an application without
 stopping.  There is an ant Task for tomcat to allow deploying applications
 via the management API that do not require stopping or starting tomcat or
 affecting jenkinsunless it blows up or consumes memory, in which case
 it will mess up all applications running in that instance and kill your
 build/test processes anyway...so again, I wouldn't do it that way.

 Also if you were using Maven to build, there is a plugin that allows
 you to start a new tomcat instance for testing then shuts it down
 afterward.  I've not used it though.  There could be something similar for
 ANT.

 On Mon, Aug 6, 2012 at 10:20 AM, Pedro Perez wrote:

> Hello,
>
> I'm new to Jenkins and so far I love it...but I have an issue
> integrating with Tomcat. I have Jenkins stopping and starting Tomcat via
> ant script. However I've found that Jenkins process-killer shuts down
> tomcat for me after it's finished. I've read https://wiki.jenkins-ci.*
> *org/display/JENKINS/**ProcessTreeKiller
>  and
> have tried to disable it, however I run Jenkins through Tomcat, and I'm 
> not
> sure how to disable the process killer when Jenkins is run as a simple web
> app on Tomcat 7. I tried to simply override the BUILD_ID variable like 
> this:
>
> $BUILD_ID=dontKillMe
>
> to no avail. Even if that worked though, I'm wondering if there is a
> "cleaner" solution to starting and stopping Tomcat with Jenkins. When 
> using
> ANT to start/stop it usually works, but not 100% every time. I've read
> about a tomcat plugin for Jenkins, but I think it doesn't stop/start 
> Tomcat
> in the order I need it...basically my build script does a code checkout,
> compile, stop tomcat, replace war, start tomcat, run tests against newly
> deployed web app.
>
> Does anybody know the "correct" way to interact with Tomcat and
> Jenkins?
>
> Thanks
> Pedro
>



 --
 Jeff Vincent
 predato...@gmail.com
 See my LinkedIn profile at:
 http://www.linkedin.com/in/**rjeffreyvincent
 I ♥ DropBox  !!


>>
>>
>> --
>> Jeff Vincent
>> predato...@gmail.com
>> See my LinkedIn profile at:
>> http://www.linkedin.com/in/rjeffreyvincent
>> I ♥ DropBox  !!
>>
>>


-- 
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox  !!

Re: Jenkins and Tomcat

[Chris Marks]

You might also look at the deploy plugin. It creates a post-build step that
can remotely deploy a war to multiple containers including Tomcat.

Topher
On Aug 6, 2012 12:30 PM, "Jeff"  wrote:

>
> http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Executing_Manager_Commands_With_Ant
>
> In the <$TOMCAT_HOME>/lib folder there should be a JAR called
> catalina-ant.jar.  Make sure it is in your ANT classpath.  Import the ant
> tasks in your ant script:
>
> 
> 
> 
>  classname="org.apache.catalina.ant.ResourcesTask"/>
> 
> 
> 
> 
>
>
> Then call it:
>
> 
>   <*deploy *
>   path="/${app.name}"
>   username="${tomcat.dev.username}"
>   war="file:${package.name}/${war.build.dir}/${app.name}.war"
>   password="${tomcat.dev.pwd}"
>   url="${tomcat.dev.url}"
>   />
> 
>
>
> On Mon, Aug 6, 2012 at 11:04 AM, Pedro Perez  wrote:
>
>> Thanks for your reply ... I actually am using different Tomcat
>> deployments for Jenkins and my other app...my difficulty was in disabling
>> the process killer from Jenkins when Jenkins is run through Tomcat (there
>> are lots of instructions on how to disable the process killer when Jenkins
>> is run as a java process without Tomcat).
>>
>> I should look into that ANT task for deploying a webapp without
>> stopping/starting Tomcat...I don't know much about how to set that up
>> however.
>>
>> Thanks!
>> P
>>
>>
>> On Monday, August 6, 2012 9:50:04 AM UTC-7, Jeff Vincent wrote:
>>>
>>> I'm a relative n00b to Jenkins but if I were you, I wouldn't run your
>>> application on the same tomcat instance.  You are making your life harder.
>>>  Why not create another instance for deploying/testing the app?  You can
>>> run multiple versions and/or instances of tomcat on different ports, run
>>> one in a VM or on another system.
>>>
>>> Regardless, tomcat can undeploy/redeploy an application without
>>> stopping.  There is an ant Task for tomcat to allow deploying applications
>>> via the management API that do not require stopping or starting tomcat or
>>> affecting jenkinsunless it blows up or consumes memory, in which case
>>> it will mess up all applications running in that instance and kill your
>>> build/test processes anyway...so again, I wouldn't do it that way.
>>>
>>> Also if you were using Maven to build, there is a plugin that allows you
>>> to start a new tomcat instance for testing then shuts it down afterward.
>>>  I've not used it though.  There could be something similar for ANT.
>>>
>>> On Mon, Aug 6, 2012 at 10:20 AM, Pedro Perez  wrote:
>>>
 Hello,

 I'm new to Jenkins and so far I love it...but I have an issue
 integrating with Tomcat. I have Jenkins stopping and starting Tomcat via
 ant script. However I've found that Jenkins process-killer shuts down
 tomcat for me after it's finished. I've read https://wiki.jenkins-ci.**
 org/display/JENKINS/**ProcessTreeKiller
  and
 have tried to disable it, however I run Jenkins through Tomcat, and I'm not
 sure how to disable the process killer when Jenkins is run as a simple web
 app on Tomcat 7. I tried to simply override the BUILD_ID variable like 
 this:

 $BUILD_ID=dontKillMe

 to no avail. Even if that worked though, I'm wondering if there is a
 "cleaner" solution to starting and stopping Tomcat with Jenkins. When using
 ANT to start/stop it usually works, but not 100% every time. I've read
 about a tomcat plugin for Jenkins, but I think it doesn't stop/start Tomcat
 in the order I need it...basically my build script does a code checkout,
 compile, stop tomcat, replace war, start tomcat, run tests against newly
 deployed web app.

 Does anybody know the "correct" way to interact with Tomcat and Jenkins?

 Thanks
 Pedro

>>>
>>>
>>>
>>> --
>>> Jeff Vincent
>>> predato...@gmail.com
>>> See my LinkedIn profile at:
>>> http://www.linkedin.com/in/**rjeffreyvincent
>>> I ♥ DropBox  !!
>>>
>>>
>
>
> --
> Jeff Vincent
> predato...@gmail.com
> See my LinkedIn profile at:
> http://www.linkedin.com/in/rjeffreyvincent
> I ♥ DropBox  !!
>
>

Selenium crashes Chrome when running from Jenkins

[Liron Yahdav]

TLDR: Running ruby scripts from Jenkins on OS X that use the 
selenium-webdriver gem with chromedriver causes the "Aw snap" page to come 
up in Chrome. Running those same scripts from outside of Jenkins works 
fine. Any ideas as to what's wrong?

--

Long version:
We have a CI machine that's a MacBook Pro running OS X Mountain Lion with 
Jenkins installed. The Jenkins server runs as a user who can login to the 
system. We configured Jasmine to use Chrome for the `rake jasmine:ci` 
command by setting ENV['JASMINE_BROWSER'] = 'chrome'. This all works fine 
when running `rake jasmine:ci` from the command line on that machine, but 
when Jenkins is configured to run the same exact command, Chrome will start 
up and when it tries to hit the url to run the tests, the tab crashes with 
the "Aw Snap" error page. I looked at the chromedriver.log file that's 
generated and there are no errors, it basically just stops all of a sudden. 
The Jenkins build eventually gets a Selenium timeout error.

I've tried setting up the same config on a MacBook Air running OS X Lion 
and the same problem occurs.
We also have integration tests written with RSpec and Capybara and when we 
configure it to use Selenium with chromedriver, the same problem occurs 
when running through Jenkins, though the "Aw Snap" page comes up a few 
steps into the first test.

Has anyone gotten a similar setup working or have any idea what the issue 
could be? Thanks!

Re: Jenkins and Tomcat

[Jeff]

http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html#Executing_Manager_Commands_With_Ant

In the <$TOMCAT_HOME>/lib folder there should be a JAR called
catalina-ant.jar.  Make sure it is in your ANT classpath.  Import the ant
tasks in your ant script:











Then call it:


  <*deploy *
  path="/${app.name}"
  username="${tomcat.dev.username}"
  war="file:${package.name}/${war.build.dir}/${app.name}.war"
  password="${tomcat.dev.pwd}"
  url="${tomcat.dev.url}"
  />



On Mon, Aug 6, 2012 at 11:04 AM, Pedro Perez  wrote:

> Thanks for your reply ... I actually am using different Tomcat deployments
> for Jenkins and my other app...my difficulty was in disabling the process
> killer from Jenkins when Jenkins is run through Tomcat (there are lots of
> instructions on how to disable the process killer when Jenkins is run as a
> java process without Tomcat).
>
> I should look into that ANT task for deploying a webapp without
> stopping/starting Tomcat...I don't know much about how to set that up
> however.
>
> Thanks!
> P
>
>
> On Monday, August 6, 2012 9:50:04 AM UTC-7, Jeff Vincent wrote:
>>
>> I'm a relative n00b to Jenkins but if I were you, I wouldn't run your
>> application on the same tomcat instance.  You are making your life harder.
>>  Why not create another instance for deploying/testing the app?  You can
>> run multiple versions and/or instances of tomcat on different ports, run
>> one in a VM or on another system.
>>
>> Regardless, tomcat can undeploy/redeploy an application without stopping.
>>  There is an ant Task for tomcat to allow deploying applications via the
>> management API that do not require stopping or starting tomcat or affecting
>> jenkinsunless it blows up or consumes memory, in which case it will
>> mess up all applications running in that instance and kill your build/test
>> processes anyway...so again, I wouldn't do it that way.
>>
>> Also if you were using Maven to build, there is a plugin that allows you
>> to start a new tomcat instance for testing then shuts it down afterward.
>>  I've not used it though.  There could be something similar for ANT.
>>
>> On Mon, Aug 6, 2012 at 10:20 AM, Pedro Perez  wrote:
>>
>>> Hello,
>>>
>>> I'm new to Jenkins and so far I love it...but I have an issue
>>> integrating with Tomcat. I have Jenkins stopping and starting Tomcat via
>>> ant script. However I've found that Jenkins process-killer shuts down
>>> tomcat for me after it's finished. I've read https://wiki.jenkins-ci.**
>>> org/display/JENKINS/**ProcessTreeKiller
>>>  and
>>> have tried to disable it, however I run Jenkins through Tomcat, and I'm not
>>> sure how to disable the process killer when Jenkins is run as a simple web
>>> app on Tomcat 7. I tried to simply override the BUILD_ID variable like this:
>>>
>>> $BUILD_ID=dontKillMe
>>>
>>> to no avail. Even if that worked though, I'm wondering if there is a
>>> "cleaner" solution to starting and stopping Tomcat with Jenkins. When using
>>> ANT to start/stop it usually works, but not 100% every time. I've read
>>> about a tomcat plugin for Jenkins, but I think it doesn't stop/start Tomcat
>>> in the order I need it...basically my build script does a code checkout,
>>> compile, stop tomcat, replace war, start tomcat, run tests against newly
>>> deployed web app.
>>>
>>> Does anybody know the "correct" way to interact with Tomcat and Jenkins?
>>>
>>> Thanks
>>> Pedro
>>>
>>
>>
>>
>> --
>> Jeff Vincent
>> predato...@gmail.com
>> See my LinkedIn profile at:
>> http://www.linkedin.com/in/**rjeffreyvincent
>> I ♥ DropBox  !!
>>
>>


-- 
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox  !!

Re: Jenkins and Tomcat

[Pedro Perez]

Thanks for your reply ... I actually am using different Tomcat deployments 
for Jenkins and my other app...my difficulty was in disabling the process 
killer from Jenkins when Jenkins is run through Tomcat (there are lots of 
instructions on how to disable the process killer when Jenkins is run as a 
java process without Tomcat). 

I should look into that ANT task for deploying a webapp without 
stopping/starting Tomcat...I don't know much about how to set that up 
however.

Thanks!
P

On Monday, August 6, 2012 9:50:04 AM UTC-7, Jeff Vincent wrote:
>
> I'm a relative n00b to Jenkins but if I were you, I wouldn't run your 
> application on the same tomcat instance.  You are making your life harder. 
>  Why not create another instance for deploying/testing the app?  You can 
> run multiple versions and/or instances of tomcat on different ports, run 
> one in a VM or on another system.
>
> Regardless, tomcat can undeploy/redeploy an application without stopping. 
>  There is an ant Task for tomcat to allow deploying applications via the 
> management API that do not require stopping or starting tomcat or affecting 
> jenkinsunless it blows up or consumes memory, in which case it will 
> mess up all applications running in that instance and kill your build/test 
> processes anyway...so again, I wouldn't do it that way.
>
> Also if you were using Maven to build, there is a plugin that allows you 
> to start a new tomcat instance for testing then shuts it down afterward. 
>  I've not used it though.  There could be something similar for ANT.
>
> On Mon, Aug 6, 2012 at 10:20 AM, Pedro Perez  wrote:
>
>> Hello,
>>
>> I'm new to Jenkins and so far I love it...but I have an issue integrating 
>> with Tomcat. I have Jenkins stopping and starting Tomcat via ant script. 
>> However I've found that Jenkins process-killer shuts down tomcat for me 
>> after it's finished. I've read 
>> https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller and have 
>> tried to disable it, however I run Jenkins through Tomcat, and I'm not sure 
>> how to disable the process killer when Jenkins is run as a simple web app 
>> on Tomcat 7. I tried to simply override the BUILD_ID variable like this:
>>
>> $BUILD_ID=dontKillMe
>>
>> to no avail. Even if that worked though, I'm wondering if there is a 
>> "cleaner" solution to starting and stopping Tomcat with Jenkins. When using 
>> ANT to start/stop it usually works, but not 100% every time. I've read 
>> about a tomcat plugin for Jenkins, but I think it doesn't stop/start Tomcat 
>> in the order I need it...basically my build script does a code checkout, 
>> compile, stop tomcat, replace war, start tomcat, run tests against newly 
>> deployed web app. 
>>
>> Does anybody know the "correct" way to interact with Tomcat and Jenkins?
>>
>> Thanks
>> Pedro
>>
>
>
>
> -- 
> Jeff Vincent
> predato...@gmail.com
> See my LinkedIn profile at:
> http://www.linkedin.com/in/rjeffreyvincent
> I ♥ DropBox  !!  
>
> 

Re: Jenkins and Tomcat

[Jeff]

I'm a relative n00b to Jenkins but if I were you, I wouldn't run your
application on the same tomcat instance.  You are making your life harder.
 Why not create another instance for deploying/testing the app?  You can
run multiple versions and/or instances of tomcat on different ports, run
one in a VM or on another system.

Regardless, tomcat can undeploy/redeploy an application without stopping.
 There is an ant Task for tomcat to allow deploying applications via the
management API that do not require stopping or starting tomcat or affecting
jenkinsunless it blows up or consumes memory, in which case it will
mess up all applications running in that instance and kill your build/test
processes anyway...so again, I wouldn't do it that way.

Also if you were using Maven to build, there is a plugin that allows you to
start a new tomcat instance for testing then shuts it down afterward.  I've
not used it though.  There could be something similar for ANT.

On Mon, Aug 6, 2012 at 10:20 AM, Pedro Perez  wrote:

> Hello,
>
> I'm new to Jenkins and so far I love it...but I have an issue integrating
> with Tomcat. I have Jenkins stopping and starting Tomcat via ant script.
> However I've found that Jenkins process-killer shuts down tomcat for me
> after it's finished. I've read
> https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller and have
> tried to disable it, however I run Jenkins through Tomcat, and I'm not sure
> how to disable the process killer when Jenkins is run as a simple web app
> on Tomcat 7. I tried to simply override the BUILD_ID variable like this:
>
> $BUILD_ID=dontKillMe
>
> to no avail. Even if that worked though, I'm wondering if there is a
> "cleaner" solution to starting and stopping Tomcat with Jenkins. When using
> ANT to start/stop it usually works, but not 100% every time. I've read
> about a tomcat plugin for Jenkins, but I think it doesn't stop/start Tomcat
> in the order I need it...basically my build script does a code checkout,
> compile, stop tomcat, replace war, start tomcat, run tests against newly
> deployed web app.
>
> Does anybody know the "correct" way to interact with Tomcat and Jenkins?
>
> Thanks
> Pedro
>



-- 
Jeff Vincent
predato...@gmail.com
See my LinkedIn profile at:
http://www.linkedin.com/in/rjeffreyvincent
I ♥ DropBox  !!

Multiple "promotions"

[David Weintraub]

We are using the Build Promotion plugin for deployments. I like it
because it allows me to deploy the build I want to the servers I want.
For example, our last build is Build #27, but I want to deploy Build
#20 to prod1. I can go back to Build #20, apply the promotion to
prod1. The Build Promotion plugin will lock the build, do the
deployment, and mark that particular build as being deployed into
production..

The only problem is that it allows only a single instance of the
deployment. I don't mind having separate deployments for QA, UAT, and
Production. However, if we happen to have two different production
servers, the Build Promotion plugin can only deploy to one and not the
other. I can reexecute the promotion, but only to the same server as
before.

Is there another plugin like the Build Promotion plugin that will
allow for multiple deployments and still mark the build when a
deployment happens?

-- 
David Weintraub
qazw...@gmail.com

Jenkins and Tomcat

[Pedro Perez]

Hello,

I'm new to Jenkins and so far I love it...but I have an issue integrating 
with Tomcat. I have Jenkins stopping and starting Tomcat via ant script. 
However I've found that Jenkins process-killer shuts down tomcat for me 
after it's finished. I've read 
https://wiki.jenkins-ci.org/display/JENKINS/ProcessTreeKiller and have 
tried to disable it, however I run Jenkins through Tomcat, and I'm not sure 
how to disable the process killer when Jenkins is run as a simple web app 
on Tomcat 7. I tried to simply override the BUILD_ID variable like this:

$BUILD_ID=dontKillMe

to no avail. Even if that worked though, I'm wondering if there is a 
"cleaner" solution to starting and stopping Tomcat with Jenkins. When using 
ANT to start/stop it usually works, but not 100% every time. I've read 
about a tomcat plugin for Jenkins, but I think it doesn't stop/start Tomcat 
in the order I need it...basically my build script does a code checkout, 
compile, stop tomcat, replace war, start tomcat, run tests against newly 
deployed web app. 

Does anybody know the "correct" way to interact with Tomcat and Jenkins?

Thanks
Pedro

Re: restart broken build when certain string is detected?

[David Weintraub]

Unless you plan on stopping mid-checkout, I can think of a single way
to do what you want. After the checkout, run "svn status". If you get
anything returned, you know that the checkout/update failed. From
there, you can force a build failure.

I don't think there's an easy way to parse the console output (unless
some plugin exists that allows your build system to do this).

On Mon, Aug 6, 2012 at 10:13 AM, phil swenson  wrote:
> I have a large Jenkins setup in Germany running against SVN in the US.
>  Unfortunately, I get quite a few broken builds from SVN flaking out
> (network drops I assume).  We've never had this problem with
> everything being in the same datacenter.
>
> I don't have a good solution to preventing the problem, so what I'd
> like to do is rerun the job when a certain text string is detected
> (org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT
> /svn/sag/!svn/vcc/default failed).
>
> ideas?
>
> thanks



-- 
David Weintraub
qazw...@gmail.com

Assertion Error on SVNKit

[David Weintraub]

Got the following on a checkout. It doesn't seem to affect anything:

AssertionError: appears to be using unpatched svnkit at
jar:file:/C:/Jenkins/plugins/subversion/WEB-INF/lib/svnkit-1.7.4-jenkins-3.jar!/org/tmatesoft/svn/core/wc/SVNEvent.class

I'm using Jenkins Subversion plugin 1.42 and Jenkins 1.476 -- both the
latest version.

Anyone else seen this?

-- 
David Weintraub
qazw...@gmail.com

RE: When will Jenkins LTS support Subversion 1.7?

[David Aldrich]

Thanks James

David

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Nord, James
Sent: 06 August 2012 16:38
To: jenkinsci-users@googlegroups.com
Subject: RE: When will Jenkins LTS support Subversion 1.7?

Hi David,

It may happen in the next versionof LTS which would be in 3 months time.

You can should be able to run the latest subversion plugin in the just released 
LTS.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com]
 On Behalf Of David Aldrich
Sent: 06 August 2012 15:23
To: jenkinsci-users@googlegroups.com
Subject: When will Jenkins LTS support Subversion 1.7?

Hi

Subversion 1.7 was first supported in version 1.40 of the Jenkins Subversion 
Plugin.

Does anyone know when Jenkins Subversion plugin 1.40 or later will be included 
in a Jenkins LTS release?

Best regards

David





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as 
well as any copies. The content of e-mails as well as traffic data may be 
monitored by NDS for employment and security purposes. To protect the 
environment please do not print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**


Click 
here
 to report this email as spam.

RE: When will Jenkins LTS support Subversion 1.7?

[Nord, James]

Hi David,

It may happen in the next versionof LTS which would be in 3 months time.

You can should be able to run the latest subversion plugin in the just released 
LTS.

/James

From: jenkinsci-users@googlegroups.com 
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich
Sent: 06 August 2012 15:23
To: jenkinsci-users@googlegroups.com
Subject: When will Jenkins LTS support Subversion 1.7?

Hi

Subversion 1.7 was first supported in version 1.40 of the Jenkins Subversion 
Plugin.

Does anyone know when Jenkins Subversion plugin 1.40 or later will be included 
in a Jenkins LTS release?

Best regards

David





**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

Re: Jenkins remote API + Email notification

[Slide]

In answer to your second question, it doesn't look like the jelly:util
lib supports any sort of authentication for the loadText tag, so I
don't think it is possible.

slide

On Mon, Aug 6, 2012 at 7:27 AM, Wojciech Jodel  wrote:
> Hi all,
>
> I am trying to somehow connect my jelly template used by Extended Email
> Notification plugin
> (https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin) to use
> Jenkins Remote API to display changes for every build. For now, I am simply
> trying to display XML generated by Remote API with this code:
>
>  xmlns:d="jelly:define" xmlns:u="jelly:util">
> ...
> https://my-jenkins/job/my-job-name/1/api/xml"; var="result"
> />
> ${result}
> ...
> 
>
> It fails, and I get message: "JellyException: null:72:103: Could not find
> uri: https://my-jenkins/job/my-job-name/1/api/xml"; despite the fact, that
> URL exists. What may i be doing wrong?
>
> Another concern is that this URL in my Jenkins is secured - is it posible to
> provide HTTP Basic Authentication within jelly script?
>
> Thanks in advance,
> Wojtek
>
>
>



-- 
Website: http://earl-of-code.com

Jenkins remote API + Email notification

[Wojtek Jodel]

Hi all,

I am trying to somehow connect my jelly template used by Extended
Email Notification plugin (https://wiki.jenkins-ci.org/display/JENKINS/
Email-ext+plugin) to use Jenkins Remote API to display changes for
every build. For now, I am simply trying to display XML generated by
Remote API with this code:


...
https://my-jenkins/job/my-job-name/1/api/xml";
var="result" />
${result}
...


It fails, and I get message: "JellyException: null:72:103: Could not
find uri: https://my-jenkins/job/my-job-name/1/api/xml"; despite the
fact, that URL exists. What may i be doing wrong?

Another concern is that this URL in my Jenkins is secured - is it
posible to provide HTTP Basic Authentication within jelly script?

Thanks in advance,
Wojtek

Jenkins Unresponsive

[William Soula]

Periodically through the day Jenkins decides to peg one of the processors and 
not return requests.  I cannot figure out what is the cause of this issue.  
I've been monitoring the Jenkins log and I see nothing in it around the time it 
hangs.  If I monitor the cpu usage with nmon, I can reliably predict when 
Jenkins is in this weird unresponsive state.  One CPU will be pegged at 100% 
and the other will be doing nothing.  When both cpus start taking work then 
Jenkins is usable again.  This morning everything was going fine and then I 
clicked the link for a job and the issue occurred, with nothing in the log.  A 
big problem with this is that it appears Jenkins gets so into whatever it is 
doing 100% on that one cpu that it drops its ssh connections to the slaves and 
builds fail because of that.  I've taken a look at the Jenkins monitoring 
plugin and can't see anything obviously wrong.  My main question is how do I 
debug this problem?  Where can I get more information about what Jenkins is 
doing when it has entered into this unresponsive state?  Below are the errors 
from the last time it came back and started working again:
Aug 6, 2012 9:34:39 AM winstone.Logger logInternal
SEVERE: Error while serving 
http://[address]/view/RC/job/RC_unit/buildHistory/ajax
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor454.invoke(Unknown Source)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at 
org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288)
at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151)
at 
org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90)
at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:111)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241)
at 
org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53)
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:571)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:656)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:485)
at org.kohsuke.stapler.Stapler.service(Stapler.java:159)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:45)
at winstone.ServletConfiguration.execute(ServletConfiguration.java:248)
at winstone.RequestDispatcher.forward(RequestDispatcher.java:333)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95)
at 
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:197)
at 
net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:171)
at 
net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86)
at 
org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at 
hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66)
at 
hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47)
at winstone.FilterConfiguration.execute(FilterConfiguration.java:194)
at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at 
hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 
org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166)
at 
hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87)
at 

Jenkins remote API + Email notification

[Wojciech Jodel]

Hi all,

I am trying to somehow connect my jelly template used by Extended Email
Notification plugin (
https://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin) to use
Jenkins Remote API to display changes for every build. For now, I am simply
trying to display XML generated by Remote API with this code:

**
*...*
* https://my-jenkins/job/my-job-name/1/api/xml";
var="result" />*
* ${result}*
*...*
**

It fails, and I get message: "*JellyException: null:72:103: Could not find
uri: https://my-jenkins/job/my-job-name/1/api/xml*"; despite the fact, that
URL exists. What may i be doing wrong?

Another concern is that this URL in my Jenkins is secured - is it posible
to provide HTTP Basic Authentication within jelly script?

Thanks in advance,
Wojtek

When will Jenkins LTS support Subversion 1.7?

[David Aldrich]

Hi

Subversion 1.7 was first supported in version 1.40 of the Jenkins Subversion 
Plugin.

Does anyone know when Jenkins Subversion plugin 1.40 or later will be included 
in a Jenkins LTS release?

Best regards

David

restart broken build when certain string is detected?

[phil swenson]

I have a large Jenkins setup in Germany running against SVN in the US.
 Unfortunately, I get quite a few broken builds from SVN flaking out
(network drops I assume).  We've never had this problem with
everything being in the same datacenter.

I don't have a good solution to preventing the problem, so what I'd
like to do is rerun the job when a certain text string is detected
(org.tmatesoft.svn.core.SVNException: svn: E175002: REPORT
/svn/sag/!svn/vcc/default failed).

ideas?

thanks

Re: workspace deletion

[phil swenson]

The problem with this plugin is it cleans the workspace EVERY run.
This is simply a periodic maintenance task I want to run...

On Fri, Aug 3, 2012 at 10:48 AM, Stanley, Jason
 wrote:
> Install the "Workspace Cleanup Plugin"
>
> -Original Message-
> From: jenkinsci-users@googlegroups.com 
> [mailto:jenkinsci-users@googlegroups.com] On Behalf Of phil swenson
> Sent: Friday, August 03, 2012 12:23 PM
> To: jenkinsci-users
> Subject: workspace deletion
>
> Is there an easy way to delete all the workspaces on all nodes?
>
> I looked at the CLI - doesn't appear to help.
>
> thanks
>

Re: Jenkins doesn't work with Eclipse Mylyn

[Stepan Vavra]

I have some news regarding the Jenkins Mylyn integration.

I've found, the last version it worked was: 1.457. Looking at changelog
there is no record saying that any API changed in 1.458.
Therefore I think this is a bug.

Regards,
Stepan


On Sun, Aug 5, 2012 at 6:13 PM, Stepan Vavra  wrote:

>
>
> Hello,
>>
>> I haven't had time to discover where exactly the problem is, but Mylyn
>> Builds Connector (1.0.1 installed from
>> http://download.eclipse.org/mylyn/releases/latest) doesn't work with the
>> latest Jenkins.
>>
>> I don't even know if Jenkins supports the API Mylyn is using.
>> All I know is that Mylyn is able to communicate with Jeknins 1.447 but is
>> not able to communicate with the latest: 1.476.
>>
>> Is this some kind of regression that is intended?
>>
>> Best regards,
>
> Stepan Vavra
>>
>
>


-- 
Stepan Vavra

Tutorial: Jenkins Plugin to integrate Jenkins and Nexus Repository

[Marcel Birkner]

Hi,

I was looking for a way to add some metadata to build artifacts after they 
are deployed to Nexus / Artifactory. Since both tools offer a 
metadata-plugin for the Pro Editions I decided to write my own Jenkins 
Plugin that calls the Nexus REST API to add some metadata to the deployed 
artifact. Turns out, writing Jenkins plugins is not that hard thanks to 
some great documentation and the Maven hpi plugin that creates the project 
skeleton.

I wrote up my experience when developing the plugin and posted the project 
on github. 


   - Jenkins - Nexus 
Tutorial
   - Sourcecode on 
Github


I hope you find the article helpful in creating your own Jenkins plugins in 
the future.

Greetings,
Marcel

Re: Modifying a builds parameters in a system Groovy script

[Reuben Gow]

Hi Chris,

I've tried out the EnvInject plugin but it doesn't seem to be able to 
overwrite existing variables.

if I put:

return [ SOME_NEW_VAR: "blah" ]


then I can put the following the in the build step

 echo ${SOME_NEW_VAR}


and get the correct value.

However if I put:

return [ version_number: "blah" ]


where version_number is one of the build parameters the echo command 
returns the original passed in parameter.
 

On Friday, 3 August 2012 17:38:32 UTC+1, cjo wrote:
>
> Have a look at the EnvInject Plugin[1], to see if you are able plug your 
> script into it and get the correct results.
> look at "Prepare an environment for the run" section in the job config.
>
> The "Evaluated Groovy script" item might override them correctly.
>
> https://wiki.jenkins-ci.org/display/JENKINS/EnvInject+Plugin 
>
> Chris
>
> On Friday, August 3, 2012 4:52:17 PM UTC+1, Reuben Gow wrote:
>>
>> Hi,
>>
>> I have a job that takes a number of parameters (version_number, 
>> release_number, branch etc). This build can be built in a number of ways, 
>> some need to get the values of these parameters from other locations. the 
>> different modes are:
>>
>> 1) Manually - Take the passed in parameters
>> 2) SCM Change - take the parameter values from the last successful build 
>> of another job
>> 3) Timer - take the parameter values from the last successful build of 
>> another job
>> 4) Upstream Job - take the parameters passed to it from the upstream job.
>>
>> 1 is obviously no problem, as is 4 with the use of the Parameterized 
>> build plugin.
>>
>> I have written a Groovy script to retrieve the parameter values for cases 
>> 2 and 3 but can't find a way to apply these values to the variables used in 
>> the build step (execute shell ). I can create new parameters and access 
>> these as variables but I don't really like this method as it makes my shell 
>> script a bit ugly. 
>>
>> Does anyone know how to overwrite parameter values from within the Groovy 
>> script.
>>
>> Thanks
>>
>

RE: What is the latest LTS release?

[David Aldrich]

Thank you, I have 1.466.1 now.

David

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Nord, James
> Sent: 06 August 2012 10:14
> To: jenkinsci-users@googlegroups.com
> Subject: RE: What is the latest LTS release?
> 
> The "latest" symlink is a bit messed up.
> 
> You can download 1.466.1 from http://mirrors.jenkins-ci.org/war-
> stable/1.466.1/jenkins.war
> 
> /James
> 
> > -Original Message-
> > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> > us...@googlegroups.com] On Behalf Of David Aldrich
> > Sent: 06 August 2012 10:07
> > To: jenkinsci-users@googlegroups.com
> > Subject: RE: What is the latest LTS release?
> >
> > This is weird. I downloaded what I thought to be 1.466.1 and installed
> > it but Jenkins is now indicating 1.447.2.
> >
> > Also,
> >
> > http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war
> >
> > is now offline.
> >
> > Is it being updated?
> >
> > David
> >
> > > -Original Message-
> > > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> > > us...@googlegroups.com] On Behalf Of Richard Bywater
> > > Sent: 06 August 2012 09:41
> > > To: jenkinsci-users@googlegroups.com
> > > Subject: Re: What is the latest LTS release?
> > >
> > > 1.466.1 is the latest as far as I'm aware.
> > >
> > > I've had problems in the past with Manage Jenkins screen showing the
> > > correct next version - thought it had been fixed but perhaps there
> > > is some process that needs to run on a server somewhere to make it
> > > visible to that screen?
> > >
> > > Cheers
> > > Richard.
> > >
> > > On Mon, Aug 6, 2012 at 8:38 PM, David Aldrich
> > >  wrote:
> > > > Hi
> > > >
> > > >
> > > >
> > > > I am running Jenkins LTS release v.1.447.1.  My 'Manage Jenkins'
> > > > page shows that 1.447.2 is available.  But this Jenkins change log:
> > > >
> > > >
> > > >
> > > > http://jenkins-ci.org/changelog-stable
> > > >
> > > >
> > > >
> > > > shows that 1.466.1 is available.
> > > >
> > > >
> > > >
> > > > What is the latest LTS release please?
> > > >
> 
> 
> 
> 
> **
> 
> This message is confidential and intended only for the addressee. If you have
> received this message in error, please immediately notify the
> postmas...@nds.com and delete it from your system as well as any copies.
> The content of e-mails as well as traffic data may be monitored by NDS for
> employment and security purposes. To protect the environment please do
> not print this e-mail unless necessary.
> 
> NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18
> 4EX, United Kingdom. A company registered in England and Wales.
> Registered no. 3080780. VAT no. GB 603 8808 40-00
> **
> 
> 
> 
>  Click
> https://www.mailcontrol.com/sr/7asMPT!cXuzTndxI!oX7Urw!oDuajywvprh
> UpNUz+Rkjz4lio1sXVHqYZRG24R6sfw6!eiyrEJNRu1zEhLyH4w==  to report
> this email as spam.

RE: What is the latest LTS release?

[Nord, James]

The "latest" symlink is a bit messed up.

You can download 1.466.1 from 
http://mirrors.jenkins-ci.org/war-stable/1.466.1/jenkins.war

/James

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of David Aldrich
> Sent: 06 August 2012 10:07
> To: jenkinsci-users@googlegroups.com
> Subject: RE: What is the latest LTS release?
>
> This is weird. I downloaded what I thought to be 1.466.1 and installed it but
> Jenkins is now indicating 1.447.2.
>
> Also,
>
> http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war
>
> is now offline.
>
> Is it being updated?
>
> David
>
> > -Original Message-
> > From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> > us...@googlegroups.com] On Behalf Of Richard Bywater
> > Sent: 06 August 2012 09:41
> > To: jenkinsci-users@googlegroups.com
> > Subject: Re: What is the latest LTS release?
> >
> > 1.466.1 is the latest as far as I'm aware.
> >
> > I've had problems in the past with Manage Jenkins screen showing the
> > correct next version - thought it had been fixed but perhaps there is
> > some process that needs to run on a server somewhere to make it
> > visible to that screen?
> >
> > Cheers
> > Richard.
> >
> > On Mon, Aug 6, 2012 at 8:38 PM, David Aldrich
> >  wrote:
> > > Hi
> > >
> > >
> > >
> > > I am running Jenkins LTS release v.1.447.1.  My 'Manage Jenkins'
> > > page shows that 1.447.2 is available.  But this Jenkins change log:
> > >
> > >
> > >
> > > http://jenkins-ci.org/changelog-stable
> > >
> > >
> > >
> > > shows that 1.466.1 is available.
> > >
> > >
> > >
> > > What is the latest LTS release please?
> > >




**
This message is confidential and intended only for the addressee. If you have 
received this message in error, please immediately notify the 
postmas...@nds.com and delete it from your system as well as any copies. The 
content of e-mails as well as traffic data may be monitored by NDS for 
employment and security purposes. To protect the environment please do not 
print this e-mail unless necessary.

NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, 
United Kingdom. A company registered in England and Wales. Registered no. 
3080780. VAT no. GB 603 8808 40-00
**

RE: What is the latest LTS release?

[David Aldrich]

This is weird. I downloaded what I thought to be 1.466.1 and installed it but 
Jenkins is now indicating 1.447.2.

Also, 

http://mirrors.jenkins-ci.org/war-stable/latest/jenkins.war

is now offline.

Is it being updated?

David

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Richard Bywater
> Sent: 06 August 2012 09:41
> To: jenkinsci-users@googlegroups.com
> Subject: Re: What is the latest LTS release?
> 
> 1.466.1 is the latest as far as I'm aware.
> 
> I've had problems in the past with Manage Jenkins screen showing the
> correct next version - thought it had been fixed but perhaps there is some
> process that needs to run on a server somewhere to make it visible to that
> screen?
> 
> Cheers
> Richard.
> 
> On Mon, Aug 6, 2012 at 8:38 PM, David Aldrich
>  wrote:
> > Hi
> >
> >
> >
> > I am running Jenkins LTS release v.1.447.1.  My 'Manage Jenkins' page
> > shows that 1.447.2 is available.  But this Jenkins change log:
> >
> >
> >
> > http://jenkins-ci.org/changelog-stable
> >
> >
> >
> > shows that 1.466.1 is available.
> >
> >
> >
> > What is the latest LTS release please?
> >
> >
> >
> > Best regards
> >
> >
> >
> > David
> >
> >
> 
> 
>  Click
> https://www.mailcontrol.com/sr/kFwHUKJdBt7TndxI!oX7Us3fUQZbLcSFGYp
> pmtP+VK+omj8RJ++B1T74JDnEXpDdfw6!eiyrEJMzZ1ZqAaZkbg==  to report
> this email as spam.

RE: What is the latest LTS release?

[David Aldrich]

Thanks Richard

David

> -Original Message-
> From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-
> us...@googlegroups.com] On Behalf Of Richard Bywater
> Sent: 06 August 2012 09:41
> To: jenkinsci-users@googlegroups.com
> Subject: Re: What is the latest LTS release?
> 
> 1.466.1 is the latest as far as I'm aware.
> 
> I've had problems in the past with Manage Jenkins screen showing the
> correct next version - thought it had been fixed but perhaps there is some
> process that needs to run on a server somewhere to make it visible to that
> screen?
> 
> Cheers
> Richard.
> 
> On Mon, Aug 6, 2012 at 8:38 PM, David Aldrich
>  wrote:
> > Hi
> >
> >
> >
> > I am running Jenkins LTS release v.1.447.1.  My 'Manage Jenkins' page
> > shows that 1.447.2 is available.  But this Jenkins change log:
> >
> >
> >
> > http://jenkins-ci.org/changelog-stable
> >
> >
> >
> > shows that 1.466.1 is available.
> >
> >
> >
> > What is the latest LTS release please?
> >
> >
> >
> > Best regards
> >
> >
> >
> > David
> >
> >
> 
> 
>  Click
> https://www.mailcontrol.com/sr/kFwHUKJdBt7TndxI!oX7Us3fUQZbLcSFGYp
> pmtP+VK+omj8RJ++B1T74JDnEXpDdfw6!eiyrEJMzZ1ZqAaZkbg==  to report
> this email as spam.

Re: What is the latest LTS release?

[Richard Bywater]

1.466.1 is the latest as far as I'm aware.

I've had problems in the past with Manage Jenkins screen showing the
correct next version - thought it had been fixed but perhaps there is
some process that needs to run on a server somewhere to make it
visible to that screen?

Cheers
Richard.

On Mon, Aug 6, 2012 at 8:38 PM, David Aldrich
 wrote:
> Hi
>
>
>
> I am running Jenkins LTS release v.1.447.1.  My ‘Manage Jenkins’ page shows
> that 1.447.2 is available.  But this Jenkins change log:
>
>
>
> http://jenkins-ci.org/changelog-stable
>
>
>
> shows that 1.466.1 is available.
>
>
>
> What is the latest LTS release please?
>
>
>
> Best regards
>
>
>
> David
>
>

What is the latest LTS release?

[David Aldrich]

Hi

I am running Jenkins LTS release v.1.447.1.  My 'Manage Jenkins' page shows 
that 1.447.2 is available.  But this Jenkins change log:

http://jenkins-ci.org/changelog-stable

shows that 1.466.1 is available.

What is the latest LTS release please?

Best regards

David