RE: Spawning process in a job seems to be non working
My guess is that ant.env(key:'BUILD_ID',value:'DO_NOT_STOP_MY_PROCESS_JENKINS') sets the environment variable in the spawned process, but not in the parent (Jenkins). That value needs to be visible to the Jenkins process. Matthew Webber From: Gábor Lipták [mailto:gabor.lip...@gmail.com] Sent: 03 September 2014 09:37 To: jenkinsci-users@googlegroups.com Subject: Fwd: Spawning process in a job seems to be non working Hi, Could anyone give me a hint, how to fix this: http://stackoverflow.com/q/25639678/337621 Thanks, Gábor Lipták -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Spawning process in a job seems to be non working
As far as I understand it Jenkins generates a BUILD_ID. At the end of the job it iterates the processes, and if any has a matching BUILD_ID, it will be terminated. Do I understand it wrong? If not, then I do exactly what I should do, don't I? 2014. szeptember 3., szerda 10:40:51 UTC+2 időpontban matthew...@diamond.ac.uk a következőt írta: My guess is that ant.env(key:'BUILD_ID',value:'DO_NOT_STOP_MY_PROCESS_JENKINS') sets the environment variable in the spawned process, but not in the parent (Jenkins). That value needs to be visible to the Jenkins process. Matthew Webber From: Gábor Lipták [mailto:gabor@gmail.com javascript:] Sent: 03 September 2014 09:37 To: jenkins...@googlegroups.com javascript: Subject: Fwd: Spawning process in a job seems to be non working Hi, Could anyone give me a hint, how to fix this: http://stackoverflow.com/q/25639678/337621 Thanks, Gábor Lipták -- 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. For more options, visit https://groups.google.com/d/optout.
Building Bar files with Jenkins and Maven
Hello there, I have been struggling with a problem for a while, so just wanted to ask for some help. I set up Git, Bitbucket, Maven and Jenkins but I want to build the *.bar files from WMB in Jenkins using Maven. I can now successfully build a project in Jenkins which fetches files from my repository in Bitbucket. But I couldn't find much information about how to create a pom.xml file and use it in Jenkins, so any help/guidance would be highly appreciated. Thanks! -- 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. For more options, visit https://groups.google.com/d/optout.
Active Directory logins
If the other domain is trusted by the main domain then this should just work. If it is not trusted the you are very likely out of luck. -- 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. For more options, visit https://groups.google.com/d/optout.
How many Remote Nodes can Jenkins manage?
How many Remote Nodes can Jenkins manage?? Are there any limitations/memory issues? What is more effective: 1) 100 Nodes 1 executes per node ? 2) 5 Nodes with 20 executes per node ? TX! -- 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. For more options, visit https://groups.google.com/d/optout.
Re: How many Remote Nodes can Jenkins manage?
On 3 September 2014 14:46, AVIV YAM SIMHAY avi...@gmail.com wrote: How many Remote Nodes can Jenkins manage?? With tuning, we have customers who have got to the 500-1000 slave count. Are there any limitations/memory issues? No hard limits, you will hit CPU limits and entropy source starvation if using SSH slaves What is more effective: 1) 100 Nodes 1 executes per node ? 2) 5 Nodes with 20 executes per node ? Normally the issue is the number of Nodes, so if your nodes can handle the work of 20 concurrent builds, the 5 remoting channels will be less pain than 100. I have done some scaling experiments. on a AWS M3.large using mostly default JVM sizings I can get one of: * 60 JNLP slaves with 2 executors per node. I was able to get up to 60 concurrent builds of the mock-load plugin's type before the jenkins master system load goes above 5 and thus critically impacts the UI performance on an M3.large * 60 standard SSH slaves 2 executors per node. I was able to get up to 10-15 concurrent builds of the mock-load plugin's type before the jenkins master system load goes above 5 and thus critically impacts the UI performance on an M3.large * 60 of CloudBees Jenkins Enterprise NIO SSH Slaves, 2 executors per node. I was able to get up to 120 concurrent builds of the mock-load plugin's type. The jenkins master system load never went above 3. There was back-pressure on the remoting channels once there was more than 25 concurrent builds. The back pressure resulted in increased build times, however the UI remained performant throughout. TX! -- 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. 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. For more options, visit https://groups.google.com/d/optout.
secret option not showing on headless start option
We have an established Jenkins instance where I'm trying to set up a new node, which I've done many times before. However, previously when I've set up a new node it's given the headless command line to use of the format: java -jar slave.jar -jnlpUrl https://hostname:port/computer/nodename/slave-agent.jnlp -secret blahblahblah However, today, the -secret and it's argument is not being shown and so this new node isn't starting up. Any ideas why it's missing and what needs to be done to get it back so I can get this node up? Thanks in advance! Scott -- 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. For more options, visit https://groups.google.com/d/optout.
SOLVED (using workaround): Re: Help needed with CLI puzzle: list-jobs works, but get-job doesn't
Daniel -- your SSH key suggestion did the trick. Thanks. On Friday, August 22, 2014 10:31:31 AM UTC-6, Daniel Beck wrote: There's a known issue with CLI authentication via --username not working for some commands in Jenkins 1.538-1.576. Try using SSH key based authentication. On 22.08.2014, at 17:58, G Dameron gregg@lmco.com javascript: wrote: I think I may be on to something, and I think it's related to the issue https://issues.jenkins-ci.org/browse/JENKINS-21086 I mentioned in my OP. The system log responds this way when I try to to a get-job on project_B: Aug 22, 2014 9:23:07 AM WARNING hudson.cli.handlers.GenericItemOptionHandler$1 run running as anonymous could not find hudson.model.FreeStyleProject@2130a9c[project_B] of class hudson.model.AbstractItem I still have the login just before it, as recommended in the issue. I even tried (a) appending the --username and --password args to the get-job, and even (b) opening up Overall/Read to the anonymous user, then using the restart URL to restart the server. Still no joy. (Thanks, Daniel, for hanging in there through my struggle.) On Thursday, August 21, 2014 6:56:21 PM UTC-6, Daniel Beck wrote: What kind of project is it (e.g. freestyle, maven, multijob, build flow, ...)? What plugin provides it? On 22.08.2014, at 02:31, G Dameron gregg@lmco.com wrote: Just alphanumerics and underscores in the name. We're not using any CloudBees plugins. On Thursday, August 21, 2014 6:14:16 PM UTC-6, Daniel Beck wrote: Are there leading/trailing spaces in the project name? Characters that are not basic printable ASCII, preferably alphanumeric, e.g. characters with special meaning on the command line, like the dollar sign? Are you using the Cloudbees Folders plugin, and the job is actually in a folder? Other than changing project names, are the java calls in your first question unmodified (e.g. no parameters removed)? On 22.08.2014, at 02:01, G Dameron gregg@lmco.com wrote: The job name I'm using meets the URL criterion. (It also meets the snowman criterion, which implies the job's real name and display name are identical, if I'm understanding you correctly). Is there any other string I could/should use for the get-job argument? On Thursday, August 21, 2014 5:43:33 PM UTC-6, Daniel Beck wrote: If it says '/job/foo' in the URL when you view the job, 'foo' is its name. Even if it says something like Project ☃ on the page you're on, in that case '☃' is its display name. (That character used for the display name is supposed to be the Unicode snowman U+2603 if your email client doesn't display it.) To the best of my knowledge, there is no way to determine a project's name from the CLI if the project has a differing display name and the name is not already known, short of writing a plugin or patching Jenkins. On 22.08.2014, at 01:33, G Dameron gregg@lmco.com wrote: What does a job's real name look like? Is there a string I can build up from known parts that would convince get-job that it's a legitimate argument? On Thursday, August 21, 2014 5:09:28 PM UTC-6, Daniel Beck wrote: It's likely the following: list-jobs shows the project's _display name_, but as parameter to commands you need to specify the project's real _name_. It's mind-bogglingly stupid, and there is currently no solution other than not using display names for projects, or patching Jenkins. A possible solution is tracked as JENKINS-22301. -- 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. 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-use...@googlegroups.com. 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-use...@googlegroups.com javascript:. 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. For more options, visit https://groups.google.com/d/optout.
Problems after fix for issue 23263 Move hudson.tasks.junit to a bundled plugin
After going from version 1.575 to 1.578 now it seems the values for TEST_COUNTS is not set properly in Jenkins anymore and my email does not get generated properly Based on the description of this fix I assume this is the issue as the functionality was moved out to a new plugin However the name of the plugin is not shown anywhere What do I need to install to get this to work again? -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Problems after fix for issue 23263 Move hudson.tasks.junit to a bundled plugin
It's a bundled plugin, so you shouldn't need to install anything directly. On Wed, Sep 3, 2014 at 9:06 AM, Reinhard Karbas reinhard.kar...@gmail.com wrote: After going from version 1.575 to 1.578 now it seems the values for TEST_COUNTS is not set properly in Jenkins anymore and my email does not get generated properly Based on the description of this fix I assume this is the issue as the functionality was moved out to a new plugin However the name of the plugin is not shown anywhere What do I need to install to get this to work again? -- 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. For more options, visit https://groups.google.com/d/optout. -- Website: http://earl-of-code.com -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Spawning process in a job seems to be non working
Solution found. See on stackoverflow link. 2014. szeptember 3., szerda 10:43:23 UTC+2 időpontban Gábor Lipták a következőt írta: As far as I understand it Jenkins generates a BUILD_ID. At the end of the job it iterates the processes, and if any has a matching BUILD_ID, it will be terminated. Do I understand it wrong? If not, then I do exactly what I should do, don't I? 2014. szeptember 3., szerda 10:40:51 UTC+2 időpontban matthew...@diamond.ac.uk a következőt írta: My guess is that ant.env(key:'BUILD_ID',value:'DO_NOT_STOP_MY_PROCESS_JENKINS') sets the environment variable in the spawned process, but not in the parent (Jenkins). That value needs to be visible to the Jenkins process. Matthew Webber From: Gábor Lipták [mailto:gabor@gmail.com] Sent: 03 September 2014 09:37 To: jenkins...@googlegroups.com Subject: Fwd: Spawning process in a job seems to be non working Hi, Could anyone give me a hint, how to fix this: http://stackoverflow.com/q/25639678/337621 Thanks, Gábor Lipták -- 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. For more options, visit https://groups.google.com/d/optout.
Events section on wiki
Hi All, We now have an events section on https://wiki.jenkins-ci.org/display/JENKINS/Home. Pls reference this page for upcoming Jenkins events. JUC SF agenda https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+User+Conference+US+West+%28San+Francisco%29+Agendaand future JUC agenda(s) will be on here as well. thanks alyssa -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Events section on wiki
To clarify, the event section is in https://wiki.jenkins-ci.org/display/JENKINS/Events and that it's now linked from the side bar. 2014-09-03 15:13 GMT-07:00 Alyssa Tong alyton...@gmail.com: Hi All, We now have an events section on https://wiki.jenkins-ci.org/display/JENKINS/Home. Pls reference this page for upcoming Jenkins events. JUC SF agenda https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+User+Conference+US+West+%28San+Francisco%29+Agendaand future JUC agenda(s) will be on here as well. thanks alyssa -- 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. For more options, visit https://groups.google.com/d/optout. -- Kohsuke Kawaguchi -- 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. For more options, visit https://groups.google.com/d/optout.
Re: Recently upgraded to Jenkins 1.576 seeing one of the builds running continuously with no changes
On 08/28/2014 09:34 PM, rajesh wrote: Hello, we recently upgraded to Jenkins 1.576 we are using Stash to host the git repository. Jenkins build machine is Linux centos the build keeps running back to back and never stops (about 17000 builds completed ). Have you checked the build pages, console logs or SCM polling logs for the job to see what reason is listed for starting a new build each time? Chris -- 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. For more options, visit https://groups.google.com/d/optout.
