Re: Downstream cleanup job
Try using the priority sorter plugin to make the cleanup job a higher priority and it will goto the front of the queue so it will execute before any of the other queued jobs. I would probably still use the Throttle Concurrent builds plugin to ensure only one of those jobs run at the same time. Geoff On 26 Mar 2014, at 23:31, Curtis Kline ckl...@evernote.com wrote: I have a scenario that seems like it would be pretty common, and is maybe somewhat similar to the one David Campos posted to the list recently. b1, b2, and b3 are QA testing jobs that each rely on a clean VM. b4 is the job that cleans the VMs. For awhile, we had b4 set up as a downstream job from each of b1, b2, and b3. However sometimes one of the testing jobs would get queued up while another testing job was being run, and would end up running before the cleanup job. That breaks everything. Next we tried using the Throttle Concurrent builds plugin, and put all four of the above jobs into one group with a max concurrent of 1. We had the same problem as before, in that if a testing job was queued while another testing job was running, the cleanup job would run too late. Next we tried three Build Flow jobs, with the Guard - Rescue form. Each testing job would be in the Guard section, and the cleanup job in the Rescue section. We put all three of the Build Flow jobs in one group for Throttle Concurrent Builds. However we immediately found that multiple build flow jobs would run at the same time, as it seems that Build Flow jobs ignore the Throttle Concurrent Builds plugin. Any suggestions here? We just need the cleanup job to always run after a testing job, so the VMs are fresh before the next testing job runs. I am probably missing something simple. Thanks! Curtis -- 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.
Re: Downstream cleanup job
Alternatively, use VM snapshots and launch the VMs you need for each job. Each one will be clean and then thrown away when the job completes. If you only have enough resources for one simultaneous build, you can continue using Throttle Concurrent Builds to maintain the restriction. - Original Message - From: jenkinsci-users@googlegroups.com To: jenkinsci-users@googlegroups.com At: Mar 27 2014 03:08:32 Try using the priority sorter plugin to make the cleanup job a higher priority and it will goto the front of the queue so it will execute before any of the other queued jobs. I would probably still use the Throttle Concurrent builds plugin to ensure only one of those jobs run at the same time. Geoff On 26 Mar 2014, at 23:31, Curtis Kline ckl...@evernote.com wrote: I have a scenario that seems like it would be pretty common, and is maybe somewhat similar to the one David Campos posted to the list recently. b1, b2, and b3 are QA testing jobs that each rely on a “clean” VM. b4 is the job that cleans the VMs. For awhile, we had b4 set up as a downstream job from each of b1, b2, and b3. However sometimes one of the testing jobs would get queued up while another testing job was being run, and would end up running before the cleanup job. That breaks everything. Next we tried using the Throttle Concurrent builds plugin, and put all four of the above jobs into one group with a max concurrent of 1. We had the same problem as before, in that if a testing job was queued while another testing job was running, the cleanup job would run too late. Next we tried three Build Flow jobs, with the Guard - Rescue form. Each testing job would be in the Guard section, and the cleanup job in the Rescue section. We put all three of the Build Flow jobs in one group for Throttle Concurrent Builds. However we immediately found that multiple build flow jobs would run at the same time, as it seems that Build Flow jobs ignore the Throttle Concurrent Builds plugin. Any suggestions here? We just need the cleanup job to always run after a testing job, so the VMs are fresh before the next testing job runs. I am probably missing something simple. Thanks! Curtis -- 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. -- 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.
Our Jenkins instance keeps crashing
Hi Jenkins is crashing on me several times a day. I am running Jenkins 1.552 on Centos 5, in a VM. Jenkins used to be stable for us. The only symptom I see is that my browser shows: An internal server error occurred. Please try again later. I don't know where to start debugging this. The Jenkins system log has several severe errors/warnings: Mar 27, 2014 10:13:32 AM SEVERE jenkins.InitReactorRunner$1 onTaskFailed Failed Inspecting plugin /var/lib/jenkins/plugins/uploaded2537880836547508584.jpi java.io.IOException: Failed to expand /var/lib/jenkins/plugins/uploaded2537880836547508584.jpi at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:430) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:128) at hudson.PluginManager$1$3$1.run(PluginManager.java:237) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:899) 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$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) and: Mar 27, 2014 10:13:35 AM WARNING hudson.ExtensionFinder$Sezpoz scout Failed to scout hudson.maven.MavenModuleSet java.lang.NoClassDefFoundError: hudson/tasks/JavadocArchiver at hudson.maven.MavenModuleSet$DescriptorImpl.clinit(MavenModuleSet.java:1322) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:680) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:311) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:310) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at jenkins.metrics.api.Metrics.postInitialize(Metrics.java:286) at hudson.PluginManager$2$1$2.run(PluginManager.java:373) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:899) 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$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassNotFoundException: hudson.tasks.JavadocArchive Any suggestions what I should do please? Best regards David -- 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: Downstream cleanup job
You can use build flow extensions plugin to block[1] the flows. /James [1] https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Extensions+Plugin#BuildFlowExtensionsPlugin-block From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Curtis Kline Sent: 26 March 2014 23:31 To: jenkinsci-users@googlegroups.com Subject: Downstream cleanup job I have a scenario that seems like it would be pretty common, and is maybe somewhat similar to the one David Campos posted to the list recently. b1, b2, and b3 are QA testing jobs that each rely on a “clean” VM. b4 is the job that cleans the VMs. For awhile, we had b4 set up as a downstream job from each of b1, b2, and b3. However sometimes one of the testing jobs would get queued up while another testing job was being run, and would end up running before the cleanup job. That breaks everything. Next we tried using the Throttle Concurrent builds plugin, and put all four of the above jobs into one group with a max concurrent of 1. We had the same problem as before, in that if a testing job was queued while another testing job was running, the cleanup job would run too late. Next we tried three Build Flow jobs, with the Guard - Rescue form. Each testing job would be in the Guard section, and the cleanup job in the Rescue section. We put all three of the Build Flow jobs in one group for Throttle Concurrent Builds. However we immediately found that multiple build flow jobs would run at the same time, as it seems that Build Flow jobs ignore the Throttle Concurrent Builds plugin. Any suggestions here? We just need the cleanup job to always run after a testing job, so the VMs are fresh before the next testing job runs. I am probably missing something simple. Thanks! Curtis -- 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. 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.
RE: Our Jenkins instance keeps crashing
Fixed exceptions in System Log by deleting rogue .jpi file and enabling JavaDoc plugin. Will wait and see if that fixes the crashes. David From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich Sent: 27 March 2014 10:24 To: jenkinsci-users@googlegroups.com Subject: Our Jenkins instance keeps crashing Hi Jenkins is crashing on me several times a day. I am running Jenkins 1.552 on Centos 5, in a VM. Jenkins used to be stable for us. The only symptom I see is that my browser shows: An internal server error occurred. Please try again later. I don't know where to start debugging this. The Jenkins system log has several severe errors/warnings: Mar 27, 2014 10:13:32 AM SEVERE jenkins.InitReactorRunner$1 onTaskFailed Failed Inspecting plugin /var/lib/jenkins/plugins/uploaded2537880836547508584.jpi java.io.IOException: Failed to expand /var/lib/jenkins/plugins/uploaded2537880836547508584.jpi at hudson.ClassicPluginStrategy.explode(ClassicPluginStrategy.java:430) at hudson.ClassicPluginStrategy.createPluginWrapper(ClassicPluginStrategy.java:128) at hudson.PluginManager$1$3$1.run(PluginManager.java:237) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:899) 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$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) and: Mar 27, 2014 10:13:35 AM WARNING hudson.ExtensionFinder$Sezpoz scout Failed to scout hudson.maven.MavenModuleSet java.lang.NoClassDefFoundError: hudson/tasks/JavadocArchiver at hudson.maven.MavenModuleSet$DescriptorImpl.clinit(MavenModuleSet.java:1322) at java.lang.Class.forName0(Native Method) at java.lang.Class.forName(Unknown Source) at hudson.ExtensionFinder$Sezpoz.scout(ExtensionFinder.java:680) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:311) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:310) at hudson.ExtensionList.load(ExtensionList.java:295) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:248) at hudson.ExtensionList.iterator(ExtensionList.java:138) at jenkins.metrics.api.Metrics.postInitialize(Metrics.java:286) at hudson.PluginManager$2$1$2.run(PluginManager.java:373) at org.jvnet.hudson.reactor.TaskGraphBuilder$TaskImpl.run(TaskGraphBuilder.java:169) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at jenkins.model.Jenkins$7.runTask(Jenkins.java:899) 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$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Caused by: java.lang.ClassNotFoundException: hudson.tasks.JavadocArchive Any suggestions what I should do please? Best regards David Click herehttps://www.mailcontrol.com/sr/3!E5NFrSgRvGX2PQPOmvUn0PzDqJDjTiI3TxHdp4XbFIPW90YBWeuJrmx3H0qkiWs0mx5zUqxysfmF8UmgH1OQ== to report this email as spam. -- 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. 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.
RE: Get all Jenkins Jobs name in Build Flow Plugin
Hello again, If anyone have a solution for this? Or more documentation ? Thanks a lot De : jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] De la part de COLLIGNON, Thomas Envoyé : jeudi 6 mars 2014 09:40 À : 'jenkinsci-users@googlegroups.com' Objet : Get all Jenkins Jobs name in Build Flow Plugin Hello, I would know if it's possible to get all Jenkins jobs name in Build Flow Plugin? In order to use this as parameters for trigger particular job. Thanks a lot Thomas Collignon -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- 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 to fix java.lang.reflect.InvocationTargetException ?
Hi One of our Jenkins jobs is generating an exception that is reported in the System Log. It is a simple job that runs some DOS batch commands. In case it is relevant, we don't use Maven. The exception is below. Any thoughts about the reason please? We are running Jenkins 1.552 on Centos 5. Best regards David Mar 27, 2014 10:54:13 AM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.transientActions in /jenkins/job/Regression_test_TestParams_MSVC/580/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at
Re: Get all Jenkins Jobs name in Build Flow Plugin
import hudson.model.* def hi = hudson.model.Hudson.instance def allJobs = hi.getItems(hudson.model.Job) On Thu, Mar 6, 2014 at 12:39 AM, COLLIGNON, Thomas t-collig...@efluid.frwrote: Hello, I would know if it's possible to get all Jenkins jobs name in Build Flow Plugin? In order to use this as parameters for trigger particular job. Thanks a lot Thomas Collignon -- 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/groups/opt_out. -- Marc MacIntyre -- 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 to wait for downstream jobs to complete in groovy?
I config some 'job templete' by the power of the plugin 'job generator plugin'. And I've written a groovy script to parse a XML file which describes the build flow according to the instruction of the page: http://stackoverflow.com/questions/11581620/call-a-jenkins-job-by-using-a-variable-for-build-the-name However, when I invoke the groovy script by the scriptler plugin, the Jenkins service stops. My groovy code is here: https://gist.github.com/LevskiWeng/c19039ff765c6f30bf4c My problem is: When the job is invoked by scriptler, the Jenkins JVM will get stopped. I've noticed that if the job invoked gets finished quickly, everything seems OK, but when the job takes more than 15s to complete, the Jenkins JVM will stop. So I think it's my code's fault, but I've no idea how could I correct the problem, is Thread.sleep() a bad idea here? Any suggestion will be appreciated, thanks. -- Levski Weng www.levskiweng.me -- 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: Get all Jenkins Jobs name in Build Flow Plugin
It works ! Thank you a lot ! De : jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] De la part de Marc MacIntyre Envoyé : jeudi 27 mars 2014 12:30 À : jenkinsci-users@googlegroups.com Objet : Re: Get all Jenkins Jobs name in Build Flow Plugin import hudson.model.* def hi = hudson.model.Hudson.instance def allJobs = hi.getItems(hudson.model.Job) On Thu, Mar 6, 2014 at 12:39 AM, COLLIGNON, Thomas t-collig...@efluid.frmailto:t-collig...@efluid.fr wrote: Hello, I would know if it's possible to get all Jenkins jobs name in Build Flow Plugin? In order to use this as parameters for trigger particular job. Thanks a lot Thomas Collignon -- 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. For more options, visit https://groups.google.com/groups/opt_out. -- Marc MacIntyre -- 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. 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.
Collect Testresults on Slave-Job
Hello, I have the following setup: jenkins (v1.549) testlink (v1.9.7) jenkins SSH Slaves plugin (v1.6) jenkins-testlink-plugin (3.10) My freestyle job is configured pretty standard: - Invoke TestLink: - TestLink Configuration: ... Custom Fields: Test Case Name - Test Execution: - Iterative Test Build Steps: Shell script is executed to produce a tap file - Result Seeking Strategy - Include Pattern: *.tap - Key Custom Field: Test Case Name - Attach TAP Stream: enabled Now when the job is ran on the master, everything is fine: I can see the expected in the TestLink section like: Build ID: xyz Build Name: xxx Passed: 1 ... Total: 1 However, when ran on the slave the Testlink plugin is somehow not aware that the test has been exectued. Because it reports: *Not Run: 1* Build ID: xyz Build Name: xxx Passed: 0 ... Not Run: 1 Total: 1 However, the build output is pretty much the same, in both cases (master and slave): ... Found 1 automated test cases in TestLink. Sorting automated test cases by TestLink test plan execution order. Executing single Build Steps. Executing iterative Build Steps. Merging build environment variables with data retrieved from TestLink. ... Looking for the test results of TestLink test cases. Found 1 test result(s). Finished: SUCCESS Is Testlink plugin supposed to work with slave configuration ? Thanks, Marian -- 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 to access jobs variables with Build Flow Plugin?
Can I use Groovy Postbuild with Build Flow or should I use only the first?
On Tuesday, March 25, 2014 4:51:54 PM UTC, rginga wrote:
I do not have an answer but I have some knowledge. The only thing you
have left after “Build” runs is “b”. from the build flow Wiki page:
Environment variables from a job can be obtained using the following,
which is especially useful for getting things like the checkout revision
used by the SCM plugin ('P4_CHANGELIST', 'GIT_REVISION', etc) :
def revision = b.environment.get( GIT_REVISION )
So, if you predefine the environment of “Build” to have those variables,
then the above command will get them. But it might only get the original
value and not any changed value that “Build” sets.
There is another plugin called Groovy Postbuild which give you access to
the “b” build object of “Build” while it is running:
Executes a groovy script in the Hudson JVM. Typically, the script checks
some conditions and changes accordingly the build result, puts badges next
to the build in the build history and/or displays information on the build
summary page.
The groovy script can use the variable *manager*, which provides access
to the following objects and methods:
- hudson - the current Hudson instance.
- build - the current build.
- listener - the build listener.
If you can figure out a way of “setting” the environment variables in the
object “build” at the end of job “Build”, then you might be able to use
b.environment.get
get it. but I am not yet a Groovy Guru. Perhaps there is a
build.environment.set method.
*From:* jenkins...@googlegroups.com javascript: [mailto:
jenkins...@googlegroups.com javascript:] *On Behalf Of *
h...@renatorodrigues.me javascript:
*Sent:* Tuesday, March 25, 2014 11:25 AM
*To:* jenkins...@googlegroups.com javascript:
*Subject:* How to access jobs variables with Build Flow Plugin?
My Build Flow job has the following structure:
b = build(Build)
parallel (
{
build(Test-Device, device: id1)
},
{
build(Test-Device, device: id2)
}
)
In the Build job, I have a variable: export DEVICES=id1 id2. From the
flow DSL, how can I have access to this variable in order to use its value
on the consequent parallel jobs?
--
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.
RE: How to access jobs variables with Build Flow Plugin?
My thought is to use Groovy Postbuild in your “Build” job in order to
set/change the environment variables. Then in your Build Flow job, use
b.environment.get to get that value.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of h...@renatorodrigues.me
Sent: Thursday, March 27, 2014 11:29 AM
To: jenkinsci-users@googlegroups.com
Subject: Re: How to access jobs variables with Build Flow Plugin?
Can I use Groovy Postbuild with Build Flow or should I use only the first?
On Tuesday, March 25, 2014 4:51:54 PM UTC, rginga wrote:
I do not have an answer but I have some knowledge. The only thing you have left
after “Build” runs is “b”. from the build flow Wiki page:
Environment variables from a job can be obtained using the following, which is
especially useful for getting things like the checkout revision used by the SCM
plugin ('P4_CHANGELIST', 'GIT_REVISION', etc) :
def revision = b.environment.get( GIT_REVISION )
So, if you predefine the environment of “Build” to have those variables, then
the above command will get them. But it might only get the original value and
not any changed value that “Build” sets.
There is another plugin called Groovy Postbuild which give you access to the
“b” build object of “Build” while it is running:
Executes a groovy script in the Hudson JVM. Typically, the script checks some
conditions and changes accordingly the build result, puts badges next to the
build in the build history and/or displays information on the build summary
page.
The groovy script can use the variable manager, which provides access to the
following objects and methods:
* hudson - the current Hudson instance.
* build - the current build.
* listener - the build listener.
If you can figure out a way of “setting” the environment variables in the
object “build” at the end of job “Build”, then you might be able to use
b.environment.get get it. but I am not yet a Groovy Guru. Perhaps there is a
build.environment.set method.
From: jenkins...@googlegroups.comjavascript:
[mailto:jenkins...@googlegroups.comjavascript:] On Behalf Of
h...@renatorodrigues.mejavascript:
Sent: Tuesday, March 25, 2014 11:25 AM
To: jenkins...@googlegroups.comjavascript:
Subject: How to access jobs variables with Build Flow Plugin?
My Build Flow job has the following structure:
b = build(Build)
parallel (
{
build(Test-Device, device: id1)
},
{
build(Test-Device, device: id2)
}
)
In the Build job, I have a variable: export DEVICES=id1 id2. From the flow
DSL, how can I have access to this variable in order to use its value on the
consequent parallel jobs?
--
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:.
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.
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.
RE: Parallel builds with Build Flow
I think you can only do that in each job definition, that is in the
specification for Job1, 2, and 3. I don’t think you can pass anything to the
build method to do that.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of h...@renatorodrigues.me
Sent: Thursday, March 27, 2014 11:36 AM
To: jenkinsci-users@googlegroups.com
Subject: Parallel builds with Build Flow
Build Flow plugin allows one to have parallel builds in a simple way:
parallel (
// job 1, 2 and 3 will be scheduled in parallel.
{ build(job1) },
{ build(job2) },
{ build(job3) }
)
// job4 will be triggered after jobs 1, 2 and 3 complete
build(job4)
Is it possible to delegate a specific node for each job on the parallel
environment?
--
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.
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.
Re: Parallel builds with Build Flow
Use the node label parameter plugin and pass the node name as a param to the
build. Build flow accepts parameters as maps, check the docs.
Sent from my iPhone
On Mar 27, 2014, at 8:53 AM, Ginga, Dick dick.gi...@perkinelmer.com wrote:
I think you can only do that in each job definition, that is in the
specification for Job1, 2, and 3. I don’t think you can pass anything to the
build method to do that.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of h...@renatorodrigues.me
Sent: Thursday, March 27, 2014 11:36 AM
To: jenkinsci-users@googlegroups.com
Subject: Parallel builds with Build Flow
Build Flow plugin allows one to have parallel builds in a simple way:
parallel (
// job 1, 2 and 3 will be scheduled in parallel.
{ build(job1) },
{ build(job2) },
{ build(job3) }
)
// job4 will be triggered after jobs 1, 2 and 3 complete
build(job4)
Is it possible to delegate a specific node for each job on the parallel
environment?
--
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.
--
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: Parallel builds with Build Flow
Ah, good to know, thanks.
From: jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of Marc MacIntyre
Sent: Thursday, March 27, 2014 12:02 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: Parallel builds with Build Flow
Use the node label parameter plugin and pass the node name as a param to the
build. Build flow accepts parameters as maps, check the docs.
Sent from my iPhone
On Mar 27, 2014, at 8:53 AM, Ginga, Dick
dick.gi...@perkinelmer.commailto:dick.gi...@perkinelmer.com wrote:
I think you can only do that in each job definition, that is in the
specification for Job1, 2, and 3. I don’t think you can pass anything to the
build method to do that.
From: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com
[mailto:jenkinsci-users@googlegroups.com] On Behalf Of
h...@renatorodrigues.memailto:h...@renatorodrigues.me
Sent: Thursday, March 27, 2014 11:36 AM
To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com
Subject: Parallel builds with Build Flow
Build Flow plugin allows one to have parallel builds in a simple way:
parallel (
// job 1, 2 and 3 will be scheduled in parallel.
{ build(job1) },
{ build(job2) },
{ build(job3) }
)
// job4 will be triggered after jobs 1, 2 and 3 complete
build(job4)
Is it possible to delegate a specific node for each job on the parallel
environment?
--
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.
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.
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.
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.
Re: Parallel builds with Build Flow
*rginga*, I'm aware of that possibility but in my case I'm paralleling the
same job, just with different parameters:
parallel (
// job 1, 2 and 3 will be scheduled in parallel.
{ build(job1, id:1, type:foo) },
{ build(job2, id:2, type:bar) }
)
// job4 will be triggered after jobs 1, 2 and 3 complete
build(job4)
*Marc MacIntyre*, I will try that. Thank you very much.
On Thursday, March 27, 2014 4:01:59 PM UTC, Marc MacIntyre wrote:
Use the node label parameter plugin and pass the node name as a param to
the build. Build flow accepts parameters as maps, check the docs.
Sent from my iPhone
On Mar 27, 2014, at 8:53 AM, Ginga, Dick
dick@perkinelmer.comjavascript:
wrote:
I think you can only do that in each job definition, that is in the
specification for Job1, 2, and 3. I don’t think you can pass anything to
the build method to do that.
*From:* jenkins...@googlegroups.com javascript: [
mailto:jenk...@googlegroups.com javascript:] *On Behalf Of *
h...@renatorodrigues.me javascript:
*Sent:* Thursday, March 27, 2014 11:36 AM
*To:* jenkins...@googlegroups.com javascript:
*Subject:* Parallel builds with Build Flow
Build Flow plugin allows one to have parallel builds in a simple way:
parallel (
// job 1, 2 and 3 will be scheduled in parallel.
{ build(job1) },
{ build(job2) },
{ build(job3) }
)
// job4 will be triggered after jobs 1, 2 and 3 complete
build(job4)
Is it possible to delegate a *specific node for each job *on the parallel
environment?
--
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-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.
Re: Maven Builds - Slow Build Times on Jenkins Slaves
Hi, just wanted to check-in if anyone has insights into this or if anyone else is experiencing similar issues with mvn build jobs running on jenkins slaves? Thanks. On Saturday, March 22, 2014 11:38:35 AM UTC-7, Kai wrote: Sorry for the late reply. Actually, it runs pretty quick when I run my maven command manually on the slave - takes about ~8 mins. However, when I run through Jenkins, it takes between ~18-19mins for the job to complete. Here are a few snippets from the console logs. Most of the areas where it tends to be slow is when it says deleting .../target directory, then says archiving disabled and stays there for like 2 mins usually, then moves on. And it does this for each maven module that's part of the project, so it adds up. Also, takes some time, after archiving steps, then says archiving disabled, usually like up to 2 min delay before moving on. *Snippets from Console Log* *19:56:10 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ test-project-parent ---19:56:10 [INFO] Deleting /var/lib/jenkins/workspace/test-project/target19:56:13 [JENKINS] Archiving disabled19:58:33 [INFO]20:03:32 [JENKINS] Archiving site from /var/lib/jenkins/workspace/test-project-main/test-project/target/site to /var/lib/jenkins/jobs/test-project-main/site/test-project20:03:32 [JENKINS] Archiving disabled20:05:51 [INFO] * On Tuesday, March 18, 2014 11:15:49 PM UTC-7, Baptiste Mathus wrote: Outside Jenkins, I mean. Le 19 mars 2014 07:15, Baptiste Mathus bma...@batmat.net a écrit : Is it also slow if you run the maven build manually on that slave? Le 16 mars 2014 22:57, Kai kaite...@gmail.com a écrit : Hi, We are currently on Jenkins 1.551 and are experiencing significant maven build slowness on our jenkins slaves. It seems deleting the target directory takes forever. Also, during the site phase, a step: Archiving site from ... comes and takes a while (even though archiving is disabled), then it says archiving disabled and moves on. However, when the build runs on the master, I don't experience this slowness and deleting the target directory is really quick. Has anyone else experienced this issue or know what could be causing the slowness when building on Jenkin slaves? Thank you so much! -- 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-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Parallel builds with Build Flow
Just correcting a typo with job names.
parallel (
{ build(job1, id:1, type:foo) },
{ build(job1, id:2, type:bar) }
)
On Thursday, March 27, 2014 4:07:33 PM UTC, h...@renatorodrigues.me wrote:
*rginga*, I'm aware of that possibility but in my case I'm paralleling
the same job, just with different parameters:
parallel (
// job 1, 2 and 3 will be scheduled in parallel.
{ build(job1, id:1, type:foo) },
{ build(job2, id:2, type:bar) }
)
// job4 will be triggered after jobs 1, 2 and 3 complete
build(job4)
*Marc MacIntyre*, I will try that. Thank you very much.
On Thursday, March 27, 2014 4:01:59 PM UTC, Marc MacIntyre wrote:
Use the node label parameter plugin and pass the node name as a param to
the build. Build flow accepts parameters as maps, check the docs.
Sent from my iPhone
On Mar 27, 2014, at 8:53 AM, Ginga, Dick dick@perkinelmer.com
wrote:
I think you can only do that in each job definition, that is in the
specification for Job1, 2, and 3. I don’t think you can pass anything to
the build method to do that.
*From:* jenkins...@googlegroups.com [mailto:jenk...@googlegroups.com] *On
Behalf Of *h...@renatorodrigues.me
*Sent:* Thursday, March 27, 2014 11:36 AM
*To:* jenkins...@googlegroups.com
*Subject:* Parallel builds with Build Flow
Build Flow plugin allows one to have parallel builds in a simple way:
parallel (
// job 1, 2 and 3 will be scheduled in parallel.
{ build(job1) },
{ build(job2) },
{ build(job3) }
)
// job4 will be triggered after jobs 1, 2 and 3 complete
build(job4)
Is it possible to delegate a *specific node for each job *on the parallel
environment?
--
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-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
RE: How to fix java.lang.reflect.InvocationTargetException ?
This problem seems to have gone away. Best regards David From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich Sent: 27 March 2014 11:24 To: jenkinsci-users@googlegroups.com Subject: How to fix java.lang.reflect.InvocationTargetException ? Hi One of our Jenkins jobs is generating an exception that is reported in the System Log. It is a simple job that runs some DOS batch commands. In case it is relevant, we don't use Maven. The exception is below. Any thoughts about the reason please? We are running Jenkins 1.552 on Centos 5. Best regards David Mar 27, 2014 10:54:13 AM WARNING hudson.ExpressionFactory2$JexlExpression evaluate Caught exception evaluating: it.transientActions in /jenkins/job/Regression_test_TestParams_MSVC/580/. Reason: java.lang.reflect.InvocationTargetException java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314) at org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185) at org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:58) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.tags.core.CoreTagLibrary$1.run(CoreTagLibrary.java:98) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.JellyViewScript.run(JellyViewScript.java:81) at org.kohsuke.stapler.jelly.IncludeTag.doTag(IncludeTag.java:147) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at
Jenkins 1.556 still unstable - HTTP Error 404
Hi Sorry for my many recent posts but I am finding it difficult to achieve a stable configuration of Jenkins. I have just upgraded from 1.552 to 1.556 and now see this error when I login: HTTP ERROR 404 Problem accessing /jenkins/;jsessionid=1ktrqn7avifn613oup7g5x0q2v. Reason: Not Found The problem remains if I revert to 1.552. Any suggestions please? Best regards David -- 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: Maven Builds - Slow Build Times on Jenkins Slaves
If using the maven type job, try using a freestyle one and see if you got a different result. Apart from that, it would be really helpful if you could generate many stacktraces in a dedicated jira, take them during those apparently idle times to see what it's doing. Cheers Le 27 mars 2014 17:08, Kai kaitea2...@gmail.com a écrit : Hi, just wanted to check-in if anyone has insights into this or if anyone else is experiencing similar issues with mvn build jobs running on jenkins slaves? Thanks. On Saturday, March 22, 2014 11:38:35 AM UTC-7, Kai wrote: Sorry for the late reply. Actually, it runs pretty quick when I run my maven command manually on the slave - takes about ~8 mins. However, when I run through Jenkins, it takes between ~18-19mins for the job to complete. Here are a few snippets from the console logs. Most of the areas where it tends to be slow is when it says deleting .../target directory, then says archiving disabled and stays there for like 2 mins usually, then moves on. And it does this for each maven module that's part of the project, so it adds up. Also, takes some time, after archiving steps, then says archiving disabled, usually like up to 2 min delay before moving on. *Snippets from Console Log* *19:56:10 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ test-project-parent ---19:56:10 [INFO] Deleting /var/lib/jenkins/workspace/test-project/target19:56:13 [JENKINS] Archiving disabled19:58:33 [INFO]20:03:32 [JENKINS] Archiving site from /var/lib/jenkins/workspace/test-project-main/test-project/target/site to /var/lib/jenkins/jobs/test-project-main/site/test-project20:03:32 [JENKINS] Archiving disabled20:05:51 [INFO] * On Tuesday, March 18, 2014 11:15:49 PM UTC-7, Baptiste Mathus wrote: Outside Jenkins, I mean. Le 19 mars 2014 07:15, Baptiste Mathus bma...@batmat.net a écrit : Is it also slow if you run the maven build manually on that slave? Le 16 mars 2014 22:57, Kai kaite...@gmail.com a écrit : Hi, We are currently on Jenkins 1.551 and are experiencing significant maven build slowness on our jenkins slaves. It seems deleting the target directory takes forever. Also, during the site phase, a step: Archiving site from ... comes and takes a while (even though archiving is disabled), then it says archiving disabled and moves on. However, when the build runs on the master, I don't experience this slowness and deleting the target directory is really quick. Has anyone else experienced this issue or know what could be causing the slowness when building on Jenkin slaves? Thank you so much! -- 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-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.
Re: Jenkins 1.556 still unstable - HTTP Error 404
Have you tried using the LTS instead of latest? I had lots of issues when I was tracking the latest for my Jenkins installs. I don't have those issues now that I am sticking with the LTS. On Thu, Mar 27, 2014 at 10:21 AM, David Aldrich david.aldr...@emea.nec.comwrote: Hi Sorry for my many recent posts but I am finding it difficult to achieve a stable configuration of Jenkins. I have just upgraded from 1.552 to 1.556 and now see this error when I login: *HTTP ERROR 404* Problem accessing /jenkins/;jsessionid=1ktrqn7avifn613oup7g5x0q2v. Reason: Not Found The problem remains if I revert to 1.552. Any suggestions please? Best regards David -- 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.
Unwanted symlink behaviour with Java 1.6 and git-client-plugin 1.6.5+
Hi all, We discovered a subtle bug yesterday with the Git Client plugin and its use of jgit (even if you're using the default command-line git implementation). I just noticed that this bug was probably fixed today by a pull request, but it's worth letting Jenkins users know about this. If Jenkins clones a git repo on a machine running Java 1.6, the repo will be created with core.symlinks = false in the .git/config file. This causes Bad Things to happen if your git repo happens to rely on the use of symlinks. This happens because the Git Client plugin no longer uses git clone to clone a repo, but rather a combination of git init then git fetch, and because the git init behaviour is implemented by jgit, even if you're using the default git CLI implementation. As of jgit 3.3.0, if you're running on a JVM which does not support symlinks (Java 1.6 or older), then the library will explicitly set core.symlinks to false when creating the .git directory. This means git init will create a repo which claims *not* to support symlinks, even if your file system *does* support symlinks. git fetch will then be executed (via the git binary, rather than jgit) and will respect the erroneous core.symlinks config value. Therefore you end up with files rather than the symlinks you expected in your cloned repo. (We actually saw this on an OS X 10.9 server with Jenkins running under Java 1.7 (with Java 1.6 also on the server as the non-default Java install), but jgit — for some reason — seems to think it's running on Java 1.6 and so believes symlinks aren't supported). Partly this seems to be a Git Client problem, but also (arguably) a jgit problem, as they explicitly configure new repos to reject symlinks, under the assumption that the repo will always be manipulated via jgit. But at least this merge from today would appear to fix the Git Client plugin by removing the use of jgit for git init for the CLI implementation: https://github.com/jenkinsci/git-client-plugin/commit/f5b27a9 So, If you see any weird problems with git repos and symlinks, you know why! :) Regards, 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.
Guidance on templating
Hi - trying to create a build template that contains SVN path and other common maven, shell and groovy bits that can be used by other jobs. Ideally, the template would have a variable for SVN path and the jobs calling it would have that variable defined. If I use the template plugin, I am told my template job is not buildable. If I use use scm from other project the SVN path gets populated but the other parts are not recognized. What alternatives do I have? -- 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: PermGen failures
Hi David That’s an awful lot of perm space… my main production instance runs with a 4GB heap and 128m of perm space (the default for the JVM is something like 64m, from memory). You should enable GC logging for the JVM so you can see how much perm space is actually being used and adjust it down accordingly ☺ Rob From: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich Sent: Friday, 28 March 2014 2:55 AM To: jenkinsci-users@googlegroups.com Subject: RE: PermGen failures Hi Rob Thanks. I have now modified /etc/sysconfig/jenkins to specify: JENKINS_JAVA_OPTIONS=-Djava.awt.headless=true -Xmx2048m -Xms256m -XX:MaxPermSize=1024M I’ll see how that goes. David From: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of JOHNSTON, Rob Sent: 27 March 2014 00:27 To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com Subject: RE: PermGen failures Hi David If it’s Jenkins itself running out of Perm space then yes, you’ll need to increase its MaxPermSize JVM setting. If it’s a particular build or group of build that throws the error (so the error occurs but Jenkins continues to function), you need to figure out how to increase the Perm space for the java process that is crashing. From: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of David Aldrich Sent: Wednesday, 26 March 2014 8:55 PM To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com Subject: RE: PermGen failures Hi Thanks for your reply. This is not a Maven build. I start Jenkins from the command line as follows: $ sudo /etc/init.d/jenkins start Does that mean that I should modify /etc/sysconfig/Jenkins ? Best regards David From: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Maciej Jaros Sent: 26 March 2014 10:48 To: jenkinsci-users@googlegroups.commailto:jenkinsci-users@googlegroups.com Subject: Re: PermGen failures David Aldrich (2014-03-25 17:12): Hi In the last few weeks I have been getting a lot of PermGen errors: FATAL: PermGen space I am running Jenkins 1.556 on Centos 5. How should I fix this problem please? If this is a compilation issue: In Build options - Advance - MAVEN_OPTS use something like: -Xmx1536m -XX:MaxPermSize=512m If this is not a maven project then add build options to your command line. Cheers, Nux. Click herehttps://www.mailcontrol.com/sr/ANxdFpL3NvTGX2PQPOmvUsaHTTHE2WHL8V5oRJekT3F1GiJuPjpGCz0ZERt4!slM2U9s6bVQO2bCP4z!bwErJQ== to report this email as spam. -- 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. 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. For more options, visit https://groups.google.com/d/optout. This e-mail is sent by Suncorp Group Limited ABN 66 145 290 124 or one of its related entities Suncorp. Suncorp may be contacted at Level 18, 36 Wickham Terrace, Brisbane or on 13 11 55 or at suncorp.com.au. The content of this e-mail is the view of the sender or stated author and does not necessarily reflect the view of Suncorp. The content, including attachments, is a confidential communication between Suncorp and the intended recipient. If you are not the intended recipient, any use, interference with, disclosure or copying of this e-mail, including attachments, is unauthorised and expressly prohibited. If you have received this e-mail in error please contact the sender immediately and delete the e-mail and any attachments from your system. -- 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. 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. For more options, visit https://groups.google.com/d/optout. This e-mail is sent by Suncorp Group Limited ABN 66 145 290
Jenkins silently skipping MultiJob phase.
Hello, We trigger a parallel batch of roughly 30 parametrized MultiJobs. The triggering job and each of the phases of the MultiJob can run on one of 2 slave nodes. This is specified via the Restrict where this job can run option. About 1 in 15 times a phase (mostly the first one) of the MultiJob is silently skipped. Jenkins simply states Not Built next to the job phase, that's it - the next phase proceeds even though according to the job setup it should only execute if the previous phase was successful. I find this unsettling. Has anyone experienced similar issues? If so, how can they be resolved. Thanks, Regards, /David -- 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.
