[JIRA] [lockable-resources-plugin] (JENKINS-29529) Master job uses one of the resources
Title: Message Title Nickolay Martinov reopened an issue Please close the issue after code is fixed. Jenkins / JENKINS-29529 Master job uses one of the resources Change By: Nickolay Martinov Resolution: Postponed Status: Resolved Reopened Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-29585) Allow selecting resources from axis values of matrix projects
Title: Message Title Nickolay Martinov commented on JENKINS-29585 Re: Allow selecting resources from axis values of matrix projects Please see the following pull request that allows implementing both scenario https://github.com/jenkinsci/lockable-resources-plugin/pull/12 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-29585) Allow selecting resources from axis values of matrix projects
Title: Message Title Nickolay Martinov updated an issue Jenkins / JENKINS-29585 Allow selecting resources from axis values of matrix projects If I correctly understand C structs in this plugin, the easiest way is to add groovy in LockableResource.isValidLabel(). Both scenario seems to be implementable if matrix build configuration is added in _expression_ context before evaluation. Change By: Nickolay Martinov Attachment: [Untitled]001.jpg Attachment: [Untitled]002.jpg Attachment: [Untitled]003.jpg Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To
[JIRA] [lockable-resources-plugin] (JENKINS-29553) Remove queue sorter
Title: Message Title Nickolay Martinov edited a comment on JENKINS-29553 Re: Remove queue sorter -Pleaseseethefollowingpullrequestthatdoesthethingformehttps://github.com/jenkinsci/lockable-resources-plugin/pull/10- Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-29553) Remove queue sorter
Title: Message Title Nickolay Martinov edited a comment on JENKINS-29553 Re: Remove queue sorter -Pleaseseethefollowingpullrequestthatdoesthethingforme - https://github.com/jenkinsci/lockable-resources-plugin/pull/10 - Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-29553) Remove queue sorter
Title: Message Title Nickolay Martinov commented on JENKINS-29553 Re: Remove queue sorter Please instead see pull request https://github.com/jenkinsci/lockable-resources-plugin/pull/11 It's done against master and doesnt include changes for other issues Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-29553) Remove queue sorter
Title: Message Title Nickolay Martinov edited a comment on JENKINS-29553 Re: Remove queue sorter - Pleaseseethefollowingpullrequestthatdoesthethingformehttps://github.com/jenkinsci/lockable-resources-plugin/pull/10 - Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-29553) Remove queue sorter
Title: Message Title Nickolay Martinov commented on JENKINS-29553 Re: Remove queue sorter Please see the following pull request that does the thing for me https://github.com/jenkinsci/lockable-resources-plugin/pull/10 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-29585) Allow selecting resources from axis values of matrix projects
Title: Message Title Nickolay Martinov updated an issue Jenkins / JENKINS-29585 Allow selecting resources from axis values of matrix projects Change By: Nickolay Martinov Herearetwoscenariosthatarecurrentlyimpossibletoimplementproperly.Scenario1:Thereare4DBservers.TwoserversrunRDBMSversion1andtwoserversrunRDBMSversion2.ThereisaproductthatmustworkwithbothversionsofRDBMS.Thereisamatrixjobthathasaxisdbwithvalues1and2.-Itshouldbepossibleforthebuildwithconfigurationdb=1tolockoneofRDBMSwithversion1andforthebuildwithconfigurationdb=2tolockoneofRDBMSwithversion2.Scenario 2 :ThereisapoolofDBservers.Theseserversrequiresomeperiodicmaintenance(DBrestart,healthcheck,cleanup,whatever).ThereisacleanupmatrixjobwithElasticAxisaxisiteratingoveralabelwhoseallDBservershave(ElasticAxisnode=db).-Itshouldbepossibletolockeachbuildaccordingtoitsconfigurationthatisvalueoflabelnode.Theeasiestwayseemstobetothreatlabelparameterofjobconfigurationforlockable-resources-pluginasagroovy_expression_.Thisgroovy_expression_canaccessbuildconfiguration,axisvalues,etcandproducetheresourcelabeltobeactuallyusedtosearchforresources. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-29585) Allow selecting resources from axis values of matrix projects
Title: Message Title Nickolay Martinov created an issue Jenkins / JENKINS-29585 Allow selecting resources from axis values of matrix projects Issue Type: Improvement Assignee: Unassigned Components: lockable-resources-plugin Created: 23/Jul/15 8:35 AM Environment: 1.6 Priority: Major Reporter: Nickolay Martinov Here are two scenarios that are currently impossible to implement properly. Scenario 1: There are 4 DB servers. Two servers run RDBMS version 1 and two servers run RDBMS version 2. There is a product that must work with both versions of RDBMS. There is a matrix job that has axis db with values 1 and 2. It should be possible for the build with configuration db=1 to lock one of RDBMS with version 1 and for the build with configuration db=2 to lock one of RDBMS with version 2. Scenario: There is a pool of DB servers. These servers require some periodic maintenance (DB restart, health check, cleanup, whatever). There is a cleanup matrix job with ElasticAxis axis iterating over a label whose all DB servers have
[JIRA] [lockable-resources-plugin] (JENKINS-29553) Remove queue sorter
Title: Message Title Nickolay Martinov created an issue Jenkins / JENKINS-29553 Remove queue sorter Issue Type: Improvement Assignee: Unassigned Components: lockable-resources-plugin Created: 22/Jul/15 8:07 AM Environment: 1.6 Priority: Major Reporter: Nickolay Martinov The plugin contains queue sorter. This sorter conflicts with other plugins that are more feature rich and configurable (hardcoded 1 minute delay in lockable-resources-pugin is an example why other plugins could be more preferable). An example is Priority Sorter Plugin. To avoid conflicts, the plugin should just lock the resources and leave queue sorting to other plugins. As an alternative, queue sorting could be extracted into a separate plugin. Add Comment
[JIRA] [lockable-resources-plugin] (JENKINS-29529) Master job uses one of the resources
Title: Message Title Nickolay Martinov updated an issue Jenkins / JENKINS-29529 Master job uses one of the resources Change By: Nickolay Martinov Priority: Minor Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-29529) Master job uses one of the resources
Title: Message Title Nickolay Martinov commented on JENKINS-29529 Re: Master job uses one of the resources Please see the following pull request that fixes the issue for me https://github.com/jenkinsci/lockable-resources-plugin/pull/9 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [lockable-resources-plugin] (JENKINS-29529) Master job uses one of the resources
Title: Message Title Nickolay Martinov commented on JENKINS-29529 Re: Master job uses one of the resources Not really a minor. For every matrix job you'll need an extra instance of the resource. Imagine that you have two instances of the resource and two matrix jobs with three configurations in each. Ideally you should be able to execute two configurations in parallel so two jobs can be finished in tree usages of each resource. But since parent builds of matrix jobs consume resource as well, you'll end up in a situation when two jobs start at the same time but none of configuration builds can progress because both parent builds consumed all resource instances and there is nothing left for configuration builds. The situation can be extended to any number of instances of resource given the proper number of matrix jobs. Seem to be show stopper. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-15355) AdjunctManager: exception upon startup
Nickolay Martinov commented on JENKINS-15355 AdjunctManager: exception upon startup Can see the issue in Jenkins ver. 1.505 Mar 15, 2013 7:49:36 AM org.kohsuke.stapler.jelly.AdjunctTag doTag WARNING: AdjunctManager is not installed for this application. Skipping adjunct tags java.lang.Exception at org.kohsuke.stapler.jelly.AdjunctTag.doTag(AdjunctTag.java:74) 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.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:119) 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.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:63) at org.kohsuke.stapler.jelly.DefaultScriptInvoker.invokeScript(DefaultScriptInvoker.java:53) at org.kohsuke.stapler.jelly.JellyRequestDispatcher.forward(JellyRequestDispatcher.java:55) at hudson.util.HudsonIsLoading.doDynamic(HudsonIsLoading.java:45) 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:601) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:288) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:151) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:90) at org.kohsuke.stapler.MetaClass$11.dispatch(MetaClass.java:363) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:45) at winstone.ServletConfiguration.execute(ServletConfiguration.java:248) at winstone.RequestDispatcher.forward(RequestDispatcher.java:333) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:376) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:162) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at winstone.FilterConfiguration.execute(FilterConfiguration.java:194) at winstone.RequestDispatcher.doFilter(RequestDispatcher.java:366) at winstone.RequestDispatcher.forward(RequestDispatcher.java:331) at winstone.RequestHandlerThread.processRequest(RequestHandlerThread.java:227) at winstone.RequestHandlerThread.run(RequestHandlerThread.java:150) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at
[JIRA] [core] (JENKINS-7488) CLONE -java.io.IOException: Unable to delete FOLDER_NAME - files in dir: [WEB_REFERENCE_FILE]
Nickolay Martinov commented on JENKINS-7488 CLONE -java.io.IOException: Unable to delete FOLDER_NAME - files in dir: [WEB_REFERENCE_FILE] I can see a bit different stack trace on Jenkins ver. 1.505 Mar 17, 2013 2:06:39 PM hudson.model.Run execute SEVERE: Failed to save build record java.io.IOException: Unable to delete /home/ci/mst/jobs/Infrastructure_free_space_monitoring/configurations/axis-label/ingot/builds/2013-03-17_14-06-01/build.xml at hudson.util.AtomicFileWriter.commit(AtomicFileWriter.java:112) at hudson.XmlFile.write(XmlFile.java:184) at hudson.model.Run.save(Run.java:1702) at hudson.model.Run.execute(Run.java:1623) at hudson.matrix.MatrixRun.run(MatrixRun.java:146) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Nickolay Martinov commented on JENKINS-17265 Builds disappearing from history Using SVN, standard plugin. Using only matrix and freestyle jobs. Previously both were disappearing like crazy. Recently matrix jobs seems to become more stable. Freestyle jobs still have problems. Perhaps makes to note that jobs are not standalone: both matrix and freestyle jobs trigger each other (build other builds) heavily. Installed plugins (env injector is disabled): Jenkins Mailer Plugin 1.4 External Monitor Job Type Plugin 1.1 LDAP Plugin 1.2 pam-auth 1.0 Javadoc Plugin 1.1 Token Macro Plugin This plug-in adds reusable macro expansion capability for other plug-ins to use. 1.6 Maven 2 Project Plugin 1.505 Jenkins Subversion Plug-in 1.45 Ant Plugin 1.2 Jenkins CVS Plug-in Integrates Jenkins with CVS version control system using a modified version of the Netbeans cvsclient. 2.8 Dump Info BuildWrapper Plugin The Dump Info BuildWrapper Plugin allows jobs to automatically dump some important Hudson-specific information into the job log. 1.1 Hudson platformlabeler plugin Assigns labels on nodes automatically based on the computer operating system. 1.1 Tracking SVN Plugin 1.1 Priority Sorter This plugin allows for the build queue to be sorted based on pre-assigned priorities for each job. 1.3 Jenkins Translation Assistance plugin 1.10 Static Analysis Utilities This plug-in provides utilities for the static code analysis plug-ins. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 1.49 Task Scanner Plugin This plug-in scans for open tasks in a specified set of files in the project modules and visualizes the results. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 4.35 Disk Usage Plugin This plugin counts disk usage. 0.18 SSH Slaves plugin 0.22 FindBugs Plug-in This plug-in collects the FindBugs analysis results of the project modules and visualizes the found warnings. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 4.48 Checkstyle Plug-in This plug-in collects the Checkstyle analysis results of the project modules and visualizes the found warnings. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 3.35 Git Client Plugin 1.0.3 Git Plugin This plugin integrates GIT with Jenkins. 1.2.0 View Job Filters Create smart views with exactly the jobs you want. Your smart views can automatically include or exclude jobs by using things like the SCM path or type, the job type, build statuses or trends or triggers, relevance to the logged-in user, email recipients, Maven configuration, job parameterization, and user permissions. Mix and match filters to narrow down to exactly what you want. 1.22 Warnings Plug-in This plug-in collects the compiler warnings of the project modules and visualizes the results. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 4.23 PMD Plug-in This plug-in collects the PMD analysis results of the project modules and visualizes the found warnings. If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 3.34 Copy Artifact Plugin Adds a build step to copy artifacts from another project. 1.25 Downstream build view This plug-in allows you to view the full status all the downstream builds so that we can graphically see that everything for this build has been completed successfully. 1.8 Hudson Blame Subversion Plug-in 1.200 Groovy Postbuild Groovy postbuild task. 1.8 groovyaxis This plugin is a sample to explain how to write a Jenkins plugin. 0.3 Duplicate Code Scanner Plug-in This plug-in collects the duplicate code analysis results of the project modules and visualizes the found warnings. Supported duplicate code analysis tools: • PMD's Copy Paste Detector (CPD) • Simian If you like this open source plug-in please consider supporting my work by buying my Android game Inca Trails. 2.34 Static Analysis Collector Plug-in This plug-in is an add-on for the plug-ins Checkstyle, Dry, FindBugs, PMD, Tasks, and Warnings: the plug-in collects the different analysis results and shows the results in a combined trend graph. Additionally, the plug-in provides health reporting and build stability based on these combined results. If you like this open
[JIRA] (JENKINS-17265) Builds disappearing from history
Nickolay Martinov commented on JENKINS-17265 Builds disappearing from history Jose has made interesting note. I recall that sometimes we can see build listed in UI but Copy Artifacts Plugin seems to fail to find the build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Nickolay Martinov commented on JENKINS-17265 Builds disappearing from history I confirm that script is perfect reproducer: Checking Infrastructure_update_sys... Checking Infrastructure_update_valgrind... Checking NOM_6_build... Job NOM_6_build missing builds: 887 618 Checking NOM_6_kit... Job NOM_6_kit missing builds: 204 Checking NOM_6_kit_smoke... Job NOM_6_kit_smoke missing builds: 139 Checking NOM_6_test_f... Checking NOM_6_test_f_m... Job NOM_6_test_f_m missing builds: 88 Checking NOM_6_test_l... Checking NOM_6_test_l_m... Job NOM_6_test_l_m missing builds: 204 Checking NOM_6_test_sdk... Job NOM_6_test_sdk missing builds: 85 Checking NOM_6_test_sdk_m... Checking NOM_V600_build... Checking NOM_V600_kit... Checking NOM_V600_kit_smoke... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17265) Builds disappearing from history
Nickolay Martinov commented on JENKINS-17265 Builds disappearing from history 1. Havent spotted exceptions. The only thing reporting error is Copy artifact plugin that cant find a build 2. Freestyle jobs. Before 1.505 in matrix jobs builds disappeared veeery often . Matrix jobs dont seem to disappear now or eat least not so often 3. Running using winstone embedded in jenkins 4. HP-UX 11.21 Itanium Java 7 master. HP-UX 11.31 Itanium Java 7 and RHEL 5.4/5.6/5.8 Java 7 slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Nickolay Martinov commented on JENKINS-15156 Builds disappear from build history after completion With 1.502 problem is still there but it has changed a bit. Now i can see the history for project on left side but when i select particular build and try to narrow down to particular configuration of multi-configuration project it tells that configuration was never built. From the main page of multi-configuration project when i click on configurations i cannot see the history of builds. Reloading configuration from disk is still a workaround that can be used but still this blocks chained builds that try to copy artifacts from one build to another. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Nickolay Martinov commented on JENKINS-15156 Builds disappear from build history after completion Could anyone please confirm that issue is fixed? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Nickolay Martinov commented on JENKINS-15156 Builds disappear from build history after completion Not sure this is caused by renaming as we do not rename jobs but had this problem very frequently (because of the number of jobs). Reverting back to version before 1.485 made this problem disappear. This is, imho, clear sign that lazy loading could be culprit. BTW, we don't have shelve plug-in. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15156) Builds disappear from build history after completion
Nickolay Martinov commented on JENKINS-15156 Builds disappear from build history after completion For us it's just random since we do not (and cant) rename jobs. No particular conditions were noted. Right now it's ok but with couple of builds on any jobs history starts disappearing; reload configuration from disk and builds are back. Since copy artifacts plugin affected, i believe this is not a UI problem. We extensively use matrix projects and ssh slaves with matrix tie parent plugin (dont know if this matters). Downgraded back to 1.463 and this problem disappeared. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-8754) ROADMAP: Improve Start-up Time
Nickolay Martinov commented on JENKINS-8754 ROADMAP: Improve Start-up Time Looks like this feature breaks a lot. See https://issues.jenkins-ci.org/browse/JENKINS-15156 Would be nice to have a patch that reverts the change. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Nickolay Martinov commented on JENKINS-15156 Builds Disappear from Build History after Completion Does anyone know version where this bug wasnt introduced yet? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-16175) Dashboard not showing job status
Nickolay Martinov commented on JENKINS-16175 Dashboard not showing job status This issue duplicates JENKINS-15156 Builds Disappear from Build History after Completion that was created earlier, contains much more data, votes, watches and generally gets much more attention. Please consider instead assigning to initial issue instead of to duplicate. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Nickolay Martinov commented on JENKINS-15156 Builds Disappear from Build History after Completion Rearranged links a bit as this issue was marked as duplicate of newer issue that didn't get as much attention... This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Nickolay Martinov updated JENKINS-15156 Builds Disappear from Build History after Completion Change By: Nickolay Martinov (17/Jan/13 4:39 AM) Priority: Critical Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15156) Builds Disappear from Build History after Completion
Nickolay Martinov commented on JENKINS-15156 Builds Disappear from Build History after Completion Reloading history isn't really a solution. Since CI is not for humans (why we need CI then?) but for automation. And this bug makes plugins like "Copy artifact" to fail. All this results in lots of false build failures. Since people cant really do anything about these build failures they tend to start just to ignore "crazy Jenkins". And this ruins whole concept. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X, IBM AIX slave fails
Nickolay Martinov commented on JENKINS-13614 archiving artefacts from remote MacOS X, IBM AIX slave fails Hello Natalia, could you please clarify if new version still fails with Java 6 or with Java 7? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X, IBM AIX slave fails
Nickolay Martinov commented on JENKINS-13614 archiving artefacts from remote MacOS X, IBM AIX slave fails This will throw exception for every file. Alternative approach is to check if file is a symlink before trying to resolve it. This works better and seems more logical. See attached patch. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X, IBM AIX slave fails
Nickolay Martinov commented on JENKINS-13614 archiving artefacts from remote MacOS X, IBM AIX slave fails Try attached patch. It works for HP-UX but since this is pure Java it should also help on AIX with high probability. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X, IBM AIX slave fails
Nickolay Martinov commented on JENKINS-13614 archiving artefacts from remote MacOS X, IBM AIX slave fails This is not a master/slave issue. This is an issue with artifact archiving on platforms other than Windows and Linux. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X slave fails
[
https://issues.jenkins-ci.org/browse/JENKINS-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162635#comment-162635
]
Nickolay Martinov commented on JENKINS-13614:
-
This happens for us too.
bash-4.0# uname -a
HP-UX B.11.31 U ia64 4068214626 unlimited-user license
Master in on HP-UX host. There is bunch of ssh slaves. One of these slaves is
on same host as the master. Build failed when job (free style) was building on
that slave.
There are no special files in workspace:
bash-4.0# find . -type l -o -type c -o -type b -o -type M -o -type n -o -type s
bash-4.0#
Since there are no symlinks it looks strange that it tries to resolve some
symlinks. Also strange why it cant obtain current working directory.
This issue is absolutely blocking for us as it does not allow to collect build
artifacts.
archiving artefacts from remote MacOS X slave fails
---
Key: JENKINS-13614
URL: https://issues.jenkins-ci.org/browse/JENKINS-13614
Project: Jenkins
Issue Type: Bug
Components: core
Environment: Jenkins 1.461
Master node: Debian Linux, Tomcat 7
Slave node: MacOS X 10.6
Reporter: Marcus Better
Archiving the artefacts from a slave fails with the following exception. It
looks like it didn't find a suitable POSIX implementation.
Oddly enough this just started happening seemingly without provocation. I'm
pretty sure this installation worked correctly earlier today.
{code}
ERROR: Failed to archive artifacts: build/*.zip, build/*.ipa, build/*.plist
hudson.util.IOException2: java.lang.UnsupportedOperationException
at hudson.FilePath.copyRecursiveTo(FilePath.java:1745)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:680)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:658)
at hudson.model.Build$RunnerImpl.post2(Build.java:162)
at
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:627)
at hudson.model.Run.run(Run.java:1459)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Caused by: java.util.concurrent.ExecutionException:
java.lang.UnsupportedOperationException
at hudson.remoting.Channel$3.adapt(Channel.java:679)
at hudson.remoting.Channel$3.adapt(Channel.java:674)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
at hudson.FilePath.copyRecursiveTo(FilePath.java:1743)
... 11 more
Caused by: java.lang.UnsupportedOperationException
at hudson.os.PosixAPI$1.getCurrentWorkingDirectory(PosixAPI.java:59)
at org.jruby.ext.posix.util.ExecIt.run(ExecIt.java:59)
at org.jruby.ext.posix.util.ExecIt.runAndWait(ExecIt.java:51)
at org.jruby.ext.posix.JavaLibCHelper.readlink(JavaLibCHelper.java:196)
at org.jruby.ext.posix.JavaPOSIX.readlink(JavaPOSIX.java:160)
at hudson.Util.resolveSymlink(Util.java:1067)
at hudson.Util.resolveSymlink(Util.java:1030)
at hudson.util.DirScanner$Glob.scan(DirScanner.java:107)
at hudson.FilePath.writeToTar(FilePath.java:1781)
at hudson.FilePath.access$1000(FilePath.java:166)
at hudson.FilePath$36.invoke(FilePath.java:1722)
at hudson.FilePath$36.invoke(FilePath.java:1719)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Thread.java:680)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X slave fails
[
https://issues.jenkins-ci.org/browse/JENKINS-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162636#comment-162636
]
Nickolay Martinov commented on JENKINS-13614:
-
Looks like this regressions is caused by
https://issues.jenkins-ci.org/browse/JENKINS-9118
archiving artefacts from remote MacOS X slave fails
---
Key: JENKINS-13614
URL: https://issues.jenkins-ci.org/browse/JENKINS-13614
Project: Jenkins
Issue Type: Bug
Components: core
Environment: Jenkins 1.461
Master node: Debian Linux, Tomcat 7
Slave node: MacOS X 10.6
Reporter: Marcus Better
Archiving the artefacts from a slave fails with the following exception. It
looks like it didn't find a suitable POSIX implementation.
Oddly enough this just started happening seemingly without provocation. I'm
pretty sure this installation worked correctly earlier today.
{code}
ERROR: Failed to archive artifacts: build/*.zip, build/*.ipa, build/*.plist
hudson.util.IOException2: java.lang.UnsupportedOperationException
at hudson.FilePath.copyRecursiveTo(FilePath.java:1745)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:680)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:658)
at hudson.model.Build$RunnerImpl.post2(Build.java:162)
at
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:627)
at hudson.model.Run.run(Run.java:1459)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Caused by: java.util.concurrent.ExecutionException:
java.lang.UnsupportedOperationException
at hudson.remoting.Channel$3.adapt(Channel.java:679)
at hudson.remoting.Channel$3.adapt(Channel.java:674)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
at hudson.FilePath.copyRecursiveTo(FilePath.java:1743)
... 11 more
Caused by: java.lang.UnsupportedOperationException
at hudson.os.PosixAPI$1.getCurrentWorkingDirectory(PosixAPI.java:59)
at org.jruby.ext.posix.util.ExecIt.run(ExecIt.java:59)
at org.jruby.ext.posix.util.ExecIt.runAndWait(ExecIt.java:51)
at org.jruby.ext.posix.JavaLibCHelper.readlink(JavaLibCHelper.java:196)
at org.jruby.ext.posix.JavaPOSIX.readlink(JavaPOSIX.java:160)
at hudson.Util.resolveSymlink(Util.java:1067)
at hudson.Util.resolveSymlink(Util.java:1030)
at hudson.util.DirScanner$Glob.scan(DirScanner.java:107)
at hudson.FilePath.writeToTar(FilePath.java:1781)
at hudson.FilePath.access$1000(FilePath.java:166)
at hudson.FilePath$36.invoke(FilePath.java:1722)
at hudson.FilePath$36.invoke(FilePath.java:1719)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Thread.java:680)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-9118) When workspace is cloned, symlinks are replaced with copies of the files they point to
[ https://issues.jenkins-ci.org/browse/JENKINS-9118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=162637#comment-162637 ] Nickolay Martinov commented on JENKINS-9118: This change seems to cause regression https://issues.jenkins-ci.org/browse/JENKINS-13614 When workspace is cloned, symlinks are replaced with copies of the files they point to -- Key: JENKINS-9118 URL: https://issues.jenkins-ci.org/browse/JENKINS-9118 Project: Jenkins Issue Type: Bug Components: clone-workspace Affects Versions: current Environment: Linux Reporter: owenmehegan Assignee: abayer When a project uses the clone workspace for SCM feature to grab a workspace from another project, somewhere in that process all symlinks in the original workspace are replaced with COPIES of the files they are supposed to point to. These copies are then afflicted with JENKINS-8677, where their exec permissions are wiped out. I'm pretty sure this is related to the clone workspace plugin. When I look at the workspace the files are coming FROM, everything is fine. Then the workspace they end up in, in the job that clones them, shows this symlink issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X slave fails
[
https://issues.jenkins-ci.org/browse/JENKINS-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nickolay Martinov updated JENKINS-13614:
Attachment: JENKINS-13614.patch
Patch that seems to help
archiving artefacts from remote MacOS X slave fails
---
Key: JENKINS-13614
URL: https://issues.jenkins-ci.org/browse/JENKINS-13614
Project: Jenkins
Issue Type: Bug
Components: core
Environment: Jenkins 1.461
Master node: Debian Linux, Tomcat 7
Slave node: MacOS X 10.6
Reporter: Marcus Better
Attachments: JENKINS-13614.patch
Archiving the artefacts from a slave fails with the following exception. It
looks like it didn't find a suitable POSIX implementation.
Oddly enough this just started happening seemingly without provocation. I'm
pretty sure this installation worked correctly earlier today.
{code}
ERROR: Failed to archive artifacts: build/*.zip, build/*.ipa, build/*.plist
hudson.util.IOException2: java.lang.UnsupportedOperationException
at hudson.FilePath.copyRecursiveTo(FilePath.java:1745)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:680)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:658)
at hudson.model.Build$RunnerImpl.post2(Build.java:162)
at
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:627)
at hudson.model.Run.run(Run.java:1459)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Caused by: java.util.concurrent.ExecutionException:
java.lang.UnsupportedOperationException
at hudson.remoting.Channel$3.adapt(Channel.java:679)
at hudson.remoting.Channel$3.adapt(Channel.java:674)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
at hudson.FilePath.copyRecursiveTo(FilePath.java:1743)
... 11 more
Caused by: java.lang.UnsupportedOperationException
at hudson.os.PosixAPI$1.getCurrentWorkingDirectory(PosixAPI.java:59)
at org.jruby.ext.posix.util.ExecIt.run(ExecIt.java:59)
at org.jruby.ext.posix.util.ExecIt.runAndWait(ExecIt.java:51)
at org.jruby.ext.posix.JavaLibCHelper.readlink(JavaLibCHelper.java:196)
at org.jruby.ext.posix.JavaPOSIX.readlink(JavaPOSIX.java:160)
at hudson.Util.resolveSymlink(Util.java:1067)
at hudson.Util.resolveSymlink(Util.java:1030)
at hudson.util.DirScanner$Glob.scan(DirScanner.java:107)
at hudson.FilePath.writeToTar(FilePath.java:1781)
at hudson.FilePath.access$1000(FilePath.java:166)
at hudson.FilePath$36.invoke(FilePath.java:1722)
at hudson.FilePath$36.invoke(FilePath.java:1719)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Thread.java:680)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13614) archiving artefacts from remote MacOS X slave fails
[
https://issues.jenkins-ci.org/browse/JENKINS-13614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nickolay Martinov updated JENKINS-13614:
Labels: patch regression showstopper (was: )
archiving artefacts from remote MacOS X slave fails
---
Key: JENKINS-13614
URL: https://issues.jenkins-ci.org/browse/JENKINS-13614
Project: Jenkins
Issue Type: Bug
Components: core
Environment: Jenkins 1.461
Master node: Debian Linux, Tomcat 7
Slave node: MacOS X 10.6
Reporter: Marcus Better
Labels: patch, regression, showstopper
Attachments: JENKINS-13614.patch
Archiving the artefacts from a slave fails with the following exception. It
looks like it didn't find a suitable POSIX implementation.
Oddly enough this just started happening seemingly without provocation. I'm
pretty sure this installation worked correctly earlier today.
{code}
ERROR: Failed to archive artifacts: build/*.zip, build/*.ipa, build/*.plist
hudson.util.IOException2: java.lang.UnsupportedOperationException
at hudson.FilePath.copyRecursiveTo(FilePath.java:1745)
at hudson.tasks.ArtifactArchiver.perform(ArtifactArchiver.java:116)
at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19)
at
hudson.model.AbstractBuild$AbstractRunner.perform(AbstractBuild.java:705)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:680)
at
hudson.model.AbstractBuild$AbstractRunner.performAllBuildSteps(AbstractBuild.java:658)
at hudson.model.Build$RunnerImpl.post2(Build.java:162)
at
hudson.model.AbstractBuild$AbstractRunner.post(AbstractBuild.java:627)
at hudson.model.Run.run(Run.java:1459)
at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46)
at hudson.model.ResourceController.execute(ResourceController.java:88)
at hudson.model.Executor.run(Executor.java:239)
Caused by: java.util.concurrent.ExecutionException:
java.lang.UnsupportedOperationException
at hudson.remoting.Channel$3.adapt(Channel.java:679)
at hudson.remoting.Channel$3.adapt(Channel.java:674)
at hudson.remoting.FutureAdapter.get(FutureAdapter.java:55)
at hudson.FilePath.copyRecursiveTo(FilePath.java:1743)
... 11 more
Caused by: java.lang.UnsupportedOperationException
at hudson.os.PosixAPI$1.getCurrentWorkingDirectory(PosixAPI.java:59)
at org.jruby.ext.posix.util.ExecIt.run(ExecIt.java:59)
at org.jruby.ext.posix.util.ExecIt.runAndWait(ExecIt.java:51)
at org.jruby.ext.posix.JavaLibCHelper.readlink(JavaLibCHelper.java:196)
at org.jruby.ext.posix.JavaPOSIX.readlink(JavaPOSIX.java:160)
at hudson.Util.resolveSymlink(Util.java:1067)
at hudson.Util.resolveSymlink(Util.java:1030)
at hudson.util.DirScanner$Glob.scan(DirScanner.java:107)
at hudson.FilePath.writeToTar(FilePath.java:1781)
at hudson.FilePath.access$1000(FilePath.java:166)
at hudson.FilePath$36.invoke(FilePath.java:1722)
at hudson.FilePath$36.invoke(FilePath.java:1719)
at hudson.FilePath$FileCallableWrapper.call(FilePath.java:2154)
at hudson.remoting.UserRequest.perform(UserRequest.java:118)
at hudson.remoting.UserRequest.perform(UserRequest.java:48)
at hudson.remoting.Request$2.run(Request.java:287)
at
hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at hudson.remoting.Engine$1$1.run(Engine.java:60)
at java.lang.Thread.run(Thread.java:680)
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
