RE: [Build flow plugin] Cannot load balance multiple workflows
Maybe I misunderstand your problem. Let’s keep it simple. The reason the multiple runs of your build flow job run on the same node is because, when selecting a node, it tries to run it one the same node it previously ran on (#2 in the Strategy below). If your nodes had just 1 executor defined, then any consecutive runs would run on different nodes. But with 8 executors, it just runs it there. Scheduling strategy Some slaves are faster, while others are slow. Some slaves are closer (network wise) to a master, others are far away. So doing a good build distribution is a challenge. Currently, Jenkins employs the following strategy: 1. If a project is configured to stick to one computer, that's always honored. 2. Jenkins tries to build a project on the same computer that it was previously built. 3. Jenkins tries to move long builds to slaves, because the amount of network interaction between a master and a slave tends to be logarithmic to the duration of a build (IOW, even if project A takes twice as long to build as project B, it won't require double network transfer.) So this strategy reduces the network overhead. If you have interesting ideas (or better yet, implementations), please let me know. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ty Satrang Sent: Thursday, March 05, 2015 1:52 PM To: jenkinsci-users@googlegroups.com Subject: Re: [Build flow plugin] Cannot load balance multiple workflows if you have a label assigned to many slaves, each with one executor, it will do what you want My slaves do all share the same label and I tried to Restrict where this project can be run and I get the same behavior. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” I suppose this could work, but does it copy the files to the workspace or does it just archive them? I am using a plugin to publish reports from the workspace. On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote: Its strategy is to try to use the same node it last built on. If you have available executors, it will use one. if you have a label assigned to many slaves, each with one executor, it will do what you want. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” From: jenkins...@googlegroups.comjavascript: [mailto:jenkins...@googlegroups.comjavascript:] On Behalf Of Ty Satrang Sent: Thursday, March 05, 2015 3:50 AM To: jenkins...@googlegroups.comjavascript: Subject: [Build flow plugin] Cannot load balance multiple workflows http://i.imgur.com/VEZ1Erc.png For some reason my flow jobs like to all run on a single node instead of choosing an idle node. This is a problem for me because I am using the Node and Label parameter pluginhttps://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin to run the jobs on the same VM as the flow job so I can copy the reports and logs to the parent workspace for publishing. I tried using the Least Load pluginhttp://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin, but I get the same behavior. I also tried the Throttle Concurrent Builds Plug-inhttp://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin to restrict the jobs per node to 1, to no effect. I am just realizing this now but, maybe it would be easier to get the files to the parent workspace another way and let the flow jobs all run on whatever single node they want. (maybe? https://github.com/dnozay/build-flow-toolbox-plugin ) -- 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.comjavascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%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.commailto:jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/0a9cb8a5-d3ef-4f02-8506-0e4b0a986493%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/0a9cb8a5-d3ef-4f02-8506-0e4b0a986493%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
Re: [Build flow plugin] Cannot load balance multiple workflows
Thank you, I did see this copy pasta in another thread, and I did try changing the scheduling strategy with a plug-in. It seems that this particular problem is somewhat exclusive to the Build Flow plugin. It doesn't just queue jobs up, as you can see in the image link, it runs the flow jobs all at once on a single node. On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote: Maybe I misunderstand your problem. Let’s keep it simple. The reason the multiple runs of your build flow job run on the same node is because, when selecting a node, it tries to run it one the same node it previously ran on (#2 in the Strategy below). If your nodes had just 1 executor defined, then any consecutive runs would run on different nodes. But with 8 executors, it just runs it there. *Scheduling strategy* Some slaves are faster, while others are slow. Some slaves are closer (network wise) to a master, others are far away. So doing a good build distribution is a challenge. Currently, Jenkins employs the following strategy: 1. If a project is configured to stick to one computer, that's always honored. 2. Jenkins tries to build a project on the same computer that it was previously built. 3. Jenkins tries to move long builds to slaves, because the amount of network interaction between a master and a slave tends to be logarithmic to the duration of a build (IOW, even if project A takes twice as long to build as project B, it won't require double network transfer.) So this strategy reduces the network overhead. If you have interesting ideas (or better yet, implementations), please let me know. *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *Ty Satrang *Sent:* Thursday, March 05, 2015 1:52 PM *To:* jenkins...@googlegroups.com javascript: *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows if you have a label assigned to many slaves, each with one executor, it will do what you want My slaves do all share the same label and I tried to Restrict where this project can be run and I get the same behavior. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” I suppose this could work, but does it copy the files to the workspace or does it just archive them? I am using a plugin to publish reports from the workspace. On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote: Its strategy is to try to use the same node it last built on. If you have available executors, it will use one. if you have a label assigned to many slaves, each with one executor, it will do what you want. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On Behalf Of *Ty Satrang *Sent:* Thursday, March 05, 2015 3:50 AM *To:* jenkins...@googlegroups.com *Subject:* [Build flow plugin] Cannot load balance multiple workflows http://i.imgur.com/VEZ1Erc.png For some reason my flow jobs like to all run on a single node instead of choosing an idle node. This is a problem for me because I am using the Node and Label parameter plugin https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin to run the jobs on the same VM as the flow job so I can copy the reports and logs to the parent workspace for publishing. I tried using the Least Load plugin http://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin, but I get the same behavior. I also tried the Throttle Concurrent Builds Plug-in http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin to restrict the jobs per node to 1, to no effect. I am just realizing this now but, maybe it would be easier to get the files to the parent workspace another way and let the flow jobs all run on whatever single node they want. (maybe? https://github.com/dnozay/build-flow-toolbox-plugin ) -- 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/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%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
RE: [Build flow plugin] Cannot load balance multiple workflows
Ok, so your upper job Sample Flow does Build(Sample downstream job, node: name-name) And Sample downstream job does a find grep command And your image represents starting Sample flow job 9 times. Since there are 9 available executors on dvm-qa5, all 9 Sample flow jobs start. I expect that 8 of them pend waiting on Sample downstream job to finish (unless you checked “Run concurrent”) And I think you wanted those 9 jobs to be distributed among other nodes in your group like dvm-qa2 and 1? I think that I don’t know how to get it to do what you want but I would not call it a “problem”. This strategy “Jenkins tries to build a project on the same computer that it was previously built.” Is called “affinity” and it helps a great deal when jobs are pulling source code and/or building. It can greatly speed up the process. From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ty Satrang Sent: Thursday, March 05, 2015 5:39 PM To: jenkinsci-users@googlegroups.com Subject: Re: [Build flow plugin] Cannot load balance multiple workflows I am not sure how you want to receive that, but here is a gist of the config that will reproduce the issue. Flow: https://gist.github.com/tsatrangtw/73a391aa75b45cb38235 Downsteam: https://gist.github.com/tsatrangtw/4c20c9a85ce63081c160 On Thursday, March 5, 2015 at 2:15:47 PM UTC-8, rginga wrote: Can you provide a simple example of your main buildflow job? From: jenkins...@googlegroups.comjavascript: [mailto:jenkins...@googlegroups.comjavascript:] On Behalf Of Ty Satrang Sent: Thursday, March 05, 2015 5:12 PM To: jenkins...@googlegroups.comjavascript: Subject: Re: [Build flow plugin] Cannot load balance multiple workflows Thank you, I did see this copy pasta in another thread, and I did try changing the scheduling strategy with a plug-in. It seems that this particular problem is somewhat exclusive to the Build Flow plugin. It doesn't just queue jobs up, as you can see in the image link, it runs the flow jobs all at once on a single node. On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote: Maybe I misunderstand your problem. Let’s keep it simple. The reason the multiple runs of your build flow job run on the same node is because, when selecting a node, it tries to run it one the same node it previously ran on (#2 in the Strategy below). If your nodes had just 1 executor defined, then any consecutive runs would run on different nodes. But with 8 executors, it just runs it there. Scheduling strategy Some slaves are faster, while others are slow. Some slaves are closer (network wise) to a master, others are far away. So doing a good build distribution is a challenge. Currently, Jenkins employs the following strategy: 1. If a project is configured to stick to one computer, that's always honored. 2. Jenkins tries to build a project on the same computer that it was previously built. 3. Jenkins tries to move long builds to slaves, because the amount of network interaction between a master and a slave tends to be logarithmic to the duration of a build (IOW, even if project A takes twice as long to build as project B, it won't require double network transfer.) So this strategy reduces the network overhead. If you have interesting ideas (or better yet, implementations), please let me know. From: jenkins...@googlegroups.commailto:jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of Ty Satrang Sent: Thursday, March 05, 2015 1:52 PM To: jenkins...@googlegroups.commailto:jenkins...@googlegroups.com Subject: Re: [Build flow plugin] Cannot load balance multiple workflows if you have a label assigned to many slaves, each with one executor, it will do what you want My slaves do all share the same label and I tried to Restrict where this project can be run and I get the same behavior. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” I suppose this could work, but does it copy the files to the workspace or does it just archive them? I am using a plugin to publish reports from the workspace. On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote: Its strategy is to try to use the same node it last built on. If you have available executors, it will use one. if you have a label assigned to many slaves, each with one executor, it will do what you want. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” From: jenkins...@googlegroups.commailto:jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of Ty Satrang Sent: Thursday, March 05, 2015 3:50 AM To: jenkins...@googlegroups.commailto:jenkins...@googlegroups.com Subject: [Build flow plugin] Cannot load balance multiple workflows http://i.imgur.com/VEZ1Erc.png
Re: [Build flow plugin] Cannot load balance multiple workflows
I am not sure how you want to receive that, but here is a gist of the config that will reproduce the issue. Flow: https://gist.github.com/tsatrangtw/73a391aa75b45cb38235 Downsteam: https://gist.github.com/tsatrangtw/4c20c9a85ce63081c160 On Thursday, March 5, 2015 at 2:15:47 PM UTC-8, rginga wrote: Can you provide a simple example of your main buildflow job? *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *Ty Satrang *Sent:* Thursday, March 05, 2015 5:12 PM *To:* jenkins...@googlegroups.com javascript: *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows Thank you, I did see this copy pasta in another thread, and I did try changing the scheduling strategy with a plug-in. It seems that this particular problem is somewhat exclusive to the Build Flow plugin. It doesn't just queue jobs up, as you can see in the image link, it runs the flow jobs all at once on a single node. On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote: Maybe I misunderstand your problem. Let’s keep it simple. The reason the multiple runs of your build flow job run on the same node is because, when selecting a node, it tries to run it one the same node it previously ran on (#2 in the Strategy below). If your nodes had just 1 executor defined, then any consecutive runs would run on different nodes. But with 8 executors, it just runs it there. *Scheduling strategy* Some slaves are faster, while others are slow. Some slaves are closer (network wise) to a master, others are far away. So doing a good build distribution is a challenge. Currently, Jenkins employs the following strategy: 1. If a project is configured to stick to one computer, that's always honored. 2. Jenkins tries to build a project on the same computer that it was previously built. 3. Jenkins tries to move long builds to slaves, because the amount of network interaction between a master and a slave tends to be logarithmic to the duration of a build (IOW, even if project A takes twice as long to build as project B, it won't require double network transfer.) So this strategy reduces the network overhead. If you have interesting ideas (or better yet, implementations), please let me know. *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On Behalf Of *Ty Satrang *Sent:* Thursday, March 05, 2015 1:52 PM *To:* jenkins...@googlegroups.com *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows if you have a label assigned to many slaves, each with one executor, it will do what you want My slaves do all share the same label and I tried to Restrict where this project can be run and I get the same behavior. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” I suppose this could work, but does it copy the files to the workspace or does it just archive them? I am using a plugin to publish reports from the workspace. On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote: Its strategy is to try to use the same node it last built on. If you have available executors, it will use one. if you have a label assigned to many slaves, each with one executor, it will do what you want. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On Behalf Of *Ty Satrang *Sent:* Thursday, March 05, 2015 3:50 AM *To:* jenkins...@googlegroups.com *Subject:* [Build flow plugin] Cannot load balance multiple workflows http://i.imgur.com/VEZ1Erc.png For some reason my flow jobs like to all run on a single node instead of choosing an idle node. This is a problem for me because I am using the Node and Label parameter plugin https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin to run the jobs on the same VM as the flow job so I can copy the reports and logs to the parent workspace for publishing. I tried using the Least Load plugin http://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin, but I get the same behavior. I also tried the Throttle Concurrent Builds Plug-in http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin to restrict the jobs per node to 1, to no effect. I am just realizing this now but, maybe it would be easier to get the files to the parent workspace another way and let the flow jobs all run on whatever single node they want. (maybe? https://github.com/dnozay/build-flow-toolbox-plugin ) -- You received this message
Re: [Build flow plugin] Cannot load balance multiple workflows
I am using Jenkins to run tests for several teams, and I would like to be able to run tests concurrently rather than serially. I have a master job that takes parameters (team, tests, code to pull) that I pass using a build flow. I use Jenkins so that I can have this happen on demand or on a schedule. It appears I may be going about this the wrong way. Do you have any suggestions? On Thursday, March 5, 2015 at 2:54:13 PM UTC-8, rginga wrote: Ok, so your upper job Sample Flow does Build(Sample downstream job, node: name-name) And Sample downstream job does a find grep command And your image represents starting Sample flow job 9 times. Since there are 9 available executors on dvm-qa5, all 9 Sample flow jobs start. I expect that 8 of them pend waiting on Sample downstream job to finish (unless you checked “Run concurrent”) And I think you wanted those 9 jobs to be distributed among other nodes in your group like dvm-qa2 and 1? I think that I don’t know how to get it to do what you want but I would not call it a “problem”. This strategy “Jenkins tries to build a project on the same computer that it was previously built.” Is called “affinity” and it helps a great deal when jobs are pulling source code and/or building. It can greatly speed up the process. *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *Ty Satrang *Sent:* Thursday, March 05, 2015 5:39 PM *To:* jenkins...@googlegroups.com javascript: *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows I am not sure how you want to receive that, but here is a gist of the config that will reproduce the issue. Flow: https://gist.github.com/tsatrangtw/73a391aa75b45cb38235 Downsteam: https://gist.github.com/tsatrangtw/4c20c9a85ce63081c160 On Thursday, March 5, 2015 at 2:15:47 PM UTC-8, rginga wrote: Can you provide a simple example of your main buildflow job? *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On Behalf Of *Ty Satrang *Sent:* Thursday, March 05, 2015 5:12 PM *To:* jenkins...@googlegroups.com *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows Thank you, I did see this copy pasta in another thread, and I did try changing the scheduling strategy with a plug-in. It seems that this particular problem is somewhat exclusive to the Build Flow plugin. It doesn't just queue jobs up, as you can see in the image link, it runs the flow jobs all at once on a single node. On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote: Maybe I misunderstand your problem. Let’s keep it simple. The reason the multiple runs of your build flow job run on the same node is because, when selecting a node, it tries to run it one the same node it previously ran on (#2 in the Strategy below). If your nodes had just 1 executor defined, then any consecutive runs would run on different nodes. But with 8 executors, it just runs it there. *Scheduling strategy* Some slaves are faster, while others are slow. Some slaves are closer (network wise) to a master, others are far away. So doing a good build distribution is a challenge. Currently, Jenkins employs the following strategy: 1. If a project is configured to stick to one computer, that's always honored. 2. Jenkins tries to build a project on the same computer that it was previously built. 3. Jenkins tries to move long builds to slaves, because the amount of network interaction between a master and a slave tends to be logarithmic to the duration of a build (IOW, even if project A takes twice as long to build as project B, it won't require double network transfer.) So this strategy reduces the network overhead. If you have interesting ideas (or better yet, implementations), please let me know. *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On Behalf Of *Ty Satrang *Sent:* Thursday, March 05, 2015 1:52 PM *To:* jenkins...@googlegroups.com *Subject:* Re: [Build flow plugin] Cannot load balance multiple workflows if you have a label assigned to many slaves, each with one executor, it will do what you want My slaves do all share the same label and I tried to Restrict where this project can be run and I get the same behavior. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” I suppose this could work, but does it copy the files to the workspace or does it just archive them? I am using a plugin to publish reports from the workspace. On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote: Its strategy is to try to use the same node it last built on. If you have available executors, it will use one. if
RE: [Build flow plugin] Cannot load balance multiple workflows
Can you provide a simple example of your main buildflow job? From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ty Satrang Sent: Thursday, March 05, 2015 5:12 PM To: jenkinsci-users@googlegroups.com Subject: Re: [Build flow plugin] Cannot load balance multiple workflows Thank you, I did see this copy pasta in another thread, and I did try changing the scheduling strategy with a plug-in. It seems that this particular problem is somewhat exclusive to the Build Flow plugin. It doesn't just queue jobs up, as you can see in the image link, it runs the flow jobs all at once on a single node. On Thursday, March 5, 2015 at 11:46:37 AM UTC-8, rginga wrote: Maybe I misunderstand your problem. Let’s keep it simple. The reason the multiple runs of your build flow job run on the same node is because, when selecting a node, it tries to run it one the same node it previously ran on (#2 in the Strategy below). If your nodes had just 1 executor defined, then any consecutive runs would run on different nodes. But with 8 executors, it just runs it there. Scheduling strategy Some slaves are faster, while others are slow. Some slaves are closer (network wise) to a master, others are far away. So doing a good build distribution is a challenge. Currently, Jenkins employs the following strategy: 1. If a project is configured to stick to one computer, that's always honored. 2. Jenkins tries to build a project on the same computer that it was previously built. 3. Jenkins tries to move long builds to slaves, because the amount of network interaction between a master and a slave tends to be logarithmic to the duration of a build (IOW, even if project A takes twice as long to build as project B, it won't require double network transfer.) So this strategy reduces the network overhead. If you have interesting ideas (or better yet, implementations), please let me know. From: jenkins...@googlegroups.comjavascript: [mailto:jenkins...@googlegroups.comjavascript:] On Behalf Of Ty Satrang Sent: Thursday, March 05, 2015 1:52 PM To: jenkins...@googlegroups.comjavascript: Subject: Re: [Build flow plugin] Cannot load balance multiple workflows if you have a label assigned to many slaves, each with one executor, it will do what you want My slaves do all share the same label and I tried to Restrict where this project can be run and I get the same behavior. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” I suppose this could work, but does it copy the files to the workspace or does it just archive them? I am using a plugin to publish reports from the workspace. On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote: Its strategy is to try to use the same node it last built on. If you have available executors, it will use one. if you have a label assigned to many slaves, each with one executor, it will do what you want. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” From: jenkins...@googlegroups.commailto:jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of Ty Satrang Sent: Thursday, March 05, 2015 3:50 AM To: jenkins...@googlegroups.commailto:jenkins...@googlegroups.com Subject: [Build flow plugin] Cannot load balance multiple workflows http://i.imgur.com/VEZ1Erc.png For some reason my flow jobs like to all run on a single node instead of choosing an idle node. This is a problem for me because I am using the Node and Label parameter pluginhttps://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin to run the jobs on the same VM as the flow job so I can copy the reports and logs to the parent workspace for publishing. I tried using the Least Load pluginhttp://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin, but I get the same behavior. I also tried the Throttle Concurrent Builds Plug-inhttp://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin to restrict the jobs per node to 1, to no effect. I am just realizing this now but, maybe it would be easier to get the files to the parent workspace another way and let the flow jobs all run on whatever single node they want. (maybe? https://github.com/dnozay/build-flow-toolbox-plugin ) -- 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.commailto:jenkinsci-use...@googlegroups.com. To view this discussion on the web visit
Re: YUM cacerts and Jenkins Upgrade - Now Git Connection Error - returned status code 128
We verified that the cacert with the correct serial number is trusted in the cacerts that is used by the Java JRE in which Jenkins run. I guess maybe it could still be in a CRL somewhere? -Jimmy On Wednesday, 4 March 2015 16:57:06 UTC-5, Jimmy Ray wrote: One of our admins performed a YUM update on our AWS Linux Jenkins serve. CA Certs were updated as well as Jenkins. Now existing Jobs are failing and when we try to configure jobs with existing GitHub creds, we get the following errors in Jenkins: Failed to connect to repository : Command git ls-remote -h SOME_GIT_REPO HEAD returned status code 128: stdout: stderr: fatal: unable to access 'SOME_GIT_REPO': Peer's certificate issuer has been marked as not trusted by the user. We have verified that the cacerts used by Java were updated via YUM. Was there a change to how Jenkins uses these certs from the Java JRE? Anyone else seen this issue? -Jimmy -- 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/bcfe7741-4fd5-43b5-94b6-4c318b819929%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Publish Over SSH Exception: Channel is broken
Two days ago Publish Over SSH worked fine. Nothing has changed on the remote server, jenkins server or slave. Wake up one day and I get an exception while publishing over ssh. If anyone might have any recommendations or can tell me how to expand the exception which is being chopped off I would appreciate it. Mar 05, 2015 11:09:14 AM WARNING jenkins.plugins.publish_over.BPInstanceConfig perform An exception was caught when invoking perform jenkins.plugins.publish_over.BapPublisherException: Exception when publishing, exception message [java.io.IOException: channel is broken] at jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:68) at jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:37) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2677) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) at ..remote call to mac-slave4(Native Method) at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1356) at hudson.remoting.UserResponse.retrieve(UserRequest.java:221) at hudson.remoting.Channel.call(Channel.java:752) at hudson.FilePath.act(FilePath.java:970) at hudson.FilePath.act(FilePath.java:959) at jenkins.plugins.publish_over.BPInstanceConfig.perform(BPInstanceConfig.java:138) at jenkins.plugins.publish_over.BPPlugin.perform(BPPlugin.java:111) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:770) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:734) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:683) at hudson.model.Run.execute(Run.java:1784) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: 4: java.io.IOException: channel is broken at com.jcraft.jsch.ChannelSftp._put(ChannelSftp.java:623) at com.jcraft.jsch.ChannelSftp.put(ChannelSftp.java:480) at com.jcraft.jsch.ChannelSftp.put(ChannelSftp.java:439) at jenkins.plugins.publish_over_ssh.BapSshClient.transferFile(BapSshClient.java:123) at jenkins.plugins.publish_over_ssh.BapSshClient.transferFile(BapSshClient.java:42) at jenkins.plugins.publish_over.BPTransfer.transferFile(BPTransfer.java:171) at jenkins.plugins.publish_over.BPTransfer.transfer(BPTransfer.java:155) at jenkins.plugins.publish_over.BapPublisher$Performer.transfer(BapPublisher.java:278) at jenkins.plugins.publish_over.BapPublisher$Performer.perform(BapPublisher.java:232) at jenkins.plugins.publish_over.BapPublisher$Performer.access$000(BapPublisher.java:205) at jenkins.plugins.publish_over.BapPublisher.perform(BapPublisher.java:158) at jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:64) at jenkins.plugins.publish_over.BPCallablePublisher.invoke(BPCallablePublisher.java:37) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2677) at hudson.remoting.UserRequest.perform(UserRequest.java:121) at hudson.remoting.UserRequest.perform(UserRequest.java:49) at hudson.remoting.Request$2.run(Request.java:324) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:68) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: channel is broken at com.jcraft.jsch.Session.write(Session.java:1161) at com.jcraft.jsch.ChannelSftp.sendWRITE(ChannelSftp.java:2264) at com.jcraft.jsch.ChannelSftp._put(ChannelSftp.java:603) ... 21 more -- 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
Publish over ssh
Hi Guys, Am new to the Jenkins world. I am trying to connect to an ec2 instance using Jenkins. The whole purpose of the job is to run an svn update and restart gunicorn( for Django app). I am able to connect to the ec2 instance using the Initial configuration. The Test Configurationreturns a success. I pasted the pk file in the text area key. When creating a job in Jenkins all I want to do is run a couple of commands on the remote server, namely: cd /home/ubuntu sh ./update-codebase Is Publish over SSH an overkill for this? If not, what do I enter in the box for the code in publish over ssh ? Thanks for your help. Tanmay -- 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/CALTo_5SbZ%2BcLsgDuFG3nX_QjC9He_pk0gEFJzBp3FKnWMfes9A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
[Build flow plugin] Cannot load balance multiple workflows
http://i.imgur.com/VEZ1Erc.png For some reason my flow jobs like to all run on a single node instead of choosing an idle node. This is a problem for me because I am using the Node and Label parameter plugin https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin to run the jobs on the same VM as the flow job so I can copy the reports and logs to the parent workspace for publishing. I tried using the Least Load plugin http://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin, but I get the same behavior. I also tried the Throttle Concurrent Builds Plug-in http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin to restrict the jobs per node to 1, to no effect. I am just realizing this now but, maybe it would be easier to get the files to the parent workspace another way and let the flow jobs all run on whatever single node they want. (maybe? https://github.com/dnozay/build-flow-toolbox-plugin ) -- 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/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
RE: Want Build number and Build Status of other jobs
I am sorry but I cannot help with Groovy or Jenkins API because I don’t know Groovy much and I don’t know the REST API at all. Actually looking back I see that the scripting language is Jelly but MAYBE groovy can be used. There are some examples here in your Jenkins server: \Jenkins\plugins\email-ext\WEB-INF\classes\hudson\plugins\emailext\templates From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of test.ezshi...@gmail.com Sent: Thursday, March 05, 2015 5:49 AM To: jenkinsci-users@googlegroups.com Subject: Re: Want Build number and Build Status of other jobs Also what are Jenkins API? By using Jenkins API can I get other job details ? Thanks On Thursday, March 5, 2015 at 4:13:39 PM UTC+5:30, test.e...@gmail.commailto:test.e...@gmail.com wrote: Hi, You are right, I would like to use 2nd options though it is complicated b'coz other job are not depended or interconnected with my job, so it's not possible to run from my job. actually I m new with Jenkins can u plz give me hint about second options. I tried with Pre-send Script in extend email notification but there is problem with for groove script plz help me on that. Thanks On Wednesday, March 4, 2015 at 8:00:13 PM UTC+5:30, rginga wrote: I can think of 2 options: If you use Build Flow or Work Flow jobs to run your other jobs, the “build” method returns an object you can use to get that information. You would then need to write that information to a file. Then, as a post build step, use the InjectEnv plugin to setup those values. Then you can use them in your email. If you use the Editable Email plugin, you can create templates containing Groovy code that should be able to fetch anything. This is complicated if you don’t know groovy. From: jenkins...@googlegroups.commailto:jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] On Behalf Of test.e...@gmail.commailto:test.e...@gmail.com Sent: Wednesday, March 04, 2015 8:09 AM To: jenkins...@googlegroups.commailto:jenkins...@googlegroups.com Subject: Want Build number and Build Status of other jobs Hi, I am using Jeninks1.6 version. I have to mail Build Number, Build Status and version details of other jobs from other from my project in jenkins. i.e I want to access other jobs build number and version details in my project. I tried with copy artifact Plugin but it doesn't give me proper details. Is any buddy know solution of this please let me know. 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-use...@googlegroups.commailto:jenkinsci-use...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6bbd6028-ebb5-4f11-8087-23e79fc71b05%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/6bbd6028-ebb5-4f11-8087-23e79fc71b05%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.commailto:jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/7ec0518e-3023-4c14-9230-4fdeaec59abb%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/7ec0518e-3023-4c14-9230-4fdeaec59abb%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/6C6EE445A6F6CE4E8A0FFB51B071A4E26E506EE8%40AMERMBX02.PERKINELMER.NET. For more options, visit https://groups.google.com/d/optout.
Re: Want Build number and Build Status of other jobs
Also what are Jenkins API? By using Jenkins API can I get other job details ? Thanks On Thursday, March 5, 2015 at 4:13:39 PM UTC+5:30, test.e...@gmail.com wrote: Hi, You are right, I would like to use 2nd options though it is complicated b'coz other job are not depended or interconnected with my job, so it's not possible to run from my job. actually I m new with Jenkins can u plz give me hint about second options. I tried with *Pre-send Script* in *extend email notification* but there is problem with for groove script plz help me on that. Thanks On Wednesday, March 4, 2015 at 8:00:13 PM UTC+5:30, rginga wrote: I can think of 2 options: If you use Build Flow or Work Flow jobs to run your other jobs, the “build” method returns an object you can use to get that information. You would then need to write that information to a file. Then, as a post build step, use the InjectEnv plugin to setup those values. Then you can use them in your email. If you use the Editable Email plugin, you can create templates containing Groovy code that should be able to fetch anything. This is complicated if you don’t know groovy. *From:* jenkins...@googlegroups.com [mailto:jenkins...@googlegroups.com] *On Behalf Of *test.e...@gmail.com *Sent:* Wednesday, March 04, 2015 8:09 AM *To:* jenkins...@googlegroups.com *Subject:* Want Build number and Build Status of other jobs Hi, I am using Jeninks1.6 version. I have to mail Build Number, Build Status and version details of other jobs from other from my project in jenkins. i.e I want to access other jobs build number and version details in my project. I tried with *copy artifact Plugin* but it doesn't give me proper details. Is any buddy know solution of this please let me know. 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-use...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6bbd6028-ebb5-4f11-8087-23e79fc71b05%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/6bbd6028-ebb5-4f11-8087-23e79fc71b05%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/7ec0518e-3023-4c14-9230-4fdeaec59abb%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
xunit thresholds issue - latest version 1.94
An excerpt of logs from a jenkins job that runs xunit as a post build action #3318 is removed because status SUCCESS is not to be kept [xUnit] [INFO] - Starting to record. [xUnit] [INFO] - Processing JUnit [xUnit] [INFO] - [JUnit] - 2 test report file(s) were found with the pattern 'tests/unittests-results/*.xml' relative to '/opt/cloudhost/jenkins/workspace/*' for the testing framework 'JUnit'. [xUnit] [INFO] - Converting '*/Case.xml' . [xUnit] [INFO] - Converting '*/Login.xml' . [xUnit] [INFO] - Check 'Failed Tests' threshold.*[xUnit] [INFO] - The percent of tests for this category exceeds the specified 'unstable' threshold percent value. [xUnit] [INFO] - Setting the build status to FAILURE* [xUnit] [INFO] - Stopping recording. Extended Email Publisher is currently disabled in project settings Started calculate disk usage of build I had a shor tlook at the code https://github.com/jenkinsci/xunit-plugin/blob/a0ad57db81ef5a91162dbfa7190a1a8bcb838edd/src/main/java/org/jenkinsci/plugins/xunit/threshold/XUnitThreshold.java#L110and the logger that specifies that this is a category that exceeds an unstable threshold returns the result as an unstable one. But in my case, it always ends up as a failure - even if the previous builds were successful. I'm trying to avoid certain false positives that can occur, and hence the threshold setup. My jenkins version is 1.580.3 and xunit version is 1.94. Any ideas on what can cause this? Tks, Dex -- 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/bc9a060c-f225-4349-ae76-c7a793ce8ccd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Jenkins API + Maven + Eclipse
I hate to +1 but I'm falling into agreement here. The writing of scripts is largely dependant on api knowledge which most people expect their IDE to auto-complete for them. Without the Jenkins artefacts in central, this impedes community development. On 5 March 2015 at 11:25, Sverre Moe sverre@gmail.com wrote: Since I am not familiar with the Jenkins API, I would like to program my Groovy scripts in Eclipse. Having to check the Javadocs every time is quite tedious. Having to write the groovy in Jenkins (in a simple text area) and test it by starting the build is taking forever. I was thinking of creating a maven project, but I cannot find any jar for the Jenkins API in the maven repository. I did find the jenkins repository http://repo.jenkins-ci.org/public, but finding anything useful jenkins api there was like looking for a needle in a haystack. dependency groupIdorg.jenking/groupId artifactIdjenkins-api/artifactId version1.599/version /dependency Using the Jenkins API in Groovy, I reckon it is the same as making a plugin for Jenkins in Java (Same API)? I could even make my code in Java and use it as is in Groovy. Looked a little into the following Plugin tutorial. Though found it a bit complex to set up environment for development. https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-SettingUpEnvironment Perhaps I should ask this in Jenkins Developers instead... -- 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/328208ad-ab8f-46b1-8c15-55368f845cea%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/328208ad-ab8f-46b1-8c15-55368f845cea%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/CAMH6%2BaxCSxnMpSV8dGYCGiVjDLmyxOH3Zim%3D_JvUS0wTtu69ng%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
RE: [Build flow plugin] Cannot load balance multiple workflows
Its strategy is to try to use the same node it last built on. If you have available executors, it will use one. if you have a label assigned to many slaves, each with one executor, it will do what you want. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Ty Satrang Sent: Thursday, March 05, 2015 3:50 AM To: jenkinsci-users@googlegroups.com Subject: [Build flow plugin] Cannot load balance multiple workflows http://i.imgur.com/VEZ1Erc.png For some reason my flow jobs like to all run on a single node instead of choosing an idle node. This is a problem for me because I am using the Node and Label parameter pluginhttps://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin to run the jobs on the same VM as the flow job so I can copy the reports and logs to the parent workspace for publishing. I tried using the Least Load pluginhttp://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin, but I get the same behavior. I also tried the Throttle Concurrent Builds Plug-inhttp://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin to restrict the jobs per node to 1, to no effect. I am just realizing this now but, maybe it would be easier to get the files to the parent workspace another way and let the flow jobs all run on whatever single node they want. (maybe? https://github.com/dnozay/build-flow-toolbox-plugin ) -- 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/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.comhttps://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%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/6C6EE445A6F6CE4E8A0FFB51B071A4E26E507091%40AMERMBX02.PERKINELMER.NET. For more options, visit https://groups.google.com/d/optout.
Re: [Build flow plugin] Cannot load balance multiple workflows
if you have a label assigned to many slaves, each with one executor, it will do what you want My slaves do all share the same label and I tried to Restrict where this project can be run and I get the same behavior. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” I suppose this could work, but does it copy the files to the workspace or does it just archive them? I am using a plugin to publish reports from the workspace. On Thursday, March 5, 2015 at 8:12:59 AM UTC-8, rginga wrote: Its strategy is to try to use the same node it last built on. If you have available executors, it will use one. if you have a label assigned to many slaves, each with one executor, it will do what you want. One way to do what you want is to have each “archive” whatever files you want which puts them onto the Jenkins server and then use “Copy artifacts from another project” *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of *Ty Satrang *Sent:* Thursday, March 05, 2015 3:50 AM *To:* jenkins...@googlegroups.com javascript: *Subject:* [Build flow plugin] Cannot load balance multiple workflows http://i.imgur.com/VEZ1Erc.png For some reason my flow jobs like to all run on a single node instead of choosing an idle node. This is a problem for me because I am using the Node and Label parameter plugin https://wiki.jenkins-ci.org/display/JENKINS/NodeLabel+Parameter+Plugin to run the jobs on the same VM as the flow job so I can copy the reports and logs to the parent workspace for publishing. I tried using the Least Load plugin http://wiki.jenkins-ci.org/display/JENKINS/Least+Load+Plugin, but I get the same behavior. I also tried the Throttle Concurrent Builds Plug-in http://wiki.jenkins-ci.org/display/JENKINS/Throttle+Concurrent+Builds+Plugin to restrict the jobs per node to 1, to no effect. I am just realizing this now but, maybe it would be easier to get the files to the parent workspace another way and let the flow jobs all run on whatever single node they want. (maybe? https://github.com/dnozay/build-flow-toolbox-plugin ) -- 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/3d1d0150-3125-4b54-a846-b0a6687022cf%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/3d1d0150-3125-4b54-a846-b0a6687022cf%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/0a9cb8a5-d3ef-4f02-8506-0e4b0a986493%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: I cant run my calabash-ios successfully on Jenkins. complaining of Ruby.Framework
I have Jenkins 1.601 now and the error still shows. Please help On Thursday, March 5, 2015 at 11:18:37 AM UTC, Daniel Beck wrote: Try updating to Jenkins 1.601. On 05.03.2015, at 12:08, seun are lumm...@gmail.com javascript: wrote: Hi, Please i am new here and i am happy to discover this forum. I need help. here is my configuration: Jenkins version: 1.600 XCode version: 6 Calabash version: 0.13. OS: 10.10 iOS version: 8.0 here is the error from Jenkins Console log: rvm rubies ruby-2.1.1 [ x86_64 ] =* ruby-2.2.0 [ x86_64 ] # = - current # =* - current default # * - default /Users/Shared/Jenkins/Home/jobs/App.iOS.Calabash.Test/workspace Choose scheme name and update it in SCHEME_XC click manage scheme and choose scheme name and find the build configuration BUILD_CONFIG if your features(automation test features) are present in different folder rather than folder where project is present , mention the path in FEATURES_PATH or else remove the argument. APPNAME - name of the application usually same as the scheme name PROJ_LOC - location of xcode project if thats same as current folder remove this option. DEVICE_TARGET=iPhone 6 (8.1 Simulator) APP_BUNDLE_PATH=/Users//Jenkins-Test/workspace/iOS-Youview-cal/build/.app bundle exec cucumber -p ios --tag @test1 /Users/Shared/Jenkins/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.8.3/lib/bundler/definition.rb:380:in `validate_ruby!': Your Ruby version is 2.0.0, but your Gemfile specified 2.2.0 (Bundler::RubyVersionMismatch) from /Users/Shared/Jenkins/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.8.3/lib/bundler.rb:118:in `setup' from /Users/Shared/Jenkins/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.8.3/lib/bundler/setup.rb:18:in `top (required)' from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' Build step 'Execute shell' marked build as failure Finished: FAILURE As you can see, i have ruby-2.2.0 as default and i have it up to date but i dont know where this Your Ruby version is 2.0.0, but your Gemfile specified 2.2.0 is coming from. i only have ruby-2.1.1 and ruby-2.2.0 i cant understand where the 2.0.0 is coming from please can someone suggest to me how to get the Ruby.Framework updated? or any suggestion ? Thanks Johnson -- 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/7765aca6-6f2d-4e3d-9dc1-400eabe1b78d%40googlegroups.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/860296fe-2156-4a92-b581-41423888edac%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: I cant run my calabash-ios successfully on Jenkins. complaining of Ruby.Framework
Try updating to Jenkins 1.601. On 05.03.2015, at 12:08, seun are lummy...@gmail.com wrote: Hi, Please i am new here and i am happy to discover this forum. I need help. here is my configuration: Jenkins version: 1.600 XCode version: 6 Calabash version: 0.13. OS: 10.10 iOS version: 8.0 here is the error from Jenkins Console log: rvm rubies ruby-2.1.1 [ x86_64 ] =* ruby-2.2.0 [ x86_64 ] # = - current # =* - current default # * - default /Users/Shared/Jenkins/Home/jobs/App.iOS.Calabash.Test/workspace Choose scheme name and update it in SCHEME_XC click manage scheme and choose scheme name and find the build configuration BUILD_CONFIG if your features(automation test features) are present in different folder rather than folder where project is present , mention the path in FEATURES_PATH or else remove the argument. APPNAME - name of the application usually same as the scheme name PROJ_LOC - location of xcode project if thats same as current folder remove this option. DEVICE_TARGET=iPhone 6 (8.1 Simulator) APP_BUNDLE_PATH=/Users//Jenkins-Test/workspace/iOS-Youview-cal/build/.app bundle exec cucumber -p ios --tag @test1 /Users/Shared/Jenkins/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.8.3/lib/bundler/definition.rb:380:in `validate_ruby!': Your Ruby version is 2.0.0, but your Gemfile specified 2.2.0 (Bundler::RubyVersionMismatch) from /Users/Shared/Jenkins/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.8.3/lib/bundler.rb:118:in `setup' from /Users/Shared/Jenkins/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.8.3/lib/bundler/setup.rb:18:in `top (required)' from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' Build step 'Execute shell' marked build as failure Finished: FAILURE As you can see, i have ruby-2.2.0 as default and i have it up to date but i dont know where this Your Ruby version is 2.0.0, but your Gemfile specified 2.2.0 is coming from. i only have ruby-2.1.1 and ruby-2.2.0 i cant understand where the 2.0.0 is coming from please can someone suggest to me how to get the Ruby.Framework updated? or any suggestion ? Thanks Johnson -- 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/7765aca6-6f2d-4e3d-9dc1-400eabe1b78d%40googlegroups.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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/916DC50E-54E4-4659-9FD1-024E4D8FA242%40beckweb.net. For more options, visit https://groups.google.com/d/optout.
Jenkins API + Maven + Eclipse
Since I am not familiar with the Jenkins API, I would like to program my Groovy scripts in Eclipse. Having to check the Javadocs every time is quite tedious. Having to write the groovy in Jenkins (in a simple text area) and test it by starting the build is taking forever. I was thinking of creating a maven project, but I cannot find any jar for the Jenkins API in the maven repository. I did find the jenkins repository http://repo.jenkins-ci.org/public, but finding anything useful jenkins api there was like looking for a needle in a haystack. dependency groupIdorg.jenking/groupId artifactIdjenkins-api/artifactId version1.599/version /dependency Using the Jenkins API in Groovy, I reckon it is the same as making a plugin for Jenkins in Java (Same API)? I could even make my code in Java and use it as is in Groovy. Looked a little into the following Plugin tutorial. Though found it a bit complex to set up environment for development. https://wiki.jenkins-ci.org/display/JENKINS/Plugin+tutorial#Plugintutorial-SettingUpEnvironment Perhaps I should ask this in Jenkins Developers instead... -- 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/328208ad-ab8f-46b1-8c15-55368f845cea%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
I cant run my calabash-ios successfully on Jenkins. complaining of Ruby.Framework
Hi, Please i am new here and i am happy to discover this forum. I need help. here is my configuration: Jenkins version: 1.600 XCode version: 6 Calabash version: 0.13. OS: 10.10 iOS version: 8.0 here is the error from Jenkins Console log: rvm rubies ruby-2.1.1 [ x86_64 ] =* ruby-2.2.0 [ x86_64 ] # = - current # =* - current default # * - default /Users/Shared/Jenkins/Home/jobs/App.iOS.Calabash.Test/workspace Choose scheme name and update it in SCHEME_XC click manage scheme and choose scheme name and find the build configuration BUILD_CONFIG if your features(automation test features) are present in different folder rather than folder where project is present , mention the path in FEATURES_PATH or else remove the argument. APPNAME - name of the application usually same as the scheme name PROJ_LOC - location of xcode project if thats same as current folder remove this option. DEVICE_TARGET=iPhone 6 (8.1 Simulator) APP_BUNDLE_PATH=/Users//Jenkins-Test/workspace/iOS-Youview-cal/build/.app bundle exec cucumber -p ios --tag @test1 /Users/Shared/Jenkins/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.8.3/lib/bundler/definition.rb:380:in `validate_ruby!': Your Ruby version is 2.0.0, but your Gemfile specified 2.2.0 (Bundler::RubyVersionMismatch) from /Users/Shared/Jenkins/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.8.3/lib/bundler.rb:118:in `setup' from /Users/Shared/Jenkins/.rvm/gems/ruby-2.2.0@global/gems/bundler-1.8.3/lib/bundler/setup.rb:18:in `top (required)' from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require' Build step 'Execute shell' marked build as failure Finished: FAILURE As you can see, i have ruby-2.2.0 as default and i have it up to date but i dont know where this Your Ruby version is 2.0.0, but your Gemfile specified 2.2.0 is coming from. i only have ruby-2.1.1 and ruby-2.2.0 i cant understand where the 2.0.0 is coming from please can someone suggest to me how to get the Ruby.Framework updated? or any suggestion ? Thanks Johnson -- 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/7765aca6-6f2d-4e3d-9dc1-400eabe1b78d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Want Build number and Build Status of other jobs
Hi, You are right, I would like to use 2nd options though it is complicated b'coz other job are not depended or interconnected with my job, so it's not possible to run from my job. actually I m new with Jenkins can u plz give me hint about second options. I tried with *Pre-send Script* in *extend email notification* but there is problem with for groove script plz help me on that. Thanks On Wednesday, March 4, 2015 at 8:00:13 PM UTC+5:30, rginga wrote: I can think of 2 options: If you use Build Flow or Work Flow jobs to run your other jobs, the “build” method returns an object you can use to get that information. You would then need to write that information to a file. Then, as a post build step, use the InjectEnv plugin to setup those values. Then you can use them in your email. If you use the Editable Email plugin, you can create templates containing Groovy code that should be able to fetch anything. This is complicated if you don’t know groovy. *From:* jenkins...@googlegroups.com javascript: [mailto: jenkins...@googlegroups.com javascript:] *On Behalf Of * test.e...@gmail.com javascript: *Sent:* Wednesday, March 04, 2015 8:09 AM *To:* jenkins...@googlegroups.com javascript: *Subject:* Want Build number and Build Status of other jobs Hi, I am using Jeninks1.6 version. I have to mail Build Number, Build Status and version details of other jobs from other from my project in jenkins. i.e I want to access other jobs build number and version details in my project. I tried with *copy artifact Plugin* but it doesn't give me proper details. Is any buddy know solution of this please let me know. 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-use...@googlegroups.com javascript:. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/6bbd6028-ebb5-4f11-8087-23e79fc71b05%40googlegroups.com https://groups.google.com/d/msgid/jenkinsci-users/6bbd6028-ebb5-4f11-8087-23e79fc71b05%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/6e0c51b2-7733-4bac-bbf8-fbdbee7eec4f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Jenkins won't start up: IndexOutOfBoundsException: Index: 0, Size: 0
Hi Guys, I just updated some plugins (I dont know what they were) from the jenkins gui and I restarted. Then either the error came up or something similar. I had a look at a few blog posts and they said to delete the jpi files and folders from plugins so jenkins would re grab it. I did this and it still comes up with this error. I have no idea how to fix this and I need this up and running soon. Any help would be greatly appreciated. I am totally stuck Thanks hudson.util.HudsonFailedToLoad: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.WebAppMain$3.run(WebAppMain.java:237) Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at jenkins.model.Jenkins.executeReactor(Jenkins.java:914) at jenkins.model.Jenkins.init(Jenkins.java:813) at hudson.model.Hudson.init(Hudson.java:83) at hudson.model.Hudson.init(Hudson.java:79) at hudson.WebAppMain$3.run(WebAppMain.java:225) Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:109) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:903) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:105) ... 8 more Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:635) at java.util.ArrayList.get(ArrayList.java:411) at hudson.ExtensionList.get(ExtensionList.java:158) at hudson.PluginManager$PluginUpdateMonitor.getInstance(PluginManager.java:1257) at hudson.maven.PluginImpl.init(PluginImpl.java:58) ... 13 more -- 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/0321d83a-febf-479a-8c47-7f1603c5305b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
