Error getting while installing StarTeam Plug in
Hi All, I'm new to Jenkins.Today only i have started to learn CI by using Jenkins. My current project i'm using Starteam so that I tried to download the starteam plugin in Jenkins , but i'm getting below error Sep 13, 2012 5:30:02 PM hudson.model.UpdateCenter$DownloadJob run SEVERE: Failed to install StarTeam hudson.util.IOException2: Failed to download from http://updates.jenkins-ci.org/download/plugins/starteam/0.6.8/starteam.hpi at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:716) at hudson.model.UpdateCenter$DownloadJob._run(UpdateCenter.java:1052) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1202) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1031) at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.net.ConnectException: Connection timed out: connect at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source) at java.lang.reflect.Constructor.newInstance(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection$6.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:686) ... 9 more Caused by: java.net.ConnectException: Connection timed out: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at sun.net.NetworkClient.doConnect(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.openServer(Unknown Source) at sun.net.www.http.HttpClient.init(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.http.HttpClient.New(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source) at sun.net.www.protocol.http.HttpURLConnection.getHeaderField(Unknown Source) at java.net.URLConnection.getHeaderFieldInt(Unknown Source) at java.net.URLConnection.getContentLength(Unknown Source) at hudson.model.UpdateCenter$UpdateCenterConfiguration.download(UpdateCenter.java:685) ... 9 more could any one help me to get this working. Regards Anba
Re: Do these features already exist?
Hi Xavier, Have you tried the Build Timeout plug-in (https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin) yet? It might help you with detecting blocked jobs. Regards, Fred On Thursday, September 13, 2012 12:48:20 PM UTC+2, Xavier Nodet wrote: Hi all, I've been using Jenkins for a year now, and I'm missing the following features... Do they exist in a plugin that I missed? More context is available at http://xnodet.blogspot.fr/2012/09/suggestions-for-jenkins-on-multi.html Thanks. Detect stale jobs We sometimes have jobs that stop running (no new run is triggered, or no available nodes). This is of course not intended, and it would be nice to be able to detect those easily. I suppose that adding a 'Last build' column to the list view, that would display the time since the job entered its current state, would be nice. Something like 'Ended 8.6 hr' or 'Queued 1.3 hr' or 'Started 12 min'... Then I'd know that if the code changed 3 hours ago, I shouldn't see any number larger than 3 hours... Detect hung jobs We have many jobs running, typically 20 to 30 simultaneously. And some builds last for several hours. It happens that tests hang, or are abnormally slow. These situations should be detected as soon as possible for investigation. Unfortunately, the 'Build History' list is not very helpful, for two reasons. It has too few jobs for us: with 50 builds, only the last 5 hours are covered, which is less than the duration of many of our builds. But then if this limit was increased, we'd probably need a list of 200 or so jobs, which would not be easy to handle. I would thus suggest to allow filtering on the 'building' status. When this flag would be set, the 'Build History' would only display the jobs that are currently being built. A view 'by revision' I often need to check if a given revision of the source has been built by a given job, or what is the latest revision that is good on a set of jobs. For example, I may want to merge this revision to some 'stable' branch for other teams to use. I think that a grid view with the following attributes would be very useful for this: each line is a commit id or SVN revision, each column is a job, each cell is blue, red or gray (or even empty if this revision has not yet been part of a run of the job, or the run is not finished yet). Do you think these would be useful additions? -- Xavier Nodet
Re: retry build upon failure?
see http://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin 2012/9/14 Ed Young e...@summitbid.com Is it possible to retry a build upon a failure? Maybe with a retry count?
try to compile from source, caught an error. What's wrong?
I got the following errors and can't find documentation about them. What am I doing wrong? The error occurs is in Jenkins Core (compiled in the github jenkins root folder on master, with mvn -X clean install, more details after log paste): [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/erikb85/coding/jenkins/core/src/main/java/hudson/DescriptorExtensionList.java:[86,35] incompatible types; no instance(s) of type variable(s) D exist so that hudson.DescriptorExtensionListT,D conforms to hudson.DescriptorExtensionListT,D found : Dhudson.DescriptorExtensionListT,D required: hudson.DescriptorExtensionListT,D [INFO] 1 error [INFO] - [INFO] [INFO] Reactor Summary: [INFO] [INFO] Jenkins main module ... SUCCESS [2.736s] [INFO] Jenkins CLI ... SUCCESS [5.360s] [INFO] Jenkins core .. FAILURE [27.288s] [INFO] Maven Integration plugin .. SKIPPED [INFO] Jenkins war ... SKIPPED [INFO] Test harness for Jenkins and plugins .. SKIPPED [INFO] Jenkins UI sample plugin .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 37.714s [INFO] Finished at: Fri Sep 14 13:43:29 CEST 2012 [INFO] Final Memory: 45M/408M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (default-compile) on project jenkins-core: Compilation failure [ERROR] /home/erikb85/coding/jenkins/core/src/main/java/hudson/DescriptorExtensionList.java:[86,35] incompatible types; no instance(s) of type variable(s) D exist so that hudson.DescriptorExtensionListT,D conforms to hudson.DescriptorExtensionListT,D [ERROR] found : Dhudson.DescriptorExtensionListT,D [ERROR] required: hudson.DescriptorExtensionListT,D [ERROR] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (default-compile) on project jenkins-core: Compilation failure /home/erikb85/coding/jenkins/core/src/main/java/hudson/DescriptorExtensionList.java:[86,35] incompatible types; no instance(s) of type variable(s) D exist so that hudson.DescriptorExtensionListT,D conforms to hudson.DescriptorExtensionListT,D found : Dhudson.DescriptorExtensionListT,D required: hudson.DescriptorExtensionListT,D at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure /home/erikb85/coding/jenkins/core/src/main/java/hudson/DescriptorExtensionList.java:[86,35] incompatible types; no instance(s) of type variable(s) D exist so that hudson.DescriptorExtensionListT,D conforms to hudson.DescriptorExtensionListT,D found : Dhudson.DescriptorExtensionListT,D required: hudson.DescriptorExtensionListT,D at
RE: retry build upon failure?
Or https://wiki.jenkins-ci.org/display/JENKINS/Retry+Failed+Builds+Plugin From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof Sent: Friday, September 14, 2012 6:16 AM To: jenkinsci-users@googlegroups.com Subject: Re: retry build upon failure? see http://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin 2012/9/14 Ed Young e...@summitbid.commailto:e...@summitbid.com Is it possible to retry a build upon a failure? Maybe with a retry count?
Coverity plugin
Hello, I am trying to make Jenkins and Coverity Static Analysis work together for projects in C/C++. I have a Jenkins Master on an Ubuntu 12.04 and a Jenkins Slave and Coverity both on the same Debian Lenny. My version of Jenkins is the 1.466.1. The builds ont Jenkins are triggered by Gerrit: when a change is pushed on a project, the Jenkins master tells the slave to download the sources and build the project. This part alone works fine. I also managed to make Coverity SA work on its own: the tools cov-build, cov-analyze and cov-commit-defects are working. Now, I want to integrate Coverity with Jenkins: I installed the latest version of *this plugin*https://wiki.jenkins-ci.org/display/JENKINS/Coverity+Plugin. In the configuration of my project on Jenkins, I added a Coverity post-build action, specified an Coverity Integrity Manager Instance, a coverity project and stream. I want Jenkins to perform a Coverity build, analysis and commit. According to the help window of this option, Jenkins will automatically monitor the build using cov-build, then invoke cov-analyze and cov-commit-defects. Then, when a build is triggered, Jenkins successfully connect to the slave who downloads and builds the project, but the cov-analyze is launched and it fails because of the absence of intermediate directory. As I understand it, cov-build is never launched and does not monitor the build, therefore the intermediate directory needed for the analysis is never created. Here is log of one of my failed builds: Triggered by Gerrit: http://gerrit.server1/22 Building remotely on Jenkins Coverity in workspace /home/coverity/workspace/HelloWorldC Checkout:HelloWorldC / /home/coverity/workspace/HelloWorldC - hudson.remoting.Channel@785b38d6:Jenkins Coverity Using strategy: Gerrit Trigger Last Built Revision: Revision 5540c6e5802a75d0ba0ccb3463deed2a7bca9424 (master) Fetching changes from 1 remote Git repository Fetching upstream changes from ssh://jenkins@server1:29418/HelloWorldC.git Commencing build of Revision 5540c6e5802a75d0ba0ccb3463deed2a7bca9424 (master) Checking out Revision 5540c6e5802a75d0ba0ccb3463deed2a7bca9424 (master) [Coverity] cmd so far is: [cov-analyze, --dir, /home/coverity/coverity/temp-550893439800959750.tmp] [HelloWorldC] $ cov-analyze --dir /home/coverity/coverity/temp-550893439800959750.tmp [ERROR] This script reads input from the Intermediate directory, and the specified directory /home/coverity/coverity/temp-550893439800959750.tmp/c/emit does not exist. Please read the documentation to determine the appropriate ordering in which to run the Coverity Prevent commands. [Coverity] cov-analyze returned 1, aborting... [Coverity] deleting intermediate directory Build step 'Coverity' changed build result to FAILURE Build step 'Coverity' marked build as failure Finished: FAILURE Does someone have a similar setup? What am i doing wrong? Thank you for your help
*.pom file is not deployed in artifactory with jenkins artifactory plugin
Dear list, I'm building some archetypes from projects, and i would deploy it to my artifactory. Actually i have a maven job with multi step maven build. The first step: goals : clean archetype:create-from-project then (regardless to previous step): goals: install pom : target/generated-sources/archetype/pom.xml this produces the archetype jar here: target/generated-sources/archetype/target/my-archetype.jar So, after the artifactory deploy plugin (Jenkins Artifactory Pluginhttp://wiki.jenkins-ci.org/display/JENKINS/Artifactory+Plugin v2.1.2) should take care of deploy to the specified repository. I just specified this: Include Patterns **.jar, **.pom (but I aldo tryed leaving that field blank) The issue is this: The artifact is deployed .. but the *.pom is not deployed and there is no my-archetype.pom in artifactory. This does not allow to eclipse to create the project from my-archetype. Could not resolve archetype org.test.maven.archetype:my-archetype.jar:0.1.5 from any of the configured repositories. Could not resolve artifact org.test.maven.archetype:my-archetype.jar:pom:0.1.5 Missing org.test.maven.archetype:my-archetype.jar:pom:0.1.5 How can i configure the plugin to deploy also the *.pom file? This issue caused me several troubles also with other projects, and i had to abandon the usage of that plugin and use the maven deploy goal. Thank you! Jenkins version 1.466.1 artifactory version 2.6.3 - regards Federico
Re: Jenkins vs Hudson: Complier warnings
Issues *JENKINS-15169* https://issues.jenkins-ci.org/browse/JENKINS-15169 logged.
Build history bar modification
Hi all. Does Jenkins provide ability to change job bar with history builds? Now it contain 2 columns: number of build end date/time. But I want to see there, for example, number of build and svn revision. Is it possible? Regards.
Re: Build history bar modification
There is a build description setter plugin that we've used in the past to add a description to each build based on information which the plugin parses from the build log file. We used it to report the generated version number of the build. That doesn't add an additional column, rather it adds another row below each build's existing build number and end date/time. Mark Waite https://wiki.jenkins-ci.org/display/JENKINS/Description+Setter+Plugin From: makiselev kiselev.maxi...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Friday, September 14, 2012 7:16 AM Subject: Build history bar modification Hi all. Does Jenkins provide ability to change job bar with history builds? Now it contain 2 columns: number of build end date/time. But I want to see there, for example, number of build and svn revision. Is it possible? Regards.
RE: try to compile from source, caught an error. What's wrong?
What version of maven are you using? Sent from my Windows Phone -- From: Erik Bernoth Sent: 9/14/2012 4:49 AM To: jenkinsci-users@googlegroups.com Subject: try to compile from source, caught an error. What's wrong? I got the following errors and can't find documentation about them. What am I doing wrong? The error occurs is in Jenkins Core (compiled in the github jenkins root folder on master, with mvn -X clean install, more details after log paste): [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/erikb85/coding/jenkins/core/src/main/java/hudson/DescriptorExtensionList.java:[86,35] incompatible types; no instance(s) of type variable(s) D exist so that hudson.DescriptorExtensionListT,D conforms to hudson.DescriptorExtensionListT,D found : Dhudson.DescriptorExtensionListT,D required: hudson.DescriptorExtensionListT,D [INFO] 1 error [INFO] - [INFO] [INFO] Reactor Summary: [INFO] [INFO] Jenkins main module ... SUCCESS [2.736s] [INFO] Jenkins CLI ... SUCCESS [5.360s] [INFO] Jenkins core .. FAILURE [27.288s] [INFO] Maven Integration plugin .. SKIPPED [INFO] Jenkins war ... SKIPPED [INFO] Test harness for Jenkins and plugins .. SKIPPED [INFO] Jenkins UI sample plugin .. SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 37.714s [INFO] Finished at: Fri Sep 14 13:43:29 CEST 2012 [INFO] Final Memory: 45M/408M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (default-compile) on project jenkins-core: Compilation failure [ERROR] /home/erikb85/coding/jenkins/core/src/main/java/hudson/DescriptorExtensionList.java:[86,35] incompatible types; no instance(s) of type variable(s) D exist so that hudson.DescriptorExtensionListT,D conforms to hudson.DescriptorExtensionListT,D [ERROR] found : Dhudson.DescriptorExtensionListT,D [ERROR] required: hudson.DescriptorExtensionListT,D [ERROR] - [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.5:compile (default-compile) on project jenkins-core: Compilation failure /home/erikb85/coding/jenkins/core/src/main/java/hudson/DescriptorExtensionList.java:[86,35] incompatible types; no instance(s) of type variable(s) D exist so that hudson.DescriptorExtensionListT,D conforms to hudson.DescriptorExtensionListT,D found : Dhudson.DescriptorExtensionListT,D required: hudson.DescriptorExtensionListT,D at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure /home/erikb85/coding/jenkins/core/src/main/java/hudson/DescriptorExtensionList.java:[86,35] incompatible types; no instance(s) of type
Re: Will reducing the Max # of builds to keep automatically delete old builds?
the disk usage plugin is installed and is what I've been using to determine which projects (mine) are the biggest disk hogs. One of my builds uses 18 GB of space. The next largest one is 1GB. The reason it uses so much space is because I want keep 50 old builds behind so that if I notice that test coverage has dropped, for example, I can go back and see where that happened. I'm not sure of any other way to track this kind of thing without keeping a large number of builds. On Fri, Sep 14, 2012 at 6:11 AM, Lars Nordin lnor...@internap.com wrote: -Original Message- From: Ed Young Scott, kicking off the build seems to have deleted the old builds, although I'm not seeing the diskspace usage go down the way I'm hoping. I have a lot of builds to reconfigure and kick off though so this make some time. -Original Message- You might want to install the disk usage plug-in and it help you find what jobs and builds are consuming the most disk space. https://wiki.jenkins-ci.org/display/JENKINS/Disk+Usage+Plugin -- - Ed
Re: Pipelines in Jenkins...
Hello, I have similar case and I get the theory but cannot make it work. I have job A which is git poll job and as post build action it triggers build B using parametrized trigger plugin with predefined parameter: gitCommit=$GIT_COMMIT But I don't know how to read this parameter in job B. env command in shell script doesn't show it. I tried various combinations with e.g. gitCommit=someConstant and with Pass through git commit but just can't make it working. Would someone share the details of how to pass id (at best git commit id) down the pipeline? thanks Lukasz On Tuesday, February 21, 2012 12:55:32 AM UTC+1, Geoff Bullen wrote: The join plugin doesn't work with the build pipeline plugin. However you can achieve pretty much the same thing by wrapping up multiple jobs a build steps using the parametrised triggers plugin In terms of passing artefacts down a pipeline of jobs, what I tend to do is pass a unique identifier along the pipeline that is used to publish the built artefact early on and to retrieve built artefacts later on. You can use the copy artefact plugin to pass built artefacts around as well
Re: Do these features already exist?
Hi Fred, Yes, I know about this plugin. But it will only abort the build, instead of notifying me. And this may not always be the correct option. So I would have to use a very large timeout... Thanks. -- Xavier Nodet On Fri, Sep 14, 2012 at 12:25 PM, Fred G fred.g...@googlemail.com wrote: Hi Xavier, Have you tried the Build Timeout plug-in ( https://wiki.jenkins-ci.org/display/JENKINS/Build-timeout+Plugin) yet? It might help you with detecting blocked jobs. Regards, Fred On Thursday, September 13, 2012 12:48:20 PM UTC+2, Xavier Nodet wrote: Hi all, I've been using Jenkins for a year now, and I'm missing the following features... Do they exist in a plugin that I missed? More context is available at http://xnodet.blogspot.fr/** 2012/09/suggestions-for-**jenkins-on-multi.htmlhttp://xnodet.blogspot.fr/2012/09/suggestions-for-jenkins-on-multi.html Thanks. Detect stale jobs We sometimes have jobs that stop running (no new run is triggered, or no available nodes). This is of course not intended, and it would be nice to be able to detect those easily. I suppose that adding a 'Last build' column to the list view, that would display the time since the job entered its current state, would be nice. Something like 'Ended 8.6 hr' or 'Queued 1.3 hr' or 'Started 12 min'... Then I'd know that if the code changed 3 hours ago, I shouldn't see any number larger than 3 hours... Detect hung jobs We have many jobs running, typically 20 to 30 simultaneously. And some builds last for several hours. It happens that tests hang, or are abnormally slow. These situations should be detected as soon as possible for investigation. Unfortunately, the 'Build History' list is not very helpful, for two reasons. It has too few jobs for us: with 50 builds, only the last 5 hours are covered, which is less than the duration of many of our builds. But then if this limit was increased, we'd probably need a list of 200 or so jobs, which would not be easy to handle. I would thus suggest to allow filtering on the 'building' status. When this flag would be set, the 'Build History' would only display the jobs that are currently being built. A view 'by revision' I often need to check if a given revision of the source has been built by a given job, or what is the latest revision that is good on a set of jobs. For example, I may want to merge this revision to some 'stable' branch for other teams to use. I think that a grid view with the following attributes would be very useful for this: each line is a commit id or SVN revision, each column is a job, each cell is blue, red or gray (or even empty if this revision has not yet been part of a run of the job, or the run is not finished yet). Do you think these would be useful additions? -- Xavier Nodet
Re: Will reducing the Max # of builds to keep automatically delete old builds?
Hi Ed, Try the Workspace Cleanup Plugin and configure it to wipe out your workspace after the build is done. cheers, Chris On 14/09/2012 14:39, Ed Young wrote: the disk usage plugin is installed and is what I've been using to determine which projects (mine) are the biggest disk hogs. One of my builds uses 18 GB of space. The next largest one is 1GB. The reason it uses so much space is because I want keep 50 old builds behind so that if I notice that test coverage has dropped, for example, I can go back and see where that happened. I'm not sure of any other way to track this kind of thing without keeping a large number of builds. On Fri, Sep 14, 2012 at 6:11 AM, Lars Nordinlnor...@internap.com wrote: -Original Message- From: Ed Young Scott, kicking off the build seems to have deleted the old builds, although I'm not seeing the diskspace usage go down the way I'm hoping. I have a lot of builds to reconfigure and kick off though so this make some time. -Original Message- You might want to install the disk usage plug-in and it help you find what jobs and builds are consuming the most disk space. https://wiki.jenkins-ci.org/display/JENKINS/Disk+Usage+Plugin -- Simplistix - Content Management, Batch Processing Python Consulting - http://www.simplistix.co.uk
Re: retry build upon failure?
I installed the Naginator Plugin (v1.8) because the retry failed build plugin indicated that it was deprecated in favor of the Naginatore plugin. It doesn't seem to be working the way I expect it to however. I configured it to simply Retry build after failure up to 3 times, with all other defaults, but after a failure there is no retry. I configured it for a fixed delay and it still did not retry. It seems like a very simple configuration and the build is a hard failure (test failures) so I can't tell where I'm going wrong. Using Jenkins 1.436. On Fri, Sep 14, 2012 at 5:59 AM, William Soula william.so...@drillinginfo.com wrote: Or https://wiki.jenkins-ci.org/display/JENKINS/Retry+Failed+Builds+Plugin From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of nicolas de loof Sent: Friday, September 14, 2012 6:16 AM To: jenkinsci-users@googlegroups.com Subject: Re: retry build upon failure? see http://wiki.jenkins-ci.org/display/JENKINS/Naginator+Plugin 2012/9/14 Ed Young e...@summitbid.com Is it possible to retry a build upon a failure? Maybe with a retry count? -- - Ed
Error while deploying to Message Broker
I have an ant build script that will build and deploy the bar file to a broker. When I execute the ant file from cmd promp both actions are successful. But when I try to invoke that ant script from Jenkins I am seeing below exeption. Can anybody please help. I am stuck , no clue where to look for the exact error. I checked the QMGR logs , broker logs. Could not find any exceptions. DO I need to do any special settings to connect to broker? - MQSI 7.0.0.0 C:\Program Files (x86)\IBM\MQSI\7.0 BIP1044I: Connecting to the queue manager... BIP1046E: Unable to connect with the queue manager (*com.ibm.mq*http://com.ibm.mq.mq/.MQQueueManager). The utility encountered a problem while attempting to connect to the queue manager to put a message to the broker's request queue. Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the queue manager is running and that the current user is able to access the queues beginning SYSTEM.BROKER. If this error text includes an MQ reason code, look up the meaning behind the error in the Application Programming Reference guide and proceed as appropriate. Build step 'Execute Windows batch command' marked build as failure Finished: FAILURE
Re: Error while deploying to Message Broker
I tried to separate both build and deploy as 2 steps. Build will be done with ant script and deploy will be done via 'Execute Windows batch command' . But same issue. On Fri, Sep 14, 2012 at 3:05 PM, radm rmasa...@gmail.com wrote: I have an ant build script that will build and deploy the bar file to a broker. When I execute the ant file from cmd promp both actions are successful. But when I try to invoke that ant script from Jenkins I am seeing below exeption. Can anybody please help. I am stuck , no clue where to look for the exact error. I checked the QMGR logs , broker logs. Could not find any exceptions. DO I need to do any special settings to connect to broker? - MQSI 7.0.0.0 C:\Program Files (x86)\IBM\MQSI\7.0 BIP1044I: Connecting to the queue manager... BIP1046E: Unable to connect with the queue manager (*com.ibm.mq*http://com.ibm.mq.mq/.MQQueueManager). The utility encountered a problem while attempting to connect to the queue manager to put a message to the broker's request queue. Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the queue manager is running and that the current user is able to access the queues beginning SYSTEM.BROKER. If this error text includes an MQ reason code, look up the meaning behind the error in the Application Programming Reference guide and proceed as appropriate. Build step 'Execute Windows batch command' marked build as failure Finished: FAILURE
Re: Error while deploying to Message Broker
Somehow now it is geting connected to QMgr , broker. I installed ENVInject plugin. After that I am able to connect to Queue manager and deployed to broker successfully. May be it is just a coincident or that plugin has done something. Good thing is it is working now. On Friday, September 14, 2012 3:05:06 PM UTC-7, radm wrote: I have an ant build script that will build and deploy the bar file to a broker. When I execute the ant file from cmd promp both actions are successful. But when I try to invoke that ant script from Jenkins I am seeing below exeption. Can anybody please help. I am stuck , no clue where to look for the exact error. I checked the QMGR logs , broker logs. Could not find any exceptions. DO I need to do any special settings to connect to broker? - MQSI 7.0.0.0 C:\Program Files (x86)\IBM\MQSI\7.0 BIP1044I: Connecting to the queue manager... BIP1046E: Unable to connect with the queue manager (*com.ibm.mq*http://com.ibm.mq.mq/.MQQueueManager). The utility encountered a problem while attempting to connect to the queue manager to put a message to the broker's request queue. Ensure that the correct connection parameters have been supplied to the utility. Also ensure that the queue manager is running and that the current user is able to access the queues beginning SYSTEM.BROKER. If this error text includes an MQ reason code, look up the meaning behind the error in the Application Programming Reference guide and proceed as appropriate. Build step 'Execute Windows batch command' marked build as failure Finished: FAILURE
Re: HTML Publishing archiving at PROJECT level???
If you want to archive only one html file why do not use the builtin artifact publisher for that? Garami Gábor gabor.gar...@hron.me Skype: hron84 Tel: +36 20 235 9621 Sent from my T-Mobile G2 Ezt a levelet telefonról adták fel, ékezethibákat tartalmazhat. 2012.09.13. 18:24, mikemil ask.mi...@gmail.com ezt írta: We have been using Jenkins for a while and we have an ant task that generates an html report - a single html file. Lately we started having some build errors that were tracked back to space issues on the hard drive. As part of the research, we noticed that Jenkins/HTML Publisher logs this message about archiving at the PROJECT level and guess what - it is archiving the entire build folder and EVERYTHING underneath, which is over 400MB. (I thought) I have the HTML Publisher configured to point to a this single html file that I want reported on our build page. Why is EVERYTHING being archived to our .hudson\jobs\TrunkDaily\htmlreports\Validator_Report folder? The job is Trunk Daily and we have what we call the 'Validator Report' which generates validator.html - and we want only that copied or shown on the build page but don't really need all this 'archiving'. I haven't seen any documentation on the publisher other than the one page in the wiki and that doesn't cover any of this. Ideas or suggestions??? Thanks!
RE: Failed to check out on jenkins slave
As same user as Jenkins? Garami Gábor gabor.gar...@hron.me Skype: hron84 Tel: +36 20 235 9621 Sent from my T-Mobile G2 Ezt a levelet telefonról adták fel, ékezethibákat tartalmazhat. 2012.09.13. 14:02, Levin, Ilya ilya.le...@hp.com ezt írta: ** ** I’m quoting (sorry if I didn’t make myself clear). The subversion work fine from the command line. ** ** *From:* jenkinsci-users@googlegroups.com [mailto: jenkinsci-users@googlegroups.com] *On Behalf Of * matthew.web...@diamond.ac.uk *Sent:* יום ה 13 ספטמבר 2012 14:53 *To:* jenkinsci-users@googlegroups.com *Subject:* RE: Failed to check out on jenkins slave ** ** Are you saying that was the problem, or are you just quoting and asking for clarification? My list was a list of possible causes of your problem, not a list of things you have to do. Did you try the subversion checkout from the command line? Get it working there first before Jenkins. ** ** *From:* jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] *On Behalf Of *Levin, Ilya *Sent:* 13 September 2012 12:37 *To:* jenkinsci-users@googlegroups.com *Subject:* RE: Failed to check out on jenkins slave ** ** Jenkins on the slave needs to accept the subversion server’s key Isn’t it something that should be defined by the master. I kinda thought that after I connect the slave to the master I’m good to go, Are there any additional things I need to do on the slave after connecting it? thanks ** ** -- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd. Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message. Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom ** **
IPv6 Support/Compliance
Hi List, Does Jenkins support/Comply with IPv6 ? Thanks, -Kamal.
