jenkins with ldap authentication
Hello, I'm trying to use ldap in my Jenkins (v 1.485). I configured the ldap connection under the security relam, and it seems that the connection with the ldap server was established. I did a little test and entered 2 users, a false one and an existing one. As you can see Jenkins identified this - which tells me that the connection exist. [cid:image001.png@01CDE9A7.D82F4840] HOWEVER when I try to log in as the legitimate user, Jenkins thinks for about 5 min and then do nothing - doesn't login. Moreover Jenkins doesn't log anything as if nothing happened - without the log I cannot understand what went wrong. Any ideas? Thanks. ilya inline: image001.png
m2release 0.10.0 (Not yet released) - duedate
Hello, I'm interessted at release 0.10.0 of m2reelase plugin. I built from source code and tried it. I have the suggestions below about the Fix Add ability to specify number of release builds to keep: - As can you see at image there is a error when you click on help image: Failed to load help image: Not found - Default number of successful release builds to keep to -1. What is the due date to perform 0.10.0 release? I'm a java developer how could i help this plugin project? -- Marcus Vinicius A. Silva *P* *ANTES DE IMPRIMIR pense em sua responsabilidade e compromisso com o MEIO AMBIENTE.* image001.png
RE: m2release 0.10.0 (Not yet released) - duedate
Hi Marcus, There are a couple of outstanding pull requests that I need to pull in before the release - one of which is for a defect with the release builds to keep. -1 as a default doesn't make sense (it is really 0 as you are marking zero builds to keep). If there are any features you would like that are missing the best way is to create a pull request and a JIRA issue. Regards, /James From: jenkinsci-...@googlegroups.com [mailto:jenkinsci-...@googlegroups.com] On Behalf Of Marcus Vinicius Sent: 03 January 2013 11:08 To: jenkinsci-users@googlegroups.com; jenkinsci-...@googlegroups.com Subject: m2release 0.10.0 (Not yet released) - duedate Hello, I'm interessted at release 0.10.0 of m2reelase plugin. I built from source code and tried it. I have the suggestions below about the Fix Add ability to specify number of release builds to keep: - As can you see at image there is a error when you click on help image: Failed to load help image: Not found - Default number of successful release builds to keep to -1. What is the due date to perform 0.10.0 release? I'm a java developer how could i help this plugin project? [cid:image001.png@01CDE9AB.ACA227C0] -- Marcus Vinicius A. Silva P ANTES DE IMPRIMIR pense em sua responsabilidade e compromisso com o MEIO AMBIENTE. ** 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 ** inline: image001.png
Jenkins-CLI does not work with Jenkins behind reverse proxy
When trying to contact a Jenkins (1.447.2) behind a reverse proxy via Jenkins CLI, there is no response until Reverse Proxy timeout is reached and then the connection gets closed. Debugging into it, the CLI hangs on the line where it is reading the input stream. After the connection was closed, the server's answer Starting HTTP duplex channel can be read from that stream. The Client terminates with an EOFException: Exception in thread main java.io.EOFException: unexpected stream termination at hudson.remoting.Channel.init(Channel.java:408) at hudson.remoting.Channel.init(Channel.java:366) at hudson.remoting.Channel.init(Channel.java:327) at hudson.remoting.Channel.init(Channel.java:323) at hudson.remoting.Channel.init(Channel.java:311) at hudson.cli.CLI.connectViaHttp(CLI.java:124) at hudson.cli.CLI.init(CLI.java:107) at hudson.cli.CLI.init(CLI.java:85) at hudson.cli.CLI._main(CLI.java:300) at hudson.cli.CLI.main(CLI.java:245) The server does not log any errors and judging from the input stream's content is was contacted properly. The reverse proxy log only shows that the timeout has been reached and the connection is therefore closed: (70007)The timeout specified has expired: Error reading chunk Is this a known issue and is there any way to establish a connection through a reverse proxy?
Re: Upgrading from Hudson Windows 1.395 to Jenkins
Hello KK, I have bulk of Jobs in Hudson . And want to migrate From Hudson (Windows) to Jenkins ( Windows) with all the JOBS imported. So i have followed the belwo link which is not happening... Can u please give me the detailed picture how to Migrate ? https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins Very Urgent reply required ASAP.thanks a lottt On Tuesday, 29 March 2011 21:45:35 UTC+5:30, Kohsuke Kawaguchi wrote: On 03/29/2011 08:23 AM, mke wrote: Does anyone have a procedure to convert from Hudson 1.395 on Windows to Jenkins? The issue list is for automated notification use and not for interactive discussion. For that, please use the users list. The instruction for upgrade is in http://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/
Re: Upgrading from Hudson Windows 1.395 to Jenkins
What version are you upgrading from? On Thu, Jan 3, 2013 at 5:51 AM, prathima chowdary chowdary.gprath...@gmail.com wrote: Hello KK, I have bulk of Jobs in Hudson . And want to migrate From Hudson (Windows) to Jenkins ( Windows) with all the JOBS imported. So i have followed the belwo link which is not happening... Can u please give me the detailed picture how to Migrate ? https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins Very Urgent reply required ASAP.thanks a lottt On Tuesday, 29 March 2011 21:45:35 UTC+5:30, Kohsuke Kawaguchi wrote: On 03/29/2011 08:23 AM, mke wrote: Does anyone have a procedure to convert from Hudson 1.395 on Windows to Jenkins? The issue list is for automated notification use and not for interactive discussion. For that, please use the users list. The instruction for upgrade is in http://wiki.jenkins-ci.org/**display/JENKINS/Upgrading+** from+Hudson+to+Jenkinshttp://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ -- Website: http://earl-of-code.com
email-ext tokens for Build Failure Analyzer
Great plugin! It's a huge time saver to have Jenkins figure out what went wrong with a build rather than having to view the log and figure it out for myself. Right now I'd say that the biggest improvements that could be made to the plugin involve making its results more prominent. It would be great if there was a failure reason email-ext token I could add to failure emails Jenkins sends out. I've seen that some plugins produce tokens for use by other plugins, apparently with the help of the Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens ). Also, the identified problems that appear in a build summary page is last on the page, seemingly following everything else. As far as I'm concerned, because of its importance it should be the very first item on the summary page. The lightbulb is a great way of seeing what happened with various builds without further clicking. Depending on how long descriptions are, it might be good to include additional information in the lightbulb tooltip such as the description or category. In any case, thanks for a very helpful plugin. - David
Re: email-ext tokens for Build Failure Analyzer
You can use Token Macro tokens in email-ext content templates. On Thu, Jan 3, 2013 at 6:24 AM, David Resnick abune...@gmail.com wrote: Great plugin! It's a huge time saver to have Jenkins figure out what went wrong with a build rather than having to view the log and figure it out for myself. Right now I'd say that the biggest improvements that could be made to the plugin involve making its results more prominent. It would be great if there was a failure reason email-ext token I could add to failure emails Jenkins sends out. I've seen that some plugins produce tokens for use by other plugins, apparently with the help of the Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens). Also, the identified problems that appear in a build summary page is last on the page, seemingly following everything else. As far as I'm concerned, because of its importance it should be the very first item on the summary page. The lightbulb is a great way of seeing what happened with various builds without further clicking. Depending on how long descriptions are, it might be good to include additional information in the lightbulb tooltip such as the description or category. In any case, thanks for a very helpful plugin. - David -- Website: http://earl-of-code.com
Re: email-ext tokens for Build Failure Analyzer
Right, but the Build Failure Analyzer plugin needs to create a token with its output first, doesn't it? - David On Thursday, January 3, 2013 3:26:43 PM UTC+2, slide wrote: You can use Token Macro tokens in email-ext content templates. On Thu, Jan 3, 2013 at 6:24 AM, David Resnick abun...@gmail.comjavascript: wrote: Great plugin! It's a huge time saver to have Jenkins figure out what went wrong with a build rather than having to view the log and figure it out for myself. Right now I'd say that the biggest improvements that could be made to the plugin involve making its results more prominent. It would be great if there was a failure reason email-ext token I could add to failure emails Jenkins sends out. I've seen that some plugins produce tokens for use by other plugins, apparently with the help of the Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens). Also, the identified problems that appear in a build summary page is last on the page, seemingly following everything else. As far as I'm concerned, because of its importance it should be the very first item on the summary page. The lightbulb is a great way of seeing what happened with various builds without further clicking. Depending on how long descriptions are, it might be good to include additional information in the lightbulb tooltip such as the description or category. In any case, thanks for a very helpful plugin. - David -- Website: http://earl-of-code.com
Re: email-ext tokens for Build Failure Analyzer
Yes, it does. You could fork the plugin, add the changes in and create a pull request. Community Driven Development at its finest. On Thu, Jan 3, 2013 at 6:35 AM, David Resnick abune...@gmail.com wrote: Right, but the Build Failure Analyzer plugin needs to create a token with its output first, doesn't it? - David On Thursday, January 3, 2013 3:26:43 PM UTC+2, slide wrote: You can use Token Macro tokens in email-ext content templates. On Thu, Jan 3, 2013 at 6:24 AM, David Resnick abun...@gmail.com wrote: Great plugin! It's a huge time saver to have Jenkins figure out what went wrong with a build rather than having to view the log and figure it out for myself. Right now I'd say that the biggest improvements that could be made to the plugin involve making its results more prominent. It would be great if there was a failure reason email-ext token I could add to failure emails Jenkins sends out. I've seen that some plugins produce tokens for use by other plugins, apparently with the help of the Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/** display/JENKINS/Static+Code+**Analysis+Plug-ins#** StaticCodeAnalysisPlug-ins-**tokenshttps://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens). Also, the identified problems that appear in a build summary page is last on the page, seemingly following everything else. As far as I'm concerned, because of its importance it should be the very first item on the summary page. The lightbulb is a great way of seeing what happened with various builds without further clicking. Depending on how long descriptions are, it might be good to include additional information in the lightbulb tooltip such as the description or category. In any case, thanks for a very helpful plugin. - David -- Website: http://earl-of-code.**com http://earl-of-code.com -- Website: http://earl-of-code.com
Question about automatic tools installation
Hi all, In our factory, we've faced with a problem with automatic installation of tools for CI (JDK, Maven, Groovy, Ant, ...) which are located in our private nexus repository. Jenkins passed through the proxy to download CI tools while the nexus is internal to our company. In three days, Jenkins has download 16go of CI Tools.. We have configured the Jenkins proxy for not going through the proxy if the URL corresponds to the nexus repository. For now, we do not see the downloads because Jenkins does not pass through the proxy to download, but is it a bug ? Jenkins should not have to download the tools systematically on each build, right? Thanks in advance. Michaël Pailloncy
Re: email-ext tokens for Build Failure Analyzer
Indeed it is! I hope to have time to get to this at some point. - David On Thursday, January 3, 2013 3:37:42 PM UTC+2, slide wrote: Yes, it does. You could fork the plugin, add the changes in and create a pull request. Community Driven Development at its finest. On Thu, Jan 3, 2013 at 6:35 AM, David Resnick abun...@gmail.comjavascript: wrote: Right, but the Build Failure Analyzer plugin needs to create a token with its output first, doesn't it? - David On Thursday, January 3, 2013 3:26:43 PM UTC+2, slide wrote: You can use Token Macro tokens in email-ext content templates. On Thu, Jan 3, 2013 at 6:24 AM, David Resnick abun...@gmail.com wrote: Great plugin! It's a huge time saver to have Jenkins figure out what went wrong with a build rather than having to view the log and figure it out for myself. Right now I'd say that the biggest improvements that could be made to the plugin involve making its results more prominent. It would be great if there was a failure reason email-ext token I could add to failure emails Jenkins sends out. I've seen that some plugins produce tokens for use by other plugins, apparently with the help of the Token Macro Plugin (e.g. https://wiki.jenkins-ci.org/** display/JENKINS/Static+Code+**Analysis+Plug-ins#** StaticCodeAnalysisPlug-ins-**tokenshttps://wiki.jenkins-ci.org/display/JENKINS/Static+Code+Analysis+Plug-ins#StaticCodeAnalysisPlug-ins-tokens). Also, the identified problems that appear in a build summary page is last on the page, seemingly following everything else. As far as I'm concerned, because of its importance it should be the very first item on the summary page. The lightbulb is a great way of seeing what happened with various builds without further clicking. Depending on how long descriptions are, it might be good to include additional information in the lightbulb tooltip such as the description or category. In any case, thanks for a very helpful plugin. - David -- Website: http://earl-of-code.**com http://earl-of-code.com -- Website: http://earl-of-code.com
TFS/Maven/Linux Help needed!
We are currently migrating from Windows to Linux build servers. I have everything up and running in Linux fine. However, when performing a maven release its failing right at the end. I have verified all the permissions, environment paths...etc. I am attaching the console output if someone could kindly point me in the right direction. Jenkins appears to be connecting to TFS fine but I think there is something going on with the maven plugin. 16:02:33 Started by user 16:02:33 Building on master in workspace /var/lib/jenkins/jobs/Stage-2xGraphics/workspace 16:02:33 [workspace] $ /usr/bin/tfs/tf workspaces -format:brief -server:http://1.2.3.250:8080/tfs/2x 16:02:36 Collection: http://1.2.3.250:8080/tfs/2x/ 16:02:36 Workspace Owner ComputerComment 16:02:36 - -- --- - 16:02:36 Jenkins-2xRecruit-2xAssessIntegration-Database-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-2xAssessIntegration-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-Current-Database-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-Current-Development-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-Current-Trunk-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-Future-Database-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-Future-Development-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-Future-Trunk-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-Future2-Database-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-Future2-Development-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-Future3-Database-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-Future3-Development-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-2xRecruit-FutureDev2-Sonar-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-Current-2xEVerify-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-FutureIntegration-2xApp-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-FutureIntegration-2xOnboardApplication-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-FutureIntegration-2xOnboardComponents-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-FutureIntegration-2xReleasePackage-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-FutureIntegration-KenexaAPI-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-FutureIntegration-NHP-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-FutureIntegration-Release-2xApp-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-FutureIntegration-Release-WorkBench-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-FutureIntegration-Sonar-2xApp-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-ProdHotFix-2xApp-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-ProdHotFix-KeyManager-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-ProdHotFix-NHP-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-ProdHotFix-Workbench-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-Production-2xGraphics-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 Jenkins-SCM-Future-Trunk-2xApp-MASTER RKAD01US\TFS2xbuildservice qpa-jenkins-226.ops-dev.pa-dev. 16:02:36 [workspace] $ /usr/bin/tfs/tf workspace -new Jenkins-Stage-2xGraphics-MASTER;rkad01us\tfs2xbuildservice -noprompt -server:http://1.2.3.250:8080/tfs/2x 16:02:37 Workspace 'Jenkins-Stage-2xGraphics-MASTER' created. 16:02:37 [workspace] $ /usr/bin/tfs/tf workfold -map $/2xGraphics/Stage/2xGraphics . -workspace:Jenkins-Stage-2xGraphics-MASTER -server:http://1.2.3.250:8080/tfs/2x
RE: TFS/Maven/Linux Help needed!
It looks like it can't find the tf command, at least that's what it looks like to me. Sent from my Windows Phone -- From: Steve Brice Sent: 1/3/2013 8:55 AM To: jenkinsci-users@googlegroups.com Subject: TFS/Maven/Linux Help needed! We are currently migrating from Windows to Linux build servers. I have everything up and running in Linux fine. However, when performing a maven release its failing right at the end. I have verified all the permissions, environment paths...etc. I am attaching the console output if someone could kindly point me in the right direction. Jenkins appears to be connecting to TFS fine but I think there is something going on with the maven plugin.
Re: Upgrading from Hudson Windows 1.395 to Jenkins
2.1.2 On Thu, Jan 3, 2013 at 6:29 PM, Slide slide.o@gmail.com wrote: What version are you upgrading from? On Thu, Jan 3, 2013 at 5:51 AM, prathima chowdary chowdary.gprath...@gmail.com wrote: Hello KK, I have bulk of Jobs in Hudson . And want to migrate From Hudson (Windows) to Jenkins ( Windows) with all the JOBS imported. So i have followed the belwo link which is not happening... Can u please give me the detailed picture how to Migrate ? https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins Very Urgent reply required ASAP.thanks a lottt On Tuesday, 29 March 2011 21:45:35 UTC+5:30, Kohsuke Kawaguchi wrote: On 03/29/2011 08:23 AM, mke wrote: Does anyone have a procedure to convert from Hudson 1.395 on Windows to Jenkins? The issue list is for automated notification use and not for interactive discussion. For that, please use the users list. The instruction for upgrade is in http://wiki.jenkins-ci.org/**display/JENKINS/Upgrading+** from+Hudson+to+Jenkinshttp://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ -- Website: http://earl-of-code.com
RE: TFS/Maven/Linux Help needed!
You may want to change the build users password :-o Maven will want the “tf” command to be on the path which it appears it’s not[1] (Jenkins uses the absolute path that its configured with[2] I would double check that environment that the user Jenkins is running as has /usr/bin/tfs on the path /James [1] 16:06:15 [INFO] err - /bin/sh: tf: command not found [2] 16:02:33 [workspace] $ /usr/bin/tfs/tf workspaces -format:brief -server:http://1.2.3.250:8080/tfs/2x From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Steve Brice Sent: 03 January 2013 15:55 To: jenkinsci-users@googlegroups.com Subject: TFS/Maven/Linux Help needed! We are currently migrating from Windows to Linux build servers. I have everything up and running in Linux fine. However, when performing a maven release its failing right at the end. I have verified all the permissions, environment paths...etc. I am attaching the console output if someone could kindly point me in the right direction. Jenkins appears to be connecting to TFS fine but I think there is something going on with the maven plugin. ** 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: Upgrading from Hudson Windows 1.395 to Jenkins
There is no direct upgrade path from anything higher than 1.395. Hudson changed the format that is used for serializing data to XML, this made Hudson and Jenkins incompatible. If you can downgrade to Hudson 1.395, you can then upgrade to Jenkins from there. On Thu, Jan 3, 2013 at 9:03 AM, prathima chowdary chowdary.gprath...@gmail.com wrote: 2.1.2 On Thu, Jan 3, 2013 at 6:29 PM, Slide slide.o@gmail.com wrote: What version are you upgrading from? On Thu, Jan 3, 2013 at 5:51 AM, prathima chowdary chowdary.gprath...@gmail.com wrote: Hello KK, I have bulk of Jobs in Hudson . And want to migrate From Hudson (Windows) to Jenkins ( Windows) with all the JOBS imported. So i have followed the belwo link which is not happening... Can u please give me the detailed picture how to Migrate ? https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins Very Urgent reply required ASAP.thanks a lottt On Tuesday, 29 March 2011 21:45:35 UTC+5:30, Kohsuke Kawaguchi wrote: On 03/29/2011 08:23 AM, mke wrote: Does anyone have a procedure to convert from Hudson 1.395 on Windows to Jenkins? The issue list is for automated notification use and not for interactive discussion. For that, please use the users list. The instruction for upgrade is in http://wiki.jenkins-ci.org/**display/JENKINS/Upgrading+** from+Hudson+to+Jenkinshttp://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ -- Website: http://earl-of-code.com -- Website: http://earl-of-code.com
Jenkins 1.496 CLI: java.lang.IllegalAccessError: org/kohsuke/args4j/CmdLineParser$1
Hello, I am getting exception from jenkins CLI since upgraded to version 1.496: + java -jar jenkins-cli.jar -shttp://myjenkins:8080/jenkins http://comitdev15:8899/jenkins -i /home/jenkins-slave/.ssh/id_rsa login Exception in thread main java.lang.reflect.UndeclaredThrowableException at $Proxy2.main(Unknown Source) at hudson.cli.CLI.execute(CLI.java:323) at hudson.cli.CLI._main(CLI.java:469) at hudson.cli.CLI.main(CLI.java:374) Caused by: java.io.IOException: Remote call on Chunked connection tohttp://myjenkins:8080/jenkins/cli http://comitdev15:8899/jenkins/cli failed at hudson.remoting.Channel.call(Channel.java:681) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) ... 4 more Caused by: java.lang.IllegalAccessError: org/kohsuke/args4j/CmdLineParser$1 at org.kohsuke.args4j.CmdLineParser.init(CmdLineParser.java:94) at hudson.cli.CLICommand.main(CLICommand.java:211) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Downgrade to 1.495 fixed the problem. Is there anyone having the same problem? -vf
Re: Upgrading from Hudson Windows 1.395 to Jenkins
Ok if we need to downgrade what r the chages to be done.. suppose if we cant , then how can we ? Is there no solution the hudson jobs cant be used? On Thu, Jan 3, 2013 at 9:44 PM, Slide slide.o@gmail.com wrote: There is no direct upgrade path from anything higher than 1.395. Hudson changed the format that is used for serializing data to XML, this made Hudson and Jenkins incompatible. If you can downgrade to Hudson 1.395, you can then upgrade to Jenkins from there. On Thu, Jan 3, 2013 at 9:03 AM, prathima chowdary chowdary.gprath...@gmail.com wrote: 2.1.2 On Thu, Jan 3, 2013 at 6:29 PM, Slide slide.o@gmail.com wrote: What version are you upgrading from? On Thu, Jan 3, 2013 at 5:51 AM, prathima chowdary chowdary.gprath...@gmail.com wrote: Hello KK, I have bulk of Jobs in Hudson . And want to migrate From Hudson (Windows) to Jenkins ( Windows) with all the JOBS imported. So i have followed the belwo link which is not happening... Can u please give me the detailed picture how to Migrate ? https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins Very Urgent reply required ASAP.thanks a lottt On Tuesday, 29 March 2011 21:45:35 UTC+5:30, Kohsuke Kawaguchi wrote: On 03/29/2011 08:23 AM, mke wrote: Does anyone have a procedure to convert from Hudson 1.395 on Windows to Jenkins? The issue list is for automated notification use and not for interactive discussion. For that, please use the users list. The instruction for upgrade is in http://wiki.jenkins-ci.org/**display/JENKINS/Upgrading+** from+Hudson+to+Jenkinshttp://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ -- Website: http://earl-of-code.com -- Website: http://earl-of-code.com
Re: Jenkins 1.496 CLI: java.lang.IllegalAccessError: org/kohsuke/args4j/CmdLineParser$1
Some more info: This is a job executed in a debian slave, our jenkins master is also running on debian. It worked perfectly well in the last months (probably over 1 year). Am 03.01.2013 17:24, schrieb John Vacz: Hello, I am getting exception from jenkins CLI since upgraded to version 1.496: + java -jar jenkins-cli.jar -shttp://myjenkins:8080/jenkins http://comitdev15:8899/jenkins -i /home/jenkins-slave/.ssh/id_rsa login Exception in thread main java.lang.reflect.UndeclaredThrowableException at $Proxy2.main(Unknown Source) at hudson.cli.CLI.execute(CLI.java:323) at hudson.cli.CLI._main(CLI.java:469) at hudson.cli.CLI.main(CLI.java:374) Caused by: java.io.IOException: Remote call on Chunked connection tohttp://myjenkins:8080/jenkins/cli http://comitdev15:8899/jenkins/cli failed at hudson.remoting.Channel.call(Channel.java:681) at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:158) ... 4 more Caused by: java.lang.IllegalAccessError: org/kohsuke/args4j/CmdLineParser$1 at org.kohsuke.args4j.CmdLineParser.init(CmdLineParser.java:94) at hudson.cli.CLICommand.main(CLICommand.java:211) at hudson.cli.CliManagerImpl.main(CliManagerImpl.java:92) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at hudson.remoting.RemoteInvocationHandler$RPCRequest.perform(RemoteInvocationHandler.java:275) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:256) at hudson.remoting.RemoteInvocationHandler$RPCRequest.call(RemoteInvocationHandler.java:215) at hudson.remoting.UserRequest.perform(UserRequest.java:118) at hudson.remoting.UserRequest.perform(UserRequest.java:48) at hudson.remoting.Request$2.run(Request.java:326) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) at hudson.cli.CliManagerImpl$1.call(CliManagerImpl.java:63) at hudson.remoting.InterceptingExecutorService$2.call(InterceptingExecutorService.java:95) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:662) Downgrade to 1.495 fixed the problem. Is there anyone having the same problem? -vf
Re: Upgrading from Hudson Windows 1.395 to Jenkins
You're asking the wrong people. Hudson devs changed the format of the XML files, you'll need to ask them if you can downgrade from your current version to 1.395. If you can't, then you would need to manually convert the XML files back to the format they used to have (which is still used by Jenkins). Once Hudson changed their XML format, it made it very difficult to migrate from Hudson to Jenkins, sorry. On Thu, Jan 3, 2013 at 9:26 AM, prathima chowdary chowdary.gprath...@gmail.com wrote: Ok if we need to downgrade what r the chages to be done.. suppose if we cant , then how can we ? Is there no solution the hudson jobs cant be used? On Thu, Jan 3, 2013 at 9:44 PM, Slide slide.o@gmail.com wrote: There is no direct upgrade path from anything higher than 1.395. Hudson changed the format that is used for serializing data to XML, this made Hudson and Jenkins incompatible. If you can downgrade to Hudson 1.395, you can then upgrade to Jenkins from there. On Thu, Jan 3, 2013 at 9:03 AM, prathima chowdary chowdary.gprath...@gmail.com wrote: 2.1.2 On Thu, Jan 3, 2013 at 6:29 PM, Slide slide.o@gmail.com wrote: What version are you upgrading from? On Thu, Jan 3, 2013 at 5:51 AM, prathima chowdary chowdary.gprath...@gmail.com wrote: Hello KK, I have bulk of Jobs in Hudson . And want to migrate From Hudson (Windows) to Jenkins ( Windows) with all the JOBS imported. So i have followed the belwo link which is not happening... Can u please give me the detailed picture how to Migrate ? https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins Very Urgent reply required ASAP.thanks a lottt On Tuesday, 29 March 2011 21:45:35 UTC+5:30, Kohsuke Kawaguchi wrote: On 03/29/2011 08:23 AM, mke wrote: Does anyone have a procedure to convert from Hudson 1.395 on Windows to Jenkins? The issue list is for automated notification use and not for interactive discussion. For that, please use the users list. The instruction for upgrade is in http://wiki.jenkins-ci.org/**display/JENKINS/Upgrading+** from+Hudson+to+Jenkinshttp://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ -- Website: http://earl-of-code.com -- Website: http://earl-of-code.com -- Website: http://earl-of-code.com
Need to Display the Clover Conditionals or Methods Values instead of Statements in Results Email
Hi, we are using the html-with-health-and-console.jelly file in the email-ext plugin to display the metrics health results in the build results email. The problem is that it only displays the Clover Coverage Statements value in the email. Is there any way to get either the Conditionals or Methods values to show instead? When debugging and I can only find a cachedBuildHealthReports arrayList, and it only shows the Clover Coverage Statements and not the other two, but all three values show up in the build UI pages. Is there a way to get the other Clover values via the jelly template?
Git question...
I have some Git projects (internal gitolite repository) that I'm configuring and when I put the git repo URL in, it shows this error below field: *Failed to connect to repository : Error performing command: ls-remote -h gitolite@mygitrepo:/myproject.git HEAD* If I login as the user that Jenkins is running as (tomcat7 on Ubuntu 12.10) and type the same command, I don't get an error, but I also don't see any output of any kind. If I leave off the HEAD option, I get a response like: 6156c0bd163a1b9e3a878e889be53c5b80f48c36refs/heads/master Am I doing something wrong? If I just save the job, it seems to clone and build just fine but I haven't tried any Maven releases yet so I don't know if that works. I can't see in any logs what the specific error might be. Thoughts? -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !!
Re: Git question...
I thought that I had seen that failure when I enabled fast remote polling and had not yet cloned the git repository. My quick web search did not show that as a bug, so I may be wrong, but it won't hurt to try disabling fast remote polling (it is in the Advanced section of the git plugin settings for your job). I tried to duplicate the problem myself and was unable to duplicate it, so I'm probably not using exactly the steps you are using. Mark Waite From: Jeff predato...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Thursday, January 3, 2013 1:35 PM Subject: Git question... I have some Git projects (internal gitolite repository) that I'm configuring and when I put the git repo URL in, it shows this error below field: Failed to connect to repository : Error performing command: ls-remote -h gitolite@mygitrepo:/myproject.git HEAD If I login as the user that Jenkins is running as (tomcat7 on Ubuntu 12.10) and type the same command, I don't get an error, but I also don't see any output of any kind. If I leave off the HEAD option, I get a response like: 6156c0bd163a1b9e3a878e889be53c5b80f48c36 refs/heads/master Am I doing something wrong? If I just save the job, it seems to clone and build just fine but I haven't tried any Maven releases yet so I don't know if that works. I can't see in any logs what the specific error might be. Thoughts? -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox !!
Re: migration hudson 2.2.0 to jenkins
What is the latest version before the fork? I thought 2.2.0 was already beyond the fork? On 2 January 2013 20:46, Lars Nordin lnor...@internap.com wrote: Search the mailing list archives for posts from folks that have done this same thing. ** ** The pattern has been – depending on how old of a version of hudson – to upgrade to the last version of hudson before the fork (you may need an interim upgrade if your version of Hudson is really old) and then upgrade to latest LTS. This is more effort but more likely to work and give you a working system as you upgrade. ** **
Re: Git question...
I didn't even realize those options existed...ack! I checked and Fast remote polling is NOT set. I have not set any other options beyond the repo URL. Did I possibly miss something? On Thu, Jan 3, 2013 at 5:17 PM, Mark Waite markwa...@yahoo.com wrote: I thought that I had seen that failure when I enabled fast remote polling and had not yet cloned the git repository. My quick web search did not show that as a bug, so I may be wrong, but it won't hurt to try disabling fast remote polling (it is in the Advanced section of the git plugin settings for your job). I tried to duplicate the problem myself and was unable to duplicate it, so I'm probably not using exactly the steps you are using. Mark Waite -- *From:* Jeff predato...@gmail.com *To:* jenkinsci-users@googlegroups.com *Sent:* Thursday, January 3, 2013 1:35 PM *Subject:* Git question... I have some Git projects (internal gitolite repository) that I'm configuring and when I put the git repo URL in, it shows this error below field: *Failed to connect to repository : Error performing command: ls-remote -h gitolite@mygitrepo:/myproject.git HEAD* If I login as the user that Jenkins is running as (tomcat7 on Ubuntu 12.10) and type the same command, I don't get an error, but I also don't see any output of any kind. If I leave off the HEAD option, I get a response like: 6156c0bd163a1b9e3a878e889be53c5b80f48c36refs/heads/master Am I doing something wrong? If I just save the job, it seems to clone and build just fine but I haven't tried any Maven releases yet so I don't know if that works. I can't see in any logs what the specific error might be. Thoughts? -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !!
RE: migration hudson 2.2.0 to jenkins
Yes, the fork happened around 1.395 or so. I don't know what version Hudson changed the format. Sent from my Windows Phone -- From: Daniel Fortunov Sent: 1/3/2013 5:18 PM To: jenkinsci-users@googlegroups.com Subject: Re: migration hudson 2.2.0 to jenkins What is the latest version before the fork? I thought 2.2.0 was already beyond the fork? On 2 January 2013 20:46, Lars Nordin lnor...@internap.com wrote: Search the mailing list archives for posts from folks that have done this same thing. ** ** The pattern has been – depending on how old of a version of hudson – to upgrade to the last version of hudson before the fork (you may need an interim upgrade if your version of Hudson is really old) and then upgrade to latest LTS. This is more effort but more likely to work and give you a working system as you upgrade. ** **
Re: Git question...
There was a report of the same error message in late November that was due to insufficient memory being available for the Jenkins process. Refer to http://jenkins.361315.n4.nabble.com/Jenkins-GIT-ls-remote-error-td4646903.html for more details on it. I suspect that is not your issue, but it should be easy to check if it is the problem. You could also try configuring a git repository without using gitolite (for instance, use apt-get to install the git server, publish the repository to /var/cache/git/repo_name, touch git-daemon-export-ok in that directory, and then create a job which uses git://yourserver/git/repo_name to checkout. That idea is suggested in http://stackoverflow.com/questions/12614771/configure-git-repository-in-jenkins . I don't think that is likely your problem either, but trying the fix may expose the real problem to you. Mark Waite From: Jeff predato...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Thursday, January 3, 2013 5:22 PM Subject: Re: Git question... I didn't even realize those options existed...ack! I checked and Fast remote polling is NOT set. I have not set any other options beyond the repo URL. Did I possibly miss something? On Thu, Jan 3, 2013 at 5:17 PM, Mark Waite markwa...@yahoo.com wrote: I thought that I had seen that failure when I enabled fast remote polling and had not yet cloned the git repository. My quick web search did not show that as a bug, so I may be wrong, but it won't hurt to try disabling fast remote polling (it is in the Advanced section of the git plugin settings for your job). I tried to duplicate the problem myself and was unable to duplicate it, so I'm probably not using exactly the steps you are using. Mark Waite From: Jeff predato...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Thursday, January 3, 2013 1:35 PM Subject: Git question... I have some Git projects (internal gitolite repository) that I'm configuring and when I put the git repo URL in, it shows this error below field: Failed to connect to repository : Error performing command: ls-remote -h gitolite@mygitrepo:/myproject.git HEAD If I login as the user that Jenkins is running as (tomcat7 on Ubuntu 12.10) and type the same command, I don't get an error, but I also don't see any output of any kind. If I leave off the HEAD option, I get a response like: 6156c0bd163a1b9e3a878e889be53c5b80f48c36 refs/heads/master Am I doing something wrong? If I just save the job, it seems to clone and build just fine but I haven't tried any Maven releases yet so I don't know if that works. I can't see in any logs what the specific error might be. Thoughts? -- 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: Git question...
Thanks for the tips...I'll try and poke around with it tomorrow. I'm finding Git to be a pain compared to SVNugh...likely loose nut behind the keyboard. My Jenkins server has 4GB of RAM and 2.5 GB is dedicated to tomcat running Jenkins but I will triple check the settings as well. We actually have 2 Jenkins masters now experiencing the issue that are identically configured (cloned VM). One is running 40 jobs (3 Git, 37 SVN) on 3 slaves (no jobs run on master). The other running only one Git job on the master (no slaves). On Thu, Jan 3, 2013 at 8:02 PM, Mark Waite markwa...@yahoo.com wrote: There was a report of the same error message in late November that was due to insufficient memory being available for the Jenkins process. Refer to http://jenkins.361315.n4.nabble.com/Jenkins-GIT-ls-remote-error-td4646903.htmlfor more details on it. I suspect that is not your issue, but it should be easy to check if it is the problem. You could also try configuring a git repository without using gitolite (for instance, use apt-get to install the git server, publish the repository to /var/cache/git/repo_name, touch git-daemon-export-ok in that directory, and then create a job which uses git://yourserver/git/repo_name to checkout. That idea is suggested in http://stackoverflow.com/questions/12614771/configure-git-repository-in-jenkins. I don't think that is likely your problem either, but trying the fix may expose the real problem to you. Mark Waite -- *From:* Jeff predato...@gmail.com *To:* jenkinsci-users@googlegroups.com *Sent:* Thursday, January 3, 2013 5:22 PM *Subject:* Re: Git question... I didn't even realize those options existed...ack! I checked and Fast remote polling is NOT set. I have not set any other options beyond the repo URL. Did I possibly miss something? On Thu, Jan 3, 2013 at 5:17 PM, Mark Waite markwa...@yahoo.com wrote: I thought that I had seen that failure when I enabled fast remote polling and had not yet cloned the git repository. My quick web search did not show that as a bug, so I may be wrong, but it won't hurt to try disabling fast remote polling (it is in the Advanced section of the git plugin settings for your job). I tried to duplicate the problem myself and was unable to duplicate it, so I'm probably not using exactly the steps you are using. Mark Waite -- *From:* Jeff predato...@gmail.com *To:* jenkinsci-users@googlegroups.com *Sent:* Thursday, January 3, 2013 1:35 PM *Subject:* Git question... I have some Git projects (internal gitolite repository) that I'm configuring and when I put the git repo URL in, it shows this error below field: *Failed to connect to repository : Error performing command: ls-remote -h gitolite@mygitrepo:/myproject.git HEAD* If I login as the user that Jenkins is running as (tomcat7 on Ubuntu 12.10) and type the same command, I don't get an error, but I also don't see any output of any kind. If I leave off the HEAD option, I get a response like: 6156c0bd163a1b9e3a878e889be53c5b80f48c36refs/heads/master Am I doing something wrong? If I just save the job, it seems to clone and build just fine but I haven't tried any Maven releases yet so I don't know if that works. I can't see in any logs what the specific error might be. Thoughts? -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !!
Jenkins 1.496 on Windows Server 2008: Update Plugin Manager does not work
Jenkins 1.496 on Windows Server 2008 runs so far. But if I go to *Plugin Manager / Advanced *and try to update the plugin information from the update center URL (press *Check now*) the following page displays *Checking Updates...* but nothing happens and finally I have no plugin information (e.g.in the *Available* tab). Any hints? Thanks Michael
