Re: Change subject in email-ext
Can you show me an example of groovy script? On Wednesday, April 15, 2015 at 4:53:44 PM UTC+5, slide wrote: You could use the SCRIPT token in the subject and have the decision making done in the groovy script. I do this for lots of things. On Wed, Apr 15, 2015 at 12:06 AM Faizan Javed faixa...@gmail.com javascript: wrote: I am using email-ext plugin to trigger emails after the build fails or become unstable. The build becomes unstable when some of the tests fail and the build fails when the compilation fail. Can we use conditions to display different customized subject depending on the cause of the email trigger? -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/78afab09-7faa-4721-98f7-54501aa6f9a5%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/78afab09-7faa-4721-98f7-54501aa6f9a5%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/db0054b6-eeb0-49e6-8aa5-2677d1048c3c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
jenkins subversion
hi i have installed jenkins and configured subversion on windows if there is a build failure i want to send the emails to the respective developer who has last committed the code in subversion how to do because subversion doesnot have the email id of the users can u help me on this -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/aa9b1685-0329-4757-8165-8e1384e69638%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: jenkins subversion
Hi, you can add them all in the Manage Jenkins -- Manage Users menu, including their e-mail addresses. You can then start to configure the e-mail behaviour, and later you can see their latest activities in the top level “People” menu. Best, Jennifer From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Shivaprakash Tirlapur Sent: Donnerstag, 16. April 2015 10:37 To: jenkinsci-users@googlegroups.com Subject: jenkins subversion hi i have installed jenkins and configured subversion on windows if there is a build failure i want to send the emails to the respective developer who has last committed the code in subversion how to do because subversion doesnot have the email id of the users can u help me on this -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/aa9b1685-0329-4757-8165-8e1384e69638%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/aa9b1685-0329-4757-8165-8e1384e69638%40googlegroups.com?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAA587D532C45541B62417404F1D22030E81D766%40you-exch1.younicos.local. For more options, visit https://groups.google.com/d/optout.
Re: how to add many jobs in jenkins for all projects at once
Any help plese :) Le mercredi 15 avril 2015 14:01:10 UTC+1, Fatiha a écrit : Hi , please we have at the moment a lot of projects to add in jenkins, i ask if there is a script or any trick on jenkins that can allow us to do it ? thank's in advance -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/24b2ac26-8aff-4062-af80-a401056d4786%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Docker plugin - slave status is connection refused
Hi, I've experienced a similar behaviour, but with docker plugin v 0.8 and Jenkins starting from version 1.606 till 1.609. If with 1.606 it is still possible to run builds, even though sometimes agents failed to start, 1.609 was impossible to use and I rolled back to 1.605. And this behaviour reproduces also on a test environment where Jenkins ran on Tomcat. Platform used OpenSuse 13.2, docker 1.5.0. I did not find any differences in config files while switching version that could affect this, but v 1.606 had fixes in slave/master communication. Since I was unable to find any network issues, I'm out of ideas on how to debug this issue. Regards, Janis On Sunday, 1 March 2015 07:37:01 UTC+2, Maneesh M P wrote: Hello, I am getting an SSH connection timed out issue with docker plugin. i am using docker plugin verision 0.7 and jenkins version 1.565.2 http://jenkins-ci.org/. Can anyone helping to figure out what is going on wrong ? [02/28/15 21:31:03] [SSH] Opening SSH connection to 54.72.187.35:52576. Connection refused SSH Connection failed with IOException: Connection refused. java.io.IOException: There was a problem while connecting to 54.72.187.35:52576 at com.trilead.ssh2.Connection.connect(Connection.java:818) at com.trilead.ssh2.Connection.connect(Connection.java:687) at com.trilead.ssh2.Connection.connect(Connection.java:587) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1146) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:701) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385) at java.net.Socket.connect(Socket.java:546) at com.trilead.ssh2.transport.TransportManager.establishConnection(TransportManager.java:346) at com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:459) at com.trilead.ssh2.Connection.connect(Connection.java:758) ... 10 more Thanks, Maneesh -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/31bbab3d-3afa-4472-9369-4c518f79d66d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Docker plugin - slave status is connection refused
If you are referring to docker plugin then tried that too, last week though... On Thursday, 16 April 2015 12:28:42 UTC+3, nigelm wrote: You could try the beta-1 version in the experimental jenkins update centre - though the error there looks like a connection failure. On Thu, Apr 16, 2015 at 10:13 AM, Jānis Balodis janis@gmail.com javascript: wrote: Hi, I've experienced a similar behaviour, but with docker plugin v 0.8 and Jenkins starting from version 1.606 till 1.609. If with 1.606 it is still possible to run builds, even though sometimes agents failed to start, 1.609 was impossible to use and I rolled back to 1.605. And this behaviour reproduces also on a test environment where Jenkins ran on Tomcat. Platform used OpenSuse 13.2, docker 1.5.0. I did not find any differences in config files while switching version that could affect this, but v 1.606 had fixes in slave/master communication. Since I was unable to find any network issues, I'm out of ideas on how to debug this issue. Regards, Janis On Sunday, 1 March 2015 07:37:01 UTC+2, Maneesh M P wrote: Hello, I am getting an SSH connection timed out issue with docker plugin. i am using docker plugin verision 0.7 and jenkins version 1.565.2 http://jenkins-ci.org/. Can anyone helping to figure out what is going on wrong ? [02/28/15 21:31:03] [SSH] Opening SSH connection to 54.72.187.35:52576. Connection refused SSH Connection failed with IOException: Connection refused. java.io.IOException: There was a problem while connecting to 54.72.187.35:52576 at com.trilead.ssh2.Connection.connect(Connection.java:818) at com.trilead.ssh2.Connection.connect(Connection.java:687) at com.trilead.ssh2.Connection.connect(Connection.java:587) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1146) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:701) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385) at java.net.Socket.connect(Socket.java:546) at com.trilead.ssh2.transport.TransportManager.establishConnection(TransportManager.java:346) at com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:459) at com.trilead.ssh2.Connection.connect(Connection.java:758) ... 10 more Thanks, Maneesh -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/31bbab3d-3afa-4472-9369-4c518f79d66d%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/31bbab3d-3afa-4472-9369-4c518f79d66d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/e82c1827-5164-4de0-9716-90cfae761bac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Git repository connection times out sometimes
Hello, I have several build jobs that clone from a remote Git repository. On some of them, the git fetch part of the command fails with the following output: Building on master in workspace C:\Program Files (x86)\Jenkins\jobs\test_123\workspace git.exe rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository git.exe config remote.origin.url ssh://g...@stash.mycompany.com:port/path/test-project1.git # timeout=10 Fetching upstream changes from ssh://g...@stash.mycompany.com:port/path/test-project1.git git.exe --version # timeout=10 git.exe -c core.askpass=true fetch --tags --progress ssh://g...@stash.mycompany.com:port/path/test-project1.git +refs/heads/*:refs/remotes/origin/* # timeout=10 ERROR: Timeout after 10 minutes ERROR: Error fetching remote repo 'origin' ERROR: Error fetching remote repo 'origin' I get no more information. The process doesn’t get rejected by Stash, it just times out waiting for admission. The odd thing is that at the same time, other builds that do the very same thing will execute. On some builds, the effect even seems to occur arbitrarily, or not. Only one job really never seems to work (the one above). This just started happening on Monday. No changes or updates were made to either Stash or Jenkins (Windows 7 x64, v1.580.1). All connections are going out from this one machine, and the Stash connection has been working fine up until now. I tried upgrading the Git plugin, without effect, so now it is back at 2.3.4. Any ideas are appreciated! (A while ago, I had a similar inexplicable issue with Subversion I never got to solve, which was terribly frustrating. So any help is very much appreciated, really.) All the best, Jennifer -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAA587D532C45541B62417404F1D22030E81D7A4%40you-exch1.younicos.local. For more options, visit https://groups.google.com/d/optout.
Re: Docker plugin - slave status is connection refused
You could try the beta-1 version in the experimental jenkins update centre - though the error there looks like a connection failure. On Thu, Apr 16, 2015 at 10:13 AM, Jānis Balodis janis.balo...@gmail.com wrote: Hi, I've experienced a similar behaviour, but with docker plugin v 0.8 and Jenkins starting from version 1.606 till 1.609. If with 1.606 it is still possible to run builds, even though sometimes agents failed to start, 1.609 was impossible to use and I rolled back to 1.605. And this behaviour reproduces also on a test environment where Jenkins ran on Tomcat. Platform used OpenSuse 13.2, docker 1.5.0. I did not find any differences in config files while switching version that could affect this, but v 1.606 had fixes in slave/master communication. Since I was unable to find any network issues, I'm out of ideas on how to debug this issue. Regards, Janis On Sunday, 1 March 2015 07:37:01 UTC+2, Maneesh M P wrote: Hello, I am getting an SSH connection timed out issue with docker plugin. i am using docker plugin verision 0.7 and jenkins version 1.565.2 http://jenkins-ci.org/. Can anyone helping to figure out what is going on wrong ? [02/28/15 21:31:03] [SSH] Opening SSH connection to 54.72.187.35:52576. Connection refused SSH Connection failed with IOException: Connection refused. java.io.IOException: There was a problem while connecting to 54.72.187.35:52576 at com.trilead.ssh2.Connection.connect(Connection.java:818) at com.trilead.ssh2.Connection.connect(Connection.java:687) at com.trilead.ssh2.Connection.connect(Connection.java:587) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1146) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:701) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385) at java.net.Socket.connect(Socket.java:546) at com.trilead.ssh2.transport.TransportManager.establishConnection(TransportManager.java:346) at com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:459) at com.trilead.ssh2.Connection.connect(Connection.java:758) ... 10 more Thanks, Maneesh -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/31bbab3d-3afa-4472-9369-4c518f79d66d%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/31bbab3d-3afa-4472-9369-4c518f79d66d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAPYP83SYcGiFKMEwi-6S7ojrNCo5ZQHHNgOyS6t%2BVr1wO5Aajg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: how to add many jobs in jenkins for all projects at once
Maybe the JobDSL plugin can helps you ( https://wiki.jenkins-ci.org/display/JENKINS/Job+DSL+Plugin ) With that plugin you can make a script that builds jobs automatically. If you have your projects on some scm I think it will be easy for you. El miércoles, 15 de abril de 2015, 15:01:10 (UTC+2), Fatiha escribió: Hi , please we have at the moment a lot of projects to add in jenkins, i ask if there is a script or any trick on jenkins that can allow us to do it ? thank's in advance -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9571aaa3-4c8e-43a2-b944-63462e873038%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
ERROR: Processing failed due to a bug in the code
From a maven job with target 'clean compile' Followed by execute shell 'mvn pre-site' This occurred after I disabled automatic reporting and tried to do it manually. Jenkins ver. 1.596.1 ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.IllegalStateException: cannot change build result while in COMPLETED at hudson.model.Run.setResult(Run.java:458) at hudson.plugins.doclinks.m2.DocLinksMavenReporter.end(DocLinksMavenReporter.java:97) at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:104) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:855) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) project=hudson.maven.MavenModuleSet@2664d296[lombok-maven-multimodule] project.getModules()=[hudson.maven.MavenModule@1310e33b[lombok-maven-multimodule/io.github:lombok-maven-multimodule][lombok-maven-multimodule/io.github:lombok-maven-multimodule][relativePath:], hudson.maven.MavenModule@219b7cf7[lombok-maven-multimodule/io.github:lombok-maven-multimodule-lomboklib][lombok-maven-multimodule/io.github:lombok-maven-multimodule-lomboklib][relativePath:lombok-maven-multimodule-lomboklib], hudson.maven.MavenModule@44826349[lombok-maven-multimodule/io.github:lombok-maven-multimodule-other][lombok-maven-multimodule/io.github:lombok-maven-multimodule-other][relativePath:lombok-maven-multimodule-other]] project.getRootModule()=hudson.maven.MavenModule@1310e33b[lombok-maven-multimodule/io.github:lombok-maven-multimodule][lombok-maven-multimodule/io.github:lombok-maven-multimodule][relativePath:] FATAL: cannot change build result while in COMPLETED java.lang.IllegalStateException: cannot change build result while in COMPLETED at hudson.model.Run.setResult(Run.java:458) at hudson.plugins.doclinks.m2.DocLinksMavenReporter.end(DocLinksMavenReporter.java:97) at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:104) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:855) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Best regards, Eero Aaltonen -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8936566a-1c85-4fd4-8811-f147f5c919c5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: ERROR: Processing failed due to a bug in the code
After unticking Publish documents, this error disappeared. On Thursday, April 16, 2015 at 3:25:19 PM UTC+3, Eero Aaltonen wrote: From a maven job with target 'clean compile' Followed by execute shell 'mvn pre-site' This occurred after I disabled automatic reporting and tried to do it manually. Jenkins ver. 1.596.1 ERROR: Processing failed due to a bug in the code. Please report this to jenkinsci-users@googlegroups.com java.lang.IllegalStateException: cannot change build result while in COMPLETED at hudson.model.Run.setResult(Run.java:458) at hudson.plugins.doclinks.m2.DocLinksMavenReporter.end(DocLinksMavenReporter.java:97) at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:104) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:855) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) project=hudson.maven.MavenModuleSet@2664d296[lombok-maven-multimodule] project.getModules()=[hudson.maven.MavenModule@1310e33b[lombok-maven-multimodule/io.github:lombok-maven-multimodule][lombok-maven-multimodule/io.github:lombok-maven-multimodule][relativePath:], hudson.maven.MavenModule@219b7cf7[lombok-maven-multimodule/io.github:lombok-maven-multimodule-lomboklib][lombok-maven-multimodule/io.github:lombok-maven-multimodule-lomboklib][relativePath:lombok-maven-multimodule-lomboklib], hudson.maven.MavenModule@44826349[lombok-maven-multimodule/io.github:lombok-maven-multimodule-other][lombok-maven-multimodule/io.github:lombok-maven-multimodule-other][relativePath:lombok-maven-multimodule-other]] project.getRootModule()=hudson.maven.MavenModule@1310e33b[lombok-maven-multimodule/io.github:lombok-maven-multimodule][lombok-maven-multimodule/io.github:lombok-maven-multimodule][relativePath:] FATAL: cannot change build result while in COMPLETED java.lang.IllegalStateException: cannot change build result while in COMPLETED at hudson.model.Run.setResult(Run.java:458) at hudson.plugins.doclinks.m2.DocLinksMavenReporter.end(DocLinksMavenReporter.java:97) at hudson.maven.AbstractMavenBuilder.end(AbstractMavenBuilder.java:104) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.doRun(MavenModuleSetBuild.java:855) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:533) at hudson.model.Run.execute(Run.java:1759) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:531) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Best regards, Eero Aaltonen -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/df3bc6f5-9600-429b-a416-4d2fee270713%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Workflow-plugin] Use Jenkins plugins in Workflow
Hi, I would like to use some plugins that are not in the compatibility list ( https://github.com/jenkinsci/workflow-plugin/blob/master/COMPATIBILITY.md) in my workflow job scripts. Is there any way to do it? Like calling the plugin class or something. Thank you! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7ed1456f-bc38-474f-b8e2-fa9bbba60567%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: Git repository connection times out sometimes
That sounds more like network issues that git issues. Is someone playing with duplicate IPs on your network and triggering spanning-tree or something? From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jennifer Hofmeister Sent: April-16-15 05:38 To: jenkinsci-users@googlegroups.com Subject: Git repository connection times out sometimes Hello, I have several build jobs that clone from a remote Git repository. On some of them, the git fetch part of the command fails with the following output: Building on master in workspace C:\Program Files (x86)\Jenkins\jobs\test_123\workspace git.exe rev-parse --is-inside-work-tree # timeout=10 Fetching changes from the remote Git repository git.exe config remote.origin.url ssh://g...@stash.mycompany.com:port/path/test-project1.git # timeout=10 Fetching upstream changes from ssh://g...@stash.mycompany.com:port/path/test-project1.git git.exe --version # timeout=10 git.exe -c core.askpass=true fetch --tags --progress ssh://g...@stash.mycompany.com:port/path/test-project1.git +refs/heads/*:refs/remotes/origin/* # timeout=10 ERROR: Timeout after 10 minutes ERROR: Error fetching remote repo 'origin' ERROR: Error fetching remote repo 'origin' I get no more information. The process doesn’t get rejected by Stash, it just times out waiting for admission. The odd thing is that at the same time, other builds that do the very same thing will execute. On some builds, the effect even seems to occur arbitrarily, or not. Only one job really never seems to work (the one above). This just started happening on Monday. No changes or updates were made to either Stash or Jenkins (Windows 7 x64, v1.580.1). All connections are going out from this one machine, and the Stash connection has been working fine up until now. I tried upgrading the Git plugin, without effect, so now it is back at 2.3.4. Any ideas are appreciated! (A while ago, I had a similar inexplicable issue with Subversion I never got to solve, which was terribly frustrating. So any help is very much appreciated, really.) All the best, Jennifer -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.commailto:jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAA587D532C45541B62417404F1D22030E81D7A4%40you-exch1.younicos.localhttps://groups.google.com/d/msgid/jenkinsci-users/CAA587D532C45541B62417404F1D22030E81D7A4%40you-exch1.younicos.local?utm_medium=emailutm_source=footer. For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/a7da27796098470682a07ac46d61372a%40mbx01colo01p.esentire.local. For more options, visit https://groups.google.com/d/optout.
Re: Selenium plugin couldn't register this node : Hub is down or not responding: Connect to ... failed: Connection refused
Don't creat Jenkins slave and it's work. Le jeudi 30 octobre 2014 09:47:05 UTC+1, Julien Breton a écrit : Hello, I use the Selenium plugin of Jenkins. On my Jenkins master (Ubuntu) I created a slave. This slave is launched by JNLP on a VM (VirtualBox Ubuntu). The communication between the master and the slave is OK. I created a Selenium node configuration. When I go to the Selenium Grid on Jenkins I see : No RCs have checked in yet. Have you started some slaves? When I watch the logs of the slave I see : 09:37:22.618 INFO - couldn't register this node : Hub is down or not responding: Connect to ... failed: Connection refused The firewall is off. I decided to test Selenium Grid without Jenkins. I launch manually the Selenium hub on my computer and the Selenium node on my VM and it's work perfectly. So I supposse it's not a network problem but a Jenkins configuration problem. I tried with a Windows 8 and a VM Ubuntu and I have the same error couldn't register this node When I do this command : nmap -p -sT IPmaster I get : Port /tcp State Closed Service krb524 Closed = nothing uses this port. If I launch the same command when I launch the Selenium hub manually (without Jenkins), the port is openned. Wat kind of Jenkins slave I should creat? Do you think there is an issue wirth the Selenium plugin? Thanks for your help. Julien -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7eeaadb2-1fac-4cc7-878b-aa64528a25cb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Migrate Jenkins Master and Slaves Nodes
I need to migrate the Jenkins Master server and Slave servers to new infrastructure. What is the ‘best practice’ to perform this migration other than just copying the JENKINS_HOME directory? What other ‘critical’ files need to be migrated over? -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/D1552340.C0A0%25ashish.yadav%40firemon.com. For more options, visit https://groups.google.com/d/optout.
Re: Docker plugin - slave status is connection refused
Hi, Further more, the first build after Jenkins master restart works fine (Docker node is started and build completed). After that nodes are spawned, I can see that sshd is up, but jenkins slave is not launched. I can connect to a running instance via ssh by the given address and port. It all works. If I'll click on Launch slave agent on a node that initially failed to start, it will launch. Regards, Janis On Thursday, 16 April 2015 12:37:37 UTC+3, Jānis Balodis wrote: If you are referring to docker plugin then tried that too, last week though... On Thursday, 16 April 2015 12:28:42 UTC+3, nigelm wrote: You could try the beta-1 version in the experimental jenkins update centre - though the error there looks like a connection failure. On Thu, Apr 16, 2015 at 10:13 AM, Jānis Balodis janis@gmail.com wrote: Hi, I've experienced a similar behaviour, but with docker plugin v 0.8 and Jenkins starting from version 1.606 till 1.609. If with 1.606 it is still possible to run builds, even though sometimes agents failed to start, 1.609 was impossible to use and I rolled back to 1.605. And this behaviour reproduces also on a test environment where Jenkins ran on Tomcat. Platform used OpenSuse 13.2, docker 1.5.0. I did not find any differences in config files while switching version that could affect this, but v 1.606 had fixes in slave/master communication. Since I was unable to find any network issues, I'm out of ideas on how to debug this issue. Regards, Janis On Sunday, 1 March 2015 07:37:01 UTC+2, Maneesh M P wrote: Hello, I am getting an SSH connection timed out issue with docker plugin. i am using docker plugin verision 0.7 and jenkins version 1.565.2 http://jenkins-ci.org/. Can anyone helping to figure out what is going on wrong ? [02/28/15 21:31:03] [SSH] Opening SSH connection to 54.72.187.35:52576. Connection refused SSH Connection failed with IOException: Connection refused. java.io.IOException: There was a problem while connecting to 54.72.187.35:52576 at com.trilead.ssh2.Connection.connect(Connection.java:818) at com.trilead.ssh2.Connection.connect(Connection.java:687) at com.trilead.ssh2.Connection.connect(Connection.java:587) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1146) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:701) at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:696) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:327) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:193) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:180) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:385) at java.net.Socket.connect(Socket.java:546) at com.trilead.ssh2.transport.TransportManager.establishConnection(TransportManager.java:346) at com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:459) at com.trilead.ssh2.Connection.connect(Connection.java:758) ... 10 more Thanks, Maneesh -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/31bbab3d-3afa-4472-9369-4c518f79d66d%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/31bbab3d-3afa-4472-9369-4c518f79d66d%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/c02baccb-c8e2-4729-bf3b-b7d7898d4eab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Migrate Jenkins Master and Slaves Nodes
Considering that Jenkins stores all the configuration there, it is a solution that will work. Regarding slaves, there shouldn't be any useful information at all. All you should do is update node settings to point to new servers. On Thursday, 16 April 2015 16:28:54 UTC+3, Ashish Yadav wrote: I need to migrate the Jenkins Master server and Slave servers to new infrastructure. What is the ‘best practice’ to perform this migration other than just copying the JENKINS_HOME directory? What other ‘critical’ files need to be migrated over? -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0da91a89-1dd9-478d-933e-e77820225c25%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Sandboxed Maven builds on Jenkins
Hi Jozo, Yes, you should be able to do something like that. However, your feeling isn't quite right: it is fairly common for people to provision hosts and tear-down them down part of the build. One reason this is advantageous is that your cleanup can fail and then your build environment is corrupt and builds start failing (or worse, don't fail but yield bad output silently). Just as an example, here's a group doing it with Vagrant and VMs: http://pivotallabs.com/spinning-useful-vms-quickly-vagrant-puppet-puppet-forge/ Brent On Thu, Apr 16, 2015 at 5:51 PM, Jozef Vilcek jozo.vil...@gmail.com wrote: Actually, Jenkins build environment I use does distributed builds (I do not manage this). I have a feeling that agent setup is rather static. Projects I need to build have native dependencies, which can change a lot. There are many projects, they share build cluster and there dependencies can be often in conflict. Can I do something like: * setup an agent with desired OS and basic setup (libraries) * project X build gets triggered * project is assigned to the agent * pre-build step is executed, which takes from workspace file list of libraries specific to project X and install them * maven build is executed - everything is green * cleanup * ... * project Y build gets triggered * by chance, it is assigned to the same agent * there is no trace of any library installed by project X * pre-build step installs libraries specific to project Y * ... etc On Thu, Apr 16, 2015 at 11:33 PM, Brent Atkinson brent.atkin...@gmail.com wrote: Hi Jozo, Yes, I was using the less incendiary term for the distributed build agents (or slaves), so you found the right docs. Container was referring to something like, but not necessarily Docker containers. When you use agents, you are typically do it to: * unload the load from the build master * need to build on different operating system or architecture from the master * need to build in an isolated or preconfigured environment different from the master That last one would seem to align with your question, unless there's a reason you didn't want to use distributed builds. Hope that helps, Brent -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/ZISjWJ48VNY/unsubscribe . To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGSvDR29di81zROJn3A6d5G7vtK4mF7gZ7CWEwS%3D5GFw%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGSvDR29di81zROJn3A6d5G7vtK4mF7gZ7CWEwS%3D5GFw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAOUjMkwvAoOYTEt8s9d7rKu_GHMurugSHWsQV%3DfFtmZmfbra%3Dw%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-users/CAOUjMkwvAoOYTEt8s9d7rKu_GHMurugSHWsQV%3DfFtmZmfbra%3Dw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0EzDORvkwntDYSMnK92iZ_nTocRU0Qfwt1cMmVfW-cVwA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: How to resolve Process leaked file descriptor issue which caused job failure in Jenkins
I'm surprised if a process leaking a file descriptor would cause a build step to fail. I've never seen it fail in any of the cases where it was reported on my jobs. You may want to confirm that the build step did not fail, independent of whether or not there was a leaked file descriptor. If you're building on Unix, be sure that the build step reports success (exit 0 from a shell script, etc.). Mark Waite On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei weile...@gmail.com wrote: if it is hard to get rid of Process leaked file descriptors, is there anyway I can make Jenkins ignore this failure step (or don't fail it), so I can move on next step. I am looking at Conditional buildstep plugin, but not able to figure out how this plugin work and whether it is the right plugin to achieve above goal? Please help. Thanks Victoria On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote: I need to invoke two window processes in order to start our test after Jenkins build is down. They were normally killed after being brought up, and I receive Process leaked file descriptors. I found someone suggest to do set BUILD_ID=dontKillMe before calling my command to start processes. Good news is that the processes are able to stay. Bad news is Process leaked file descriptors still occur and mark Jenkins job failed, hence, I can't execute any test steps afterwards Any input will be highly appreciated. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtGmaX1FYmqRf4QbMYRL2B%3D%3DCohwFEJgj5zPogVwZeDCYQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Remote Communication Service (Windows Slaves running as a service)
Hi all, I'm trying to configure some Windows 7 workstations to connect to our Jenkins server via a Window service. Currently they connect just fine over JNLP but we have traditionally experienced fewer issues when connecting via DCOM. I'm stuck early in the process, when Jenkins uses Remote Communication Service to detect if Java is installed on the system. I've verified that Jenkins copies RemComSvc.exe from the server to the client's C:\Windows directory but then nothing happens. The console output is: Connecting to mwdev05bltsgs Checking if Java exists ERROR: Failed to prepare Java jcifs.smb.SmbException: 0xC205 at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:563) at jcifs.smb.SmbTransport.send(SmbTransport.java:664) System specs: Server: Jenkins v1.544.3 running on Windows 2008 Server and Java JRE 7u72 server. Client: Windows 7 running Java JRE 7u72 64 bit. JAVA_HOME is set to Java install path, and the System PATH contains %JAVA_HOME%\bin. I have numerous other nodes connected successfully using this setup via DCOM but for some reason there's a handful that refuse to advance past the Checking if Java exists... stage. Does anyone have experience troubleshooting this particular issue? Is there a way that I can manually invoke RemComSvc.exe and see the results myself? Thanks, Terry -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/9AD8B655B5126D4FAE1397203CDDBF2D16768F%40XCH-PHX-205.sw.nos.boeing.com. For more options, visit https://groups.google.com/d/optout.
Re: How to resolve Process leaked file descriptor issue which caused job failure in Jenkins
I think those two lines are independent of one another. The line: Build step 'Execute Windows batch command' marked build as failure hints that the batch script returned a failure code to its calling environment. I believe the default exit value for a batch script is the exit value of the last command executed in that script. If you want to ignore that last return value, add EXIT 0 to the end of the first batch script so that it will always return success. Mark Waite On Thu, Apr 16, 2015 at 2:39 PM Victoria Wei Lei weile...@gmail.com wrote: Mark, the particular step is to call two processes by window batch command, those processes are successfully running after I set BUILD_ID=dontKillMe. Jenkins job was still marked as failure: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information Build step 'Execute Windows batch command' marked build as failure Thanks On Thursday, April 16, 2015 at 3:21:03 PM UTC-5, Mark Waite wrote: I'm surprised if a process leaking a file descriptor would cause a build step to fail. I've never seen it fail in any of the cases where it was reported on my jobs. You may want to confirm that the build step did not fail, independent of whether or not there was a leaked file descriptor. If you're building on Unix, be sure that the build step reports success (exit 0 from a shell script, etc.). Mark Waite On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei weil...@gmail.com wrote: if it is hard to get rid of Process leaked file descriptors, is there anyway I can make Jenkins ignore this failure step (or don't fail it), so I can move on next step. I am looking at Conditional buildstep plugin, but not able to figure out how this plugin work and whether it is the right plugin to achieve above goal? Please help. Thanks Victoria On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote: I need to invoke two window processes in order to start our test after Jenkins build is down. They were normally killed after being brought up, and I receive Process leaked file descriptors. I found someone suggest to do set BUILD_ID=dontKillMe before calling my command to start processes. Good news is that the processes are able to stay. Bad news is Process leaked file descriptors still occur and mark Jenkins job failed, hence, I can't execute any test steps afterwards Any input will be highly appreciated. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2db1326a-066f-4cfe-9adc-3d5b814dad11%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/2db1326a-066f-4cfe-9adc-3d5b814dad11%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAO49JtEe%3DaBvjTzkU6EHcQ349t4JF5oa%3D7H%3DgJMr978AB6DcQA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Sandboxed Maven builds on Jenkins
I have asked this question on stack overflow: http://stackoverflow.com/questions/2995/sandboxed-maven-builds-on-jenkins/ Any help is much appreciated! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b0f048f9-90a6-4237-84d0-caae29fec7a7%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Sandboxed Maven builds on Jenkins
Hi Brent, I am not sure. I am not familiar with Jenkins very well, therefore, most likely, I am missing something :) Can you elaborate or point me to some documentation? What do you mean by containers? With quick search, I have found a section about distributed builds and slave setup. Do you refres to that whne you talk about agents? Jozo On Thu, Apr 16, 2015 at 11:00 PM, Brent Atkinson brent.atkin...@gmail.com wrote: Hi, I may be missing something, but is there a reason you aren't just provisioning VMs or containers and using normal maven builds using agents? Brent On Thu, Apr 16, 2015 at 4:56 PM, Jozo Vilcek jozo.vil...@gmail.com wrote: I have asked this question on stack overflow: http://stackoverflow.com/questions/2995/sandboxed-maven-builds-on-jenkins/ Any help is much appreciated! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b0f048f9-90a6-4237-84d0-caae29fec7a7%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/b0f048f9-90a6-4237-84d0-caae29fec7a7%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/ZISjWJ48VNY/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGpxgA_aoH2zYPbkpWcJkLGqTdhbKP%3D45VKCbkFmQQMQ%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGpxgA_aoH2zYPbkpWcJkLGqTdhbKP%3D45VKCbkFmQQMQ%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAOUjMkzpxEC4n8ZQj%2BS73q%2Bcej7BxS3DHboYfuMNP0y__L%2Bcmw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Sandboxed Maven builds on Jenkins
Hi Jozo, Yes, I was using the less incendiary term for the distributed build agents (or slaves), so you found the right docs. Container was referring to something like, but not necessarily Docker containers. When you use agents, you are typically do it to: * unload the load from the build master * need to build on different operating system or architecture from the master * need to build in an isolated or preconfigured environment different from the master That last one would seem to align with your question, unless there's a reason you didn't want to use distributed builds. Hope that helps, Brent -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGSvDR29di81zROJn3A6d5G7vtK4mF7gZ7CWEwS%3D5GFw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: How to resolve Process leaked file descriptor issue which caused job failure in Jenkins
Mark, the particular step is to call two processes by window batch command, those processes are successfully running after I set BUILD_ID=dontKillMe. Jenkins job was still marked as failure: Process leaked file descriptors. See http://wiki.jenkins-ci.org/display/JENKINS/Spawning+processes+from+build for more information Build step 'Execute Windows batch command' marked build as failure Thanks On Thursday, April 16, 2015 at 3:21:03 PM UTC-5, Mark Waite wrote: I'm surprised if a process leaking a file descriptor would cause a build step to fail. I've never seen it fail in any of the cases where it was reported on my jobs. You may want to confirm that the build step did not fail, independent of whether or not there was a leaked file descriptor. If you're building on Unix, be sure that the build step reports success (exit 0 from a shell script, etc.). Mark Waite On Thu, Apr 16, 2015 at 1:49 PM Victoria Wei Lei weil...@gmail.com javascript: wrote: if it is hard to get rid of Process leaked file descriptors, is there anyway I can make Jenkins ignore this failure step (or don't fail it), so I can move on next step. I am looking at Conditional buildstep plugin, but not able to figure out how this plugin work and whether it is the right plugin to achieve above goal? Please help. Thanks Victoria On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote: I need to invoke two window processes in order to start our test after Jenkins build is down. They were normally killed after being brought up, and I receive Process leaked file descriptors. I found someone suggest to do set BUILD_ID=dontKillMe before calling my command to start processes. Good news is that the processes are able to stay. Bad news is Process leaked file descriptors still occur and mark Jenkins job failed, hence, I can't execute any test steps afterwards Any input will be highly appreciated. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-use...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/2db1326a-066f-4cfe-9adc-3d5b814dad11%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Sandboxed Maven builds on Jenkins
Hi, I may be missing something, but is there a reason you aren't just provisioning VMs or containers and using normal maven builds using agents? Brent On Thu, Apr 16, 2015 at 4:56 PM, Jozo Vilcek jozo.vil...@gmail.com wrote: I have asked this question on stack overflow: http://stackoverflow.com/questions/2995/sandboxed-maven-builds-on-jenkins/ Any help is much appreciated! -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/b0f048f9-90a6-4237-84d0-caae29fec7a7%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/b0f048f9-90a6-4237-84d0-caae29fec7a7%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGpxgA_aoH2zYPbkpWcJkLGqTdhbKP%3D45VKCbkFmQQMQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: How to resolve Process leaked file descriptor issue which caused job failure in Jenkins
if it is hard to get rid of Process leaked file descriptors, is there anyway I can make Jenkins ignore this failure step (or don't fail it), so I can move on next step. I am looking at Conditional buildstep plugin, but not able to figure out how this plugin work and whether it is the right plugin to achieve above goal? Please help. Thanks Victoria On Tuesday, April 14, 2015 at 3:34:39 PM UTC-5, Victoria Wei Lei wrote: I need to invoke two window processes in order to start our test after Jenkins build is down. They were normally killed after being brought up, and I receive Process leaked file descriptors. I found someone suggest to do set BUILD_ID=dontKillMe before calling my command to start processes. Good news is that the processes are able to stay. Bad news is Process leaked file descriptors still occur and mark Jenkins job failed, hence, I can't execute any test steps afterwards Any input will be highly appreciated. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/1b0a16f2-a41d-4037-b793-2727882f64ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Sandboxed Maven builds on Jenkins
Actually, Jenkins build environment I use does distributed builds (I do not manage this). I have a feeling that agent setup is rather static. Projects I need to build have native dependencies, which can change a lot. There are many projects, they share build cluster and there dependencies can be often in conflict. Can I do something like: * setup an agent with desired OS and basic setup (libraries) * project X build gets triggered * project is assigned to the agent * pre-build step is executed, which takes from workspace file list of libraries specific to project X and install them * maven build is executed - everything is green * cleanup * ... * project Y build gets triggered * by chance, it is assigned to the same agent * there is no trace of any library installed by project X * pre-build step installs libraries specific to project Y * ... etc On Thu, Apr 16, 2015 at 11:33 PM, Brent Atkinson brent.atkin...@gmail.com wrote: Hi Jozo, Yes, I was using the less incendiary term for the distributed build agents (or slaves), so you found the right docs. Container was referring to something like, but not necessarily Docker containers. When you use agents, you are typically do it to: * unload the load from the build master * need to build on different operating system or architecture from the master * need to build in an isolated or preconfigured environment different from the master That last one would seem to align with your question, unless there's a reason you didn't want to use distributed builds. Hope that helps, Brent -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/ZISjWJ48VNY/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGSvDR29di81zROJn3A6d5G7vtK4mF7gZ7CWEwS%3D5GFw%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGSvDR29di81zROJn3A6d5G7vtK4mF7gZ7CWEwS%3D5GFw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAOUjMkwvAoOYTEt8s9d7rKu_GHMurugSHWsQV%3DfFtmZmfbra%3Dw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Artifactory issues
Tommy, If you are using bridged networking (definitely not NAT) and are on a network where you can safely assign the VM a different static IP, you need to start by configuring the VM an IP that is not in an IPv4 private address space. Once you have done this, you should attempt to access Artifactory from outside your local network (by browser, etc) to ensure that no routing rules or packet filtering will prevent access from the EC2 instance. If that works, you should be good to go. Hope that helps, Brent On Thu, Apr 16, 2015 at 7:04 PM, Tommy Cregan mmddt00161...@gmail.com wrote: On Thursday, April 16, 2015 at 11:14:33 PM UTC+1, Tommy Cregan wrote: Hi all, I'm having a bit of trouble with the *Artifactory Server* details in Jenkins. I have *Artifactory* running in *Virtual Box* localhost:8081 on *Ubuntu* and I have configured the *Ubuntu* instance of this *VM* with a *Static IP* and bridged networking. I have *Jenkins* running on an Ubuntu instance on *Amazon AWS* and I'm trying to configure the Artifactory Servers IP address in Jenkins configuration page for *Maven* deployment. The IP address keeps failing in the test. What am I doing wrong? Also, are the Default Deployer Credentials supposed to be my *Jenkins* credentials or the Artifactory user and password I have also configured? I am entering the VM's static IP in the Artifactory URL like http://192.168.xx.xx:8081/artifactory. I understand this IP is insulated from external access so what are the alternatives? Any help is much appreciated. Tommy -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/44408722-bb44-462f-a9e5-74dae7432cd3%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/44408722-bb44-462f-a9e5-74dae7432cd3%40googlegroups.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GS883sTFWzSSKTka9G0X9tj%3DvgtPVQPAQOeguMK-fMPg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
Re: Artifactory issues
On Thursday, April 16, 2015 at 11:14:33 PM UTC+1, Tommy Cregan wrote: Hi all, I'm having a bit of trouble with the *Artifactory Server* details in Jenkins. I have *Artifactory* running in *Virtual Box* localhost:8081 on *Ubuntu* and I have configured the *Ubuntu* instance of this *VM* with a *Static IP* and bridged networking. I have *Jenkins* running on an Ubuntu instance on *Amazon AWS* and I'm trying to configure the Artifactory Servers IP address in Jenkins configuration page for *Maven* deployment. The IP address keeps failing in the test. What am I doing wrong? Also, are the Default Deployer Credentials supposed to be my *Jenkins* credentials or the Artifactory user and password I have also configured? I am entering the VM's static IP in the Artifactory URL like http://192.168.xx.xx:8081/artifactory. I understand this IP is insulated from external access so what are the alternatives? Any help is much appreciated. Tommy -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/44408722-bb44-462f-a9e5-74dae7432cd3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Artifactory issues
Hi all, I'm having a bit of trouble with the *Artifactory Server* details in Jenkins. I have *Artifactory* running in *Virtual Box* localhost:8081 on *Ubuntu* and I have configured the *Ubuntu* instance of this *VM* with a *Static IP* and bridged networking. I have *Jenkins* running on an Ubuntu instance on *Amazon AWS* and I'm trying to configure the Artifactory Servers IP address in Jenkins configuration page for *Maven* deployment. The IP address keeps failing in the test. What am I doing wrong? Also are the Default Deployer Credentials supposed to be my *Jenkins* credentials or the Artifactory user and password I have also configured? Any help is much appreciated. Tommy -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/cc89dde2-f5c2-41c6-b8c0-a5ee59724674%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Sandboxed Maven builds on Jenkins
Brent, Thanks for the lead. I will dig into it. It seems there is a light at the end of my tunnel :) Thanks a lot! Jozo On Fri, Apr 17, 2015 at 12:04 AM, Brent Atkinson brent.atkin...@gmail.com wrote: Hi Jozo, Yes, you should be able to do something like that. However, your feeling isn't quite right: it is fairly common for people to provision hosts and tear-down them down part of the build. One reason this is advantageous is that your cleanup can fail and then your build environment is corrupt and builds start failing (or worse, don't fail but yield bad output silently). Just as an example, here's a group doing it with Vagrant and VMs: http://pivotallabs.com/spinning-useful-vms-quickly-vagrant-puppet-puppet-forge/ Brent On Thu, Apr 16, 2015 at 5:51 PM, Jozef Vilcek jozo.vil...@gmail.com wrote: Actually, Jenkins build environment I use does distributed builds (I do not manage this). I have a feeling that agent setup is rather static. Projects I need to build have native dependencies, which can change a lot. There are many projects, they share build cluster and there dependencies can be often in conflict. Can I do something like: * setup an agent with desired OS and basic setup (libraries) * project X build gets triggered * project is assigned to the agent * pre-build step is executed, which takes from workspace file list of libraries specific to project X and install them * maven build is executed - everything is green * cleanup * ... * project Y build gets triggered * by chance, it is assigned to the same agent * there is no trace of any library installed by project X * pre-build step installs libraries specific to project Y * ... etc On Thu, Apr 16, 2015 at 11:33 PM, Brent Atkinson brent.atkin...@gmail.com wrote: Hi Jozo, Yes, I was using the less incendiary term for the distributed build agents (or slaves), so you found the right docs. Container was referring to something like, but not necessarily Docker containers. When you use agents, you are typically do it to: * unload the load from the build master * need to build on different operating system or architecture from the master * need to build in an isolated or preconfigured environment different from the master That last one would seem to align with your question, unless there's a reason you didn't want to use distributed builds. Hope that helps, Brent -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/ZISjWJ48VNY/unsubscribe . To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGSvDR29di81zROJn3A6d5G7vtK4mF7gZ7CWEwS%3D5GFw%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0GGSvDR29di81zROJn3A6d5G7vtK4mF7gZ7CWEwS%3D5GFw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAOUjMkwvAoOYTEt8s9d7rKu_GHMurugSHWsQV%3DfFtmZmfbra%3Dw%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-users/CAOUjMkwvAoOYTEt8s9d7rKu_GHMurugSHWsQV%3DfFtmZmfbra%3Dw%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to a topic in the Google Groups Jenkins Users group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-users/ZISjWJ48VNY/unsubscribe. To unsubscribe from this group and all its topics, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0EzDORvkwntDYSMnK92iZ_nTocRU0Qfwt1cMmVfW-cVwA%40mail.gmail.com https://groups.google.com/d/msgid/jenkinsci-users/CALyHw0EzDORvkwntDYSMnK92iZ_nTocRU0Qfwt1cMmVfW-cVwA%40mail.gmail.com?utm_medium=emailutm_source=footer . For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups Jenkins Users group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAOUjMkwnWEXVdiMfHY61LH_dZ9uHTDmJ3vSAA3WY_f5RTR5pfw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
