[JIRA] [mercurial-plugin] (JENKINS-27827) Mercurial + Multiple SCMs changelog no longer displayed
Title: Message Title Jesse Glick commented on JENKINS-27827 Re: Mercurial + Multiple SCMs changelog no longer displayed I have no current plans to work on it unless a CloudBees customer reports it. Pull requests with expanded test coverage will be reviewed as soon as I am able. 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] [dynamic-search-view-plugin] (JENKINS-30663) [Dynamic Search View] - NPEs may happen before the full configuration
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-30663 [Dynamic Search View] - NPEs may happen before the full configuration Issue Type: Bug Assignee: Oleg Nenashev Components: dynamic-search-view-plugin Created: 27/Sep/15 12:30 PM Priority: Minor Reporter: Oleg Nenashev If a view gets created without calling View.submit(), it may contain null defaultIncludeRegex and defaultJobFilters, which may cause NPEs in further logic. Add Comment
[JIRA] [analysis-collector-plugin] (JENKINS-30390) workflow ExceptionInInitializerError
Title: Message Title Antonio Muñiz commented on JENKINS-30390 Re: workflow ExceptionInInitializerError Acceptance test added: https://github.com/jenkinsci/acceptance-test-harness/pull/40 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] [_test] (JENKINS-30664) Jenkins is using proxy which is not set to connect to a website/internet
Title: Message Title Bharath Kashyap created an issue Jenkins / JENKINS-30664 Jenkins is using proxy which is not set to connect to a website/internet Issue Type: Bug Assignee: Oleg Nenashev Components: _test Created: 27/Sep/15 1:14 PM Environment: Windows 8.1 Chrome Priority: Critical Reporter: Bharath Kashyap In order to connect the internet, from my office network; I had set proxy address and port inside Manage Jenkins -> Manage Plugins -> Advanced -> Proxy settings. It used to build fine there. At my home network on the same laptop, I have to remove these Advanced proxy configurations for me to connect internet. Even though I do ths, and restart tomcat and jenkins; whenever I build the project; it's trying to use the same old proxy server !!! And fails. I then rechecked, Advanced Tab, the proxy is not configured. But I don't see why it is trying to use the proxy settings here [Jenkins Log] proxying through http://192.168.5.1:3128 Any idea where I am failing here ???
[JIRA] [workflow-plugin] (JENKINS-27057) CME in WorkflowRun.logsToCopy
Title: Message Title Jesse Glick commented on JENKINS-27057 Re: CME in WorkflowRun.logsToCopy Observed to fail more consistently when applying a fix for JENKINS-30055. 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] [workflow-plugin] (JENKINS-27057) CME in WorkflowRun.logsToCopy
Title: Message Title Jesse Glick started work on JENKINS-27057 Change By: Jesse Glick Status: Open In Progress 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] [dynamic-search-view-plugin] (JENKINS-30663) [Dynamic Search View] - NPEs may happen before the full configuration get submitted
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-30663 [Dynamic Search View] - NPEs may happen before the full configuration get submitted Change By: Oleg Nenashev Summary: [Dynamic Search View] - NPEs may happen before the full configuration get submitted 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] [libvirt-slave-plugin] (JENKINS-23205) NPE Causes Jenkins Job to Fail
Title: Message Title G. Kr. closed an issue as Fixed Jenkins / JENKINS-23205 NPE Causes Jenkins Job to Fail Change By: G. Kr. Status: Resolved Closed 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] [libvirt-slave-plugin] (JENKINS-23205) NPE Causes Jenkins Job to Fail
Title: Message Title G. Kr. resolved as Fixed should be fixed by above commit Jenkins / JENKINS-23205 NPE Causes Jenkins Job to Fail Change By: G. Kr. Status: Open Resolved Resolution: Fixed 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] [dimensionsscm-plugin] (JENKINS-29777) Unable to configure Dimensions in Jenkins
Title: Message Title David Conneely closed an issue as Not A Defect I believe this issue to be caused by an incomplete installation as explained in previous comments. Please re-open or re-submit the issue if you that is not sufficient to resolve it. Jenkins / JENKINS-29777 Unable to configure Dimensions in Jenkins Change By: David Conneely Status: Open Closed Resolution: Not A Defect 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-30665) JDK 7 (or above) compiled classes cannot be used with Jenkins 1.601 and above
Title: Message Title Tobias Olsson updated an issue Jenkins / JENKINS-30665 JDK 7 (or above) compiled classes cannot be used with Jenkins 1.601 and above Change By: Tobias Olsson I'm one of the developers for the Lucene plugin. As Lucene libraries are compiled using java 7 (since java 6 is deprecated) this bug causes all releases above 1.600 to be broken for us.Some history: in JDK 7 a new "feature" introduced was that the compiler has to keep a stack map. Any code compiled for java 1.6 is run in a compatibility mode, but all code compiled with target 1.7 needs to have this. More can be read here: [http://chrononsystems.com/blog/java-7-design-flaw-leads-to-huge-backward-step-for-the-jvm]What happens is that for some reason, that stack map becomes either corrupt or removed after applying commit [https://github.com/jenkinsci/jenkins/commit/89681c20296c5f1c134039d2e24d434e1992437b ] causing java.lang.VerifyErrors (attached full stack, but excerpt below). - I do not understand how any of that code can cause a problem, yet it does.- Just to be clear. This has NOTHING to do with compiling jenkins with java 7. I have not tried that. I'm only interested in how the official builds interact with plugins requiring java 7 (it's because our required dependencies are only compiled for java 7).Reproduce:I have bisected by1) Added the lucene search plugin through normal plugin download2) Added a job3) Ran it4) Search for "user" or something else that is in the build log. Either I see the stack(bad) or the found jobs(good). I actually bisected the patch with the script "test.sh" attached, but it's clearly visible in both console and browser.This has been reproduced on other hosts and other jdk's as well.Caused by: java.lang.VerifyError: Expecting a stackmap frame at branch target 25Exception Details: Location:org/apache/lucene/util/packed/PackedInts$Format.longCount(III)I @3: ifne Reason:Expected stackmap frame at this location. Bytecode:000: b200 5e9a 0016 1d9b 0009 1d10 40a4 000c010: bb00 6059 1db7 0063 bf2a 1b1c 1db6 006e020: 3704 b200 5e9a 0014 1604 1400 6f94 9b00030: 0bbb 0060 59b7 0071 bf16 0414 0064 7109040: 949a 000b 1604 1400 646d 88ac 1604 1400050: 646d 0a61 88ac Add Comment
[JIRA] [core] (JENKINS-30665) JDK 7 (or above) compiled classes cannot be used with Jenkins 1.601 and above
Title: Message Title Tobias Olsson commented on JENKINS-30665 Re: JDK 7 (or above) compiled classes cannot be used with Jenkins 1.601 and above The problem is the @AdaptField which seems to be broken. Removing that annotation makes everything work as it should. 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-30665) JDK 7 (or above) compiled classes cannot be used with Jenkins 1.601 and above
Title: Message Title Tobias Olsson updated an issue Jenkins / JENKINS-30665 JDK 7 (or above) compiled classes cannot be used with Jenkins 1.601 and above Change By: Tobias Olsson I'm one of the developers for the Lucene plugin. As Lucene libraries are compiled using java 7 (since java 6 is deprecated) this bug causes all releases above 1.600 to be broken for us.Some history: in JDK 7 a new "feature" introduced was that the compiler has to keep a stack map. Any code compiled for java 1.6 is run in a compatibility mode, but all code compiled with target 1.7 needs to have this. More can be read here: [http://chrononsystems.com/blog/java-7-design-flaw-leads-to-huge-backward-step-for-the-jvm]What happens is that for some reason, that stack map becomes either corrupt or removed after applying commit [https://github.com/jenkinsci/jenkins/commit/89681c20296c5f1c134039d2e24d434e1992437b ] causing java.lang.VerifyErrors (attached full stack, but excerpt below). - I do not understand how any of that code can cause a problem, yet it does. - Just to be clear. This has NOTHING to do with compiling jenkins with java 7. I have not tried that. I'm only interested in how the official builds interact with plugins requiring java 7 (it's because our required dependencies are only compiled for java 7).Reproduce:I have bisected by1) Added the lucene search plugin through normal plugin download2) Added a job3) Ran it4) Search for "user" or something else that is in the build log. Either I see the stack(bad) or the found jobs(good). I actually bisected the patch with the script "test.sh" attached, but it's clearly visible in both console and browser.This has been reproduced on other hosts and other jdk's as well.Caused by: java.lang.VerifyError: Expecting a stackmap frame at branch target 25Exception Details: Location:org/apache/lucene/util/packed/PackedInts$Format.longCount(III)I @3: ifne Reason:Expected stackmap frame at this location. Bytecode:000: b200 5e9a 0016 1d9b 0009 1d10 40a4 000c010: bb00 6059 1db7 0063 bf2a 1b1c 1db6 006e020: 3704 b200 5e9a 0014 1604 1400 6f94 9b00030: 0bbb 0060 59b7 0071 bf16 0414 0064 7109040: 949a 000b 1604 1400 646d 88ac 1604 1400050: 646d 0a61 88ac Add Comment
[JIRA] [libvirt-slave-plugin] (JENKINS-17647) Add LXC support
Title: Message Title G. Kr. closed an issue as Fixed Jenkins / JENKINS-17647 Add LXC support Change By: G. Kr. Status: Resolved Closed 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] [libvirt-slave-plugin] (JENKINS-17647) Add LXC support
Title: Message Title G. Kr. resolved as Fixed Jenkins / JENKINS-17647 Add LXC support Change By: G. Kr. Status: Open Resolved Resolution: Fixed 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] [libvirt-slave-plugin] (JENKINS-17647) Add LXC support
Title: Message Title G. Kr. commented on JENKINS-17647 Re: Add LXC support fixed a long time ago in https://github.com/jenkinsci/libvirt-slave-plugin/commit/69b19c4d056c07a16825b3dff8c52854b7340ba4 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-30665) JDK 7 (or above) compiled classes cannot be used with Jenkins 1.601 and above
Title: Message Title Tobias Olsson created an issue Jenkins / JENKINS-30665 JDK 7 (or above) compiled classes cannot be used with Jenkins 1.601 and above Issue Type: Bug Assignee: Unassigned Attachments: java.lang.VerifyError.stack.txt, test.sh Components: core Created: 27/Sep/15 8:00 PM Environment: Operating System: Linux 64bit Ubuntu Java: java version "1.8.0_11" Java(TM) SE Runtime Environment (build 1.8.0_11-b12) Java HotSpot(TM) 64-Bit Server VM (build 25.11-b03, mixed mode) Self-compiled (with java 6) and releases all work the same. All are run with hpi:run or java -jar war/target/jenkins.jar Labels: java7 Priority: Major Reporter: Tobias Olsson I'm one of the developers
[JIRA] [ec2-plugin] (JENKINS-26493) Use new EC2 API endpoint hostnames
Title: Message Title arkaitzj commented on JENKINS-26493 Re: Use new EC2 API endpoint hostnames Hi This is a problem for me as well, I don't know how the rest of the people are working with the current plugin. According to the code and this EC2 documentation the API endpoints that the plugin constructs will never work. This is just a simple URL constructing function that needs to be changed, there is even a pull request in github to get it fixed. Could we get that merged or the problem fixed please? 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] [dynamic-search-view-plugin] (JENKINS-27613) dynamic search view could not be restarted.
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-27613 dynamic search view could not be restarted. Change By: SCM/JIRA link daemon Status: In Progress Resolved Resolution: Fixed 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] [dynamic-search-view-plugin] (JENKINS-30663) [Dynamic Search View] - NPEs may happen before the full configuration
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30663 Re: [Dynamic Search View] - NPEs may happen before the full configuration Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkinsci/plugins/dynamic_search/views/SimpleSearchView.java src/test/java/org/jenkinsci/plugins/dynamicsearchview/SimpleSearchViewTest.java http://jenkins-ci.org/commit/dynamic-search-view-plugin/4f1ec1ebaae053efabe5280b1d68ffde431ea2b9 Log: [FIXED JENKINS-30663] - Properly handle nullable default options in SimpleSearchView 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] [dynamic-search-view-plugin] (JENKINS-30663) [Dynamic Search View] - NPEs may happen before the full configuration
Title: Message Title SCM/JIRA link daemon resolved as Fixed Jenkins / JENKINS-30663 [Dynamic Search View] - NPEs may happen before the full configuration Change By: SCM/JIRA link daemon Status: Open Resolved Resolution: Fixed 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] [dynamic-search-view-plugin] (JENKINS-30662) [Dynamic Search View] requests cache implementation is not thread-safe
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30662 Re: [Dynamic Search View] requests cache implementation is not thread-safe Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkinsci/plugins/dynamic_search/views/UserContextCache.java http://jenkins-ci.org/commit/dynamic-search-view-plugin/850219b6ed0a3cd07b47c31cd92521d1fae5b074 Log: JENKINS-30662 - Thread safety in UserContext 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] [dynamic-search-view-plugin] (JENKINS-27613) dynamic search view could not be restarted.
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27613 Re: dynamic search view could not be restarted. Code changed in jenkins User: Oleg Nenashev Path: src/main/resources/com/synopsys/arc/jenkinsci/plugins/dynamic_search/views/SimpleSearchView/itemsTable.groovy src/main/resources/com/synopsys/arc/jenkinsci/plugins/dynamic_search/views/SimpleSearchView/main.jelly http://jenkins-ci.org/commit/dynamic-search-view-plugin/f8ba05b30f9a85e67ab2970957ae0f1e8aacc681 Log: [FIXED JENKINS-27613] - NPE in the layout due to the changes in View.main.jelly implementation in the core 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] [dynamic-search-view-plugin] (JENKINS-30662) [Dynamic Search View] requests cache implementation is not thread-safe
Title: Message Title SCM/JIRA link daemon commented on JENKINS-30662 Re: [Dynamic Search View] requests cache implementation is not thread-safe Code changed in jenkins User: Oleg Nenashev Path: src/main/java/com/synopsys/arc/jenkinsci/plugins/dynamic_search/views/SimpleSearchView.java http://jenkins-ci.org/commit/dynamic-search-view-plugin/77c23700efc4e3f55954ca979ca2c0466b601558 Log: JENKINS-30662 - Proper initialization of UserContextCache on jenkins startup 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] [libvirt-slave-plugin] (JENKINS-19531) Slave should be shut down only if idle
Title: Message Title G. Kr. closed an issue as Fixed Jenkins / JENKINS-19531 Slave should be shut down only if idle Change By: G. Kr. Status: Resolved Closed 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] [libvirt-slave-plugin] (JENKINS-19531) Slave should be shut down only if idle
Title: Message Title G. Kr. resolved as Fixed already solved https://github.com/jenkinsci/libvirt-slave-plugin/pull/7#event-92245324 Jenkins / JENKINS-19531 Slave should be shut down only if idle Change By: G. Kr. Status: Open Resolved Resolution: Fixed 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] [clearcase-plugin] (JENKINS-30666) Change maintainer
Title: Message Title Lars Kruse created an issue Jenkins / JENKINS-30666 Change maintainer Issue Type: Bug Assignee: Lars Kruse Components: clearcase-plugin Created: 27/Sep/15 8:30 PM Priority: Minor Reporter: Lars Kruse Vincent is looking for a new maintainer for this plugin. We will transfer maintenance to [Praqma|www.praqma.com] and support it under the Joint Open Source Roadmap Alliance [Josra|www.josra.org]. Josra is also maintaining the ClearCase UCM plugin . Add Comment
[JIRA] [log-parser-plugin] (JENKINS-27208) Make Log Parser Plugin compatible with Workflow
Title: Message Title Manuel Jesús Recena Soto edited a comment on JENKINS-27208 Re: Make Log Parser Plugin compatible with Workflow A [PR|https://github.com/jenkinsci/log-parser-plugin/pull/ 9 10 ] has been sent. 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] [multiple-scms-plugin] (JENKINS-30667) poll scm always run even there is no changes with multiple scm plugin configured two branches in the same repo
Title: Message Title huaqiang li created an issue Jenkins / JENKINS-30667 poll scm always run even there is no changes with multiple scm plugin configured two branches in the same repo Issue Type: Bug Assignee: Kevin Bell Components: multiple-scms-plugin, pollscm-plugin Created: 28/Sep/15 1:30 AM Priority: Major Reporter: huaqiang li i use multiple scm plugin to configure two git scms with the same git project , but two different branches. and i use the poll scm plugin as trigger . the poll always thinks there is new change even if there is no new changes. the poll log: Git Polling Log : Started on Sep 28, 2015 1:32:00 AM Polling SCM changes on master Using strategy: Default [poll] Last Built Revision: Revision c3b9bbfc4dfc3884fdd3e523e527c03ad97a5e04 (refs/remotes/origin/master) using GIT_SSH to set credentials ui gitlab deploy key > git --version # timeout=10 > git -c core.askpass=true ls-remote -h g...@git.dev.fwmrm.net:af/engine.git # timeout=10 [poll] Latest remote head revision on origin/master is: c3b9bbfc4dfc3884fdd3e523e527c03ad97a5e04 - already built by 21 Using strategy: Default [poll] Last Built Revision: Revision c3b9bbfc4dfc3884fdd3e523e527c03ad97a5e04 (refs/remotes/origin/master) using GIT_SSH to set credentials ui gitlab deploy key > git --version # timeout=10 > git -c core.askpass=true ls-remote -h g...@git.dev.fwmrm.net:af/engine.git # timeout=10 [poll] Latest remote head revision on origin/6.3 is: 1993a6ce1f7192ba0b48b81c0948b1039a169f70 Done. Took 1 sec Changes found
[JIRA] [core] (JENKINS-20967) Cloud provisioning called when Jenkins is quieting Down
Title: Message Title Kanstantsin Shautsou commented on JENKINS-20967 Re: Cloud provisioning called when Jenkins is quieting Down Highlight. 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] [docker-plugin] (JENKINS-30668) docker cloud doesn't pull the image before start the docker container
Title: Message Title huaqiang li created an issue Jenkins / JENKINS-30668 docker cloud doesn't pull the image before start the docker container Issue Type: Bug Assignee: Kanstantsin Shautsou Components: docker-plugin Created: 28/Sep/15 1:43 AM Priority: Major Reporter: huaqiang li in the Cloud i added a docker host , and add a Docker template with the docker image ID with my private registry:label , the docker plugin failed to start the docker container on docker host . so i have to pull the docker image manually on docker host , and then the docker cloud works to start the docker container as docker slave . the docker cloud should pull the docker image before start docker container on docker host . Add Comment
[JIRA] [ivy-plugin] (JENKINS-29670) Support Ivy 2.4.0
Title: Message Title Kevin Formsma closed an issue as Fixed Jenkins / JENKINS-29670 Support Ivy 2.4.0 Change By: Kevin Formsma Status: Resolved Closed 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] [ivy-plugin] (JENKINS-29670) Support Ivy 2.4.0
Title: Message Title Kevin Formsma resolved as Fixed Added support for Ivy 2.4.0 in Ivy Plugin 1.25 Jenkins / JENKINS-29670 Support Ivy 2.4.0 Change By: Kevin Formsma Status: Open Resolved Resolution: Fixed 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] [android-lint-plugin] (JENKINS-30661) Install without Maven plugin fails to install
Title: Message Title René de Groot updated an issue Jenkins / JENKINS-30661 Install without Maven plugin fails to install Change By: René de Groot The marked as optional dependency seems to be a required dependency. Install fails without the Maven plugin installed but succeeds after installation. From the updateCenter/ page: Android Lint Plugin Failure -java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1322) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1121) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104) at java.lang.Thread.run(Thread.java:745)Caused by: java.io.IOException: Failed to install android-lint plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:473) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1318) ... 5 moreCaused by: java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:439) at hudson.PluginManager.dynamicLoad(PluginManager.java:464) ... 6 moreCaused by: java.lang.NoClassDefFoundError: hudson/maven/AggregatableAction at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:760) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:796) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at jenkins.ClassLoaderReflectionToolkit.invoke(ClassLoaderReflectionToolkit.java:44) at jenkins.ClassLoaderReflectionToolkit._findClass(ClassLoaderReflectionToolkit.java:86) at hudson.ClassicPluginStrategy$DependencyClassLoader.findClass(ClassicPluginStrategy.java:674) at java.lang.ClassLoader.loadClass(ClassLoader.java:424) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at jenkins.util.AntClassLoader.findBaseClass(AntClassLoader.java:1397) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1074) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:760) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:796) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078) at java.lang.ClassLoader.loadClass(ClassLoader.java:357) at
[JIRA] [android-lint-plugin] (JENKINS-30661) Install without Maven plugin fails to install
Title: Message Title René de Groot created an issue Jenkins / JENKINS-30661 Install without Maven plugin fails to install Issue Type: Bug Assignee: Christopher Orr Components: android-lint-plugin Created: 27/Sep/15 7:30 AM Environment: Jenkins ver. 1.609.1 installed on Fedora repo rpm Priority: Minor Reporter: René de Groot The marked as optional dependency seems to be a required dependency. Install fails without the Maven plugin installed but succeeds after installation. Android Lint Plugin Failure - java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1322) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1121) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:104) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Failed to install android-lint plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:473) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1318) ... 5 more Caused by: java.io.IOException: Failed to initialize at hudson.ClassicPluginStrategy.load(ClassicPluginStrategy.java:439) at
[JIRA] [build-pipeline-plugin] (JENKINS-25427) Build Pipleline Plugin no longer allows starting build with parameters
Title: Message Title jorge middleton commented on JENKINS-25427 Re: Build Pipleline Plugin no longer allows starting build with parameters There is a _javascript_ issue with msie with the current version of fancybox. To fix it, you can use https://github.com/prdolmos/fancybox-1.3.4-patched-for-jquery-1.9 isIE6 = $.browser.msie && $.browser.version < 7 && !window.XMLHttpRequest Jorge 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] [dynamic-search-view-plugin] (JENKINS-27613) dynamic search view could not be restarted.
Title: Message Title Oleg Nenashev commented on JENKINS-27613 Re: dynamic search view could not be restarted. This regression appears in new Jenkins cores, which changed the parameters being taken by ListView's main.jelly. In order to avoid such issues in the future, I'm going to keep the snapshot of this page within the plugin. 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] [dynamic-search-view-plugin] (JENKINS-30662) [Dynamic Search View] requests cache implementation is not thread-safe
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-30662 [Dynamic Search View] requests cache implementation is not thread-safe Issue Type: Bug Assignee: Oleg Nenashev Components: dynamic-search-view-plugin Created: 27/Sep/15 11:31 AM Priority: Minor Reporter: Oleg Nenashev The implementation may fail on parallel requests to the View. There is also a potential NPE risk during the initialization of the cache Add Comment This
