[JIRA] [core] (JENKINS-26613) StackOverflowError while parsing POMs
Mayur Nagekar commented on JENKINS-26613 StackOverflowError while parsing POMs Is it fixed in 1.598 ? I am afraid I cannot downgrade to < 1.598 on my server. 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-26644) Modules marqued as (didn't run) after succesful Build
satya b commented on JENKINS-26644 Modules marqued as (didn't run) after succesful Build I too getting same problem oftenly from last few weeks. all module builds are all success but its not showing green and appears as grey. also as Bahir mentioned these builds are impact on test results also. jenkins version is 1.528 and Maven Project Plugin version is 1.528 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/d/optout.
[JIRA] [git-plugin] (JENKINS-27668) Multiple repo configuration dont have seperate local repo directory
Sagayaraj David reopened JENKINS-27668 Multiple repo configuration dont have seperate local repo directory Ok - But I wonder if GIT plugin does not support checkout of distinct repositories under single workspace, why would it have the option to add multiple repositories in the configuration? I even tried Multi-SCM plugin - which is also not differentiating the different repo code in workspace. Everything appears directly cluttering under the JOB's workspace Change By: Sagayaraj David (31/Mar/15 3:51 AM) Resolution: Not A Defect Status: Resolved Reopened 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/d/optout.
[JIRA] [git-plugin] (JENKINS-27668) Multiple repo configuration dont have seperate local repo directory
Sagayaraj David commented on JENKINS-27668 Multiple repo configuration dont have seperate local repo directory Ok - But I wonder if GIT plugin does not support checkout of distinct repositories under single workspace, why would it have the option to add multiple repositories in the configuration? I even tried Multi-SCM plugin - which is also not differentiating the different repo code in workspace. Everything appears directly cluttering under the JOB's workspace 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26797) Zombie instance created by the EC2 plugins
SCM/JIRA link daemon commented on JENKINS-26797 Zombie instance created by the EC2 plugins Code changed in jenkins User: Christoph Beckmann Path: pom.xml src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/test/java/hudson/plugins/ec2/SlaveTemplateUnitTest.java http://jenkins-ci.org/commit/ec2-plugin/6b46558c8d2797bbd17cf7523d3d321b8cabb3b0 Log: JENKINS-26797 - Zombie instance created by the EC2 plugins changed updateRemoteTags back to private introduced powermock-module-junit4 for invokeMethod 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26797) Zombie instance created by the EC2 plugins
SCM/JIRA link daemon commented on JENKINS-26797 Zombie instance created by the EC2 plugins Code changed in jenkins User: Francis Upton Path: pom.xml src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/test/java/hudson/plugins/ec2/SlaveTemplateUnitTest.java http://jenkins-ci.org/commit/ec2-plugin/0dcf0870e6e6bf1046af0f5c64f6dfe40a93baf5 Log: Merge pull request #140 from cbek/JENKINS-26797 JENKINS-26797 - Zombie instance created by the EC2 plugins Compare: https://github.com/jenkinsci/ec2-plugin/compare/2c5aa2462f72...0dcf0870e6e6 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26797) Zombie instance created by the EC2 plugins
SCM/JIRA link daemon commented on JENKINS-26797 Zombie instance created by the EC2 plugins Code changed in jenkins User: Christoph Beckmann Path: pom.xml src/main/java/hudson/plugins/ec2/SlaveTemplate.java src/test/java/hudson/plugins/ec2/SlaveTemplateUnitTest.java http://jenkins-ci.org/commit/ec2-plugin/141236b5e3739c46b7ca5b9f85b43a0c63ee7624 Log: JENKINS-26797 - Zombie instance created by the EC2 plugins fixing error code for provisionOndemand - InvalidInstanceID.NotFound refactoring updateRemoteTags - no code duplication no exception throwing if remote tagging fails - only logging otherwise we got zombie instances which are not shown adding unit testing 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26414) Add support for new C4 instance types
SCM/JIRA link daemon commented on JENKINS-26414 Add support for new C4 instance types Code changed in jenkins User: Francis Upton Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java http://jenkins-ci.org/commit/ec2-plugin/2c5aa2462f72c34082a3d2dcd2e9806b300bdd3a Log: Merge pull request #142 from cbek/JENKINS-26414 JENKINS-26414 - Add support for new C4 instance types Compare: https://github.com/jenkinsci/ec2-plugin/compare/b59267e0e262...2c5aa2462f72 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/d/optout.
[JIRA] [ec2-plugin] (JENKINS-26414) Add support for new C4 instance types
SCM/JIRA link daemon commented on JENKINS-26414 Add support for new C4 instance types Code changed in jenkins User: Christoph Beckmann Path: src/main/java/hudson/plugins/ec2/EC2Cloud.java http://jenkins-ci.org/commit/ec2-plugin/d34b4ae093fd65bd880f22e222474c961443d642 Log: JENKINS-26414 - Add support for new C4 instance types fixing AmazonServiceException: AWS was not able to validate the provided access credentials 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/d/optout.
[JIRA] [claim-plugin] (JENKINS-27675) Some way to view all unclaimed failed tests across all projects
trejkaz created JENKINS-27675 Some way to view all unclaimed failed tests across all projects Issue Type: New Feature Assignee: Christian Bremer Components: claim-plugin Created: 31/Mar/15 1:25 AM Description: I have been spending a lot of time digging down into Test Results screens, visually screening for tests which aren't claimed, going back out, repeating this for 5 sub-projects in the matrix build and then repeating that across multiple projects at the top-level, and a lot of time is being wasted. It would be great if there were a single location where I could see all failing tests across all builds that aren't currently claimed. Project: Jenkins Priority: Minor Reporter: trejkaz 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/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-27674) Build change history is no longer displayed
chikigai created JENKINS-27674 Build change history is no longer displayed Issue Type: Bug Assignee: Kevin Bell Components: multiple-scms-plugin Created: 31/Mar/15 12:18 AM Description: I have several jobs configured to checkout various GIT and SVN repositories using the Multiple SCMs plugin. I used to be able to check the change history (mainly SVN) for each completed build, but since upgrading to Jenkins 1.596.1 LTS, nothing is displayed. The issue is still present using Jenkins 1.596.2 LTS. The following error occurs for all change histories that were previously viewable: Failed to parse C:\jenkins-data\x\builds\2015-03-05_16-58-03\changelog.xml org.xml.sax.SAXException: could not close temp changelog file hudson.util.IOException2: Failed to parse C:\jenkins-data\x\builds\2015-03-05_16-58-03\changelog.xml.temp2 at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser$LogSplitter.endElement(MultiSCMChangeLogParser.java:106) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.endElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanEndElement(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source) at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.jenkinsci.plugins.multiplescms.MultiSCMChangeLogParser.parse(MultiSCMChangeLogParser.java:135) at hudson.model.AbstractBuild.calcChangeSet(AbstractBuild.java:894) at hudson.model.AbstractBuild.getChangeSet(AbstractBuild.java:862) at sun.reflect.GeneratedMethodAccessor232.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.export.MethodProperty.getValue(MethodProperty.java:66) at org.kohsuke.stapler.export.Property.writeTo(Property.java:116) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:197) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeNestedObjectTo(Model.java:192) at org.kohsuke.stapler.export.Model.writeTo(Model.java:164) at org.kohsuke.stapler.ResponseImpl.serveExposedBean(ResponseImpl.java:267) at hudson.model.Api.doJson(Api.java:211) at sun.reflect.GeneratedMethodAccessor218.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:298) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:161) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:96) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:121) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:211) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:5
[JIRA] [workflow-plugin] (JENKINS-27392) API to decorate console output
Jesse Glick started work on JENKINS-27392 API to decorate console output Change By: Jesse Glick (30/Mar/15 11:43 PM) Status: Open In Progress 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/d/optout.
[JIRA] [hipchat-plugin] (JENKINS-27202) Workflow compatibility for HipChatNotifier
owenmehegan assigned JENKINS-27202 to aldaris Workflow compatibility for HipChatNotifier Change By: owenmehegan (30/Mar/15 11:38 PM) Assignee: aldaris 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27115) GIt polling queries wrong head
Mark Waite resolved JENKINS-27115 as Not A Defect GIt polling queries wrong head Help text improvement will be included in 2.3.6 and later Change By: Mark Waite (30/Mar/15 11:22 PM) Status: In Progress Resolved Resolution: Not A Defect 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/d/optout.
[JIRA] [git-client-plugin] (JENKINS-27115) GIt polling queries wrong head
Mark Waite started work on JENKINS-27115 GIt polling queries wrong head Change By: Mark Waite (30/Mar/15 11:22 PM) Status: Open In Progress 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/d/optout.
[JIRA] [core] (JENKINS-27384) Jenkins uses 100% cpu seems related to process leak
Daniel Beck commented on JENKINS-27384 Jenkins uses 100% cpu seems related to process leak Maybe install Support Core plugin and upload a support bundle. 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/d/optout.
[JIRA] [core] (JENKINS-27384) Jenkins uses 100% cpu seems related to process leak
Mark Waite commented on JENKINS-27384 Jenkins uses 100% cpu seems related to process leak I haven't ever seen this case. Are there any other details you can provide which might hint what is different about your environment compared to other environments? 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27486) Workflow step to mask console output
Jesse Glick commented on JENKINS-27486 Workflow step to mask console output Would like the Mask Passwords plugin to be able to do this via SimpleBuildWrapper; and BindingStep in the Credentials Binding plugin should also do this. 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/d/optout.
[JIRA] [http_request] (JENKINS-26014) No preemptive authentication
Janario Oliveira closed JENKINS-26014 as Fixed No preemptive authentication Change By: Janario Oliveira (30/Mar/15 11:07 PM) Status: Resolved Closed 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27486) Workflow step to mask console output
Jesse Glick started work on JENKINS-27486 Workflow step to mask console output Change By: Jesse Glick (30/Mar/15 11:08 PM) Status: Open In Progress 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/d/optout.
[JIRA] [ios-device-connector-plugin] (JENKINS-27673) IP address of the ios device
Suresh Daniel created JENKINS-27673 IP address of the ios device Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: ios-device-connector-plugin Created: 30/Mar/15 11:02 PM Description: It will be nice to get the IP address of the device if it is connected to a wifi/cellular network Project: Jenkins Priority: Minor Reporter: Suresh Daniel 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/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
James Nord commented on JENKINS-25203 support embedded content in json It needs some testing, you can download the build from https://jenkins.ci.cloudbees.com/job/plugins/job/cucumber-testresult-plugin/53/org.jenkins-ci.plugins$cucumber-testresult-plugin/artifact/org.jenkins-ci.plugins/cucumber-testresult-plugin/0.7-SNAPSHOT/cucumber-testresult-plugin-0.7-SNAPSHOT.hpi 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26128) Dynamically-scoped env step
SCM/JIRA link daemon commented on JENKINS-26128 Dynamically-scoped env step Code changed in jenkins User: Jesse Glick Path: CHANGES.md TUTORIAL.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/EnvStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/EnvStep.java basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/EnvStep/config.groovy basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/EnvStep/help-overrides.html basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/EnvStep/help.html basic-steps/src/test/java/org/jenkinsci/plugins/workflow/steps/EnvStepTest.java cps/src/main/java/org/jenkinsci/plugins/workflow/cps/EnvActionImpl.java cps/src/main/resources/org/jenkinsci/plugins/workflow/cps/CpsFlowDefinition/help-script.html step-api/src/main/java/org/jenkinsci/plugins/workflow/steps/BodyInvoker.java step-api/src/main/java/org/jenkinsci/plugins/workflow/steps/EnvironmentExpander.java step-api/src/test/java/org/jenkinsci/plugins/workflow/steps/StepConfigTester.java support/src/main/java/org/jenkinsci/plugins/workflow/support/DefaultStepContext.java http://jenkins-ci.org/commit/workflow-plugin/42805fed800b4a9865a9d1edb1e3dd7688a3f1ba Log: Merge pull request #104 from jglick/withEnv-JENKINS-26128 JENKINS-26128 withEnv Compare: https://github.com/jenkinsci/workflow-plugin/compare/205f27b05941...42805fed800b 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26128) Dynamically-scoped env step
SCM/JIRA link daemon resolved JENKINS-26128 as Fixed Dynamically-scoped env step Change By: SCM/JIRA link daemon (30/Mar/15 10:28 PM) Status: In Progress Resolved Resolution: 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26128) Dynamically-scoped env step
SCM/JIRA link daemon commented on JENKINS-26128 Dynamically-scoped env step Code changed in jenkins User: Jesse Glick Path: CHANGES.md aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/EnvStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/EnvStep.java basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/EnvStep/config.jelly basic-steps/src/test/java/org/jenkinsci/plugins/workflow/steps/EnvStepTest.java http://jenkins-ci.org/commit/workflow-plugin/cd30c066b3d21b735a6c76b6e43e555dc2930077 Log: [FIXED JENKINS-26128] Added withEnv step. 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/d/optout.
[JIRA] [credentials-binding-plugin] (JENKINS-27631) Do not even temporarily save secrets in Workflow build record
Jesse Glick started work on JENKINS-27631 Do not even temporarily save secrets in Workflow build record Change By: Jesse Glick (30/Mar/15 10:01 PM) Status: Open In Progress 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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-26760) Update pipeline if build fails
Patrik Boström resolved JENKINS-26760 as Fixed Update pipeline if build fails Rebuild feature will be released in 0.9.0 Change By: Patrik Boström (30/Mar/15 8:55 PM) Status: Open Resolved Resolution: 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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-26760) Update pipeline if build fails
Patrik Boström closed JENKINS-26760 as Fixed Update pipeline if build fails Change By: Patrik Boström (30/Mar/15 8:56 PM) Status: Resolved Closed 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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25298) Able to rerun jobs from view
Patrik Boström resolved JENKINS-25298 as Fixed Able to rerun jobs from view Will be released in 0.9.0 Change By: Patrik Boström (30/Mar/15 8:54 PM) Status: Open Resolved Resolution: 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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27667) Unable to view more than 10 pipelines
Patrik Boström resolved JENKINS-27667 as Fixed Unable to view more than 10 pipelines Change By: Patrik Boström (30/Mar/15 8:54 PM) Status: Open Resolved Resolution: 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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27667) Unable to view more than 10 pipelines
Patrik Boström commented on JENKINS-27667 Unable to view more than 10 pipelines Now it is possible to show up to 50 instances. Will be released in 0.9.0 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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27584) NullPointerException in ManualStep.getManualStepLatest
Patrik Boström commented on JENKINS-27584 NullPointerException in ManualStep.getManualStepLatest Merged to master 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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25298) Able to rerun jobs from view
Patrik Boström commented on JENKINS-25298 Able to rerun jobs from view Merged to master https://github.com/Diabol/delivery-pipeline-plugin/pull/97 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/d/optout.
[JIRA] [envinject-plugin] (JENKINS-27313) Environment variable Injection failing after upgrading from 1.90 to 1.91
Brandon Turner commented on JENKINS-27313 Environment variable Injection failing after upgrading from 1.90 to 1.91 This is possibly related to https://github.com/jenkinsci/envinject-plugin/commit/d50c5a5de5448da74144caf25044598d40de3330 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/d/optout.
[JIRA] [credentials-binding-plugin] (JENKINS-27389) credentials set via 'withCredentials' block isn't accesible from 'env'
Jesse Glick started work on JENKINS-27389 credentials set via 'withCredentials' block isn't accesible from 'env' Change By: Jesse Glick (30/Mar/15 7:58 PM) Status: Open In Progress 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-26552) @StepContextParameter EnvVars missing Computer.environment
Jesse Glick resolved JENKINS-26552 as Fixed @StepContextParameter EnvVars missing Computer.environment Change By: Jesse Glick (30/Mar/15 7:56 PM) Status: In Progress Resolved Resolution: 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/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-25203) support embedded content in json
Dominic Bishop commented on JENKINS-25203 support embedded content in json It's good to see more progress on this. Is there a TODO of what work is still outstanding? 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/d/optout.
AVAILABLE CONSULTANT HOTLIST
*Greetings from Humac Inc.,* *Dear business partner, here is the updated list of available consultants from Humac for your daily requirements.* *Kindly contact us over email / **phone for quick response**. Wishing to have a successful business future with you.* *Technology* *Visa* *Relocation* *Availability* *Contact* COGNOS BI DEVELOPER *H1B* *NC, ONLY* *Immediate* *g...@humacinc.com* * / 623-748-4392* -- Gino Senior IT Recruiter Humac Inc Phone: 623-748-4392 Email: g...@humacinc.com -- 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.
AVAILABLE CONSULTANT HOTLIST
*Greetings from Humac Inc.,* *Dear business partner, here is the updated list of available consultants from Humac for your daily requirements.* *Kindly contact us over email / **phone for quick response**. Wishing to have a successful business future with you.* *Technology* *Visa* *Relocation* *Availability* *Contact* COGNOS BI DEVELOPER *H1B* *NC, ONLY* *Immediate* *g...@humacinc.com* * / 623-748-4392* -- Gino Senior IT Recruiter Humac Inc Phone: 623-748-4392 Email: g...@humacinc.com -- 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-27642) Restart from the URL throws exception
Rahul Racha edited a comment on JENKINS-27642 Restart from the URL throws exception Thanks for the response Daniel. Please find the support bundle attached to this ticket. 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/d/optout.
[JIRA] [core] (JENKINS-27642) Restart from the URL throws exception
Rahul Racha updated JENKINS-27642 Restart from the URL throws exception Thanks for the response Daniel. Here's the support bundle attached to this comment. Change By: Rahul Racha (30/Mar/15 6:39 PM) Attachment: support.zip 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/d/optout.
[JIRA] [parameterized-trigger-plugin] (JENKINS-11280) Downstream project name is not accepting env variable/build parameters
Sung Hong commented on JENKINS-11280 Downstream project name is not accepting env variable/build parameters It would be awesome if this can be fixed. It doesn't seem to work in either 'build' or 'post build' sections. 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/d/optout.
[JIRA] [core] (JENKINS-27672) Dead executor after upgrade to 1.596.1
Matt Legrand created JENKINS-27672 Dead executor after upgrade to 1.596.1 Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Mar/15 4:40 PM Description: Several times recently we have seen slaves nodes with status = "Dead!". Per instructions I'm attaching the log output for an instance of this happening. Restarting the Dead thread works and it functions normally thereafter...thus the "minor" category I gave this bug. Here's the log information: Mar 30, 2015 8:55:20 AM SEVERE hudson.remoting.Channel$2 handle Failed to execute command Pipe.EOF(264) (channel gizmo-1) java.lang.NullPointerException at hudson.remoting.ProxyWriter$EOF.execute(ProxyWriter.java:177) at hudson.remoting.Channel$2.handle(Channel.java:461) at hudson.remoting.SynchronousCommandTransport$ReaderThread.run(SynchronousCommandTransport.java:60) Mar 30, 2015 8:55:20 AM SEVERE hudson.remoting.Channel$2 handle This command is created here Command Pipe.EOF(264) created at at hudson.remoting.Command.(Command.java:67) at hudson.remoting.Command.(Command.java:50) at hudson.remoting.ProxyWriter$EOF.(ProxyWriter.java:169) at hudson.remoting.ProxyWriter.close(ProxyWriter.java:124) at hudson.remoting.ProxyWriter.finalize(ProxyWriter.java:132) at java.lang.ref.Finalizer.invokeFinalizeMethod(Native Method) at java.lang.ref.Finalizer.runFinalizer(Finalizer.java:83) at java.lang.ref.Finalizer.access$100(Finalizer.java:14) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:160) Environment: Jenkins version = 1.542 Java version: # java -version java version "1.7.0_51" OpenJDK Runtime Environment (rhel-2.4.4.1.el6_5-x86_64 u51-b02) OpenJDK 64-Bit Server VM (build 24.45-b08, mixed mode) Master OS version: Centos 6.4 (uname -a) Linux (node) 2.6.32-358.6.2.el6.x86_64 #1 SMP Thu May 16 20:59:36 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Plugins: Matrix Authorization Strategy Plugin 1.1 Jenkins Mailer Plugin 1.8 External Monitor Job Type Plugin 1.2 LDAP Plugin 1.8 PAM Authentication plugin 1.1 Jenkins user build vars plugin 1.1 Jenkins Priority Sorter Plugin 2.6 Ant Plugin 1.2 Javadoc Plugin 1.1 AnsiColor 0.3.1 Token Macro Plugin 1.10 build-name-setter 1.3 Jenkins build timeout plugin 1.12.2 Jenkins CVS Plug-in 2.11 Hudson Extended Read Permission Plugin 1.0 built-on-column 1.1 Credentials Plugin 1.18 Jenkins description setter plugin 1.8 Maven Integration plugin 2.1 Jenkins Email Extension Plugin 2.37.1 OfflineOnFailure 1.0 SSH Credentials Plugin 1.10 Jenkins GIT client plugin 1.12.0 SCM API Plugin 0.2 Jenkins Multiple SCMs plugin 0.3 Run Condition Plugin 1.0 conditional-buildstep 1.3.3 MapDB API Plugin 1.0.1.0 Jenkins Subversion Plug-in 2.4 Jenkins Parameterized Trigger plugin 2.22 Jenkins GIT plugin 2.2.9 Green Balls 1.13 Groovy Postbuild 1.8 Hudson Groovy builder 1.14 Jenkins Job Configuration History Plugin 2.5 Jenkins jQuery plugin 1.7.2-1 Least Load plugin 1.0.3 Log Parser Plugin 1.0.8 Matrix Tie Parent plugin 1.2 Monitoring 1.49.0 Node and Label parameter plugin 1.4 Hudson Post build task 1.8 Jenkins Post-Build Script Plug-in 0.16 Python Plugin 1.2 Hudson Ruby Plugin 1.2 ShiningPanda Plugin 0.20 Show Build Parameters plugin 1.0 Jenkins SSH Slaves plugin 1.9 Jenkins SSH plugin 2.4 Jenkins Translation Assistance plugin 1.11 Validating String Parameter Plugin 2.2 Jenkins Workspace Cleanup Plugin 0.19 Environment Injector Plugin 1.89 Jenkins Multijob plugin 1.13 Jenkins Cobertura Plugin 1.9.5 GitHub API Plugin 1.59 GitHub plugin 1.10 We have about 100 slaves running both Linux (via ssh) and Windows (via JNLP). Project: Jenkins Priority: Minor Reporter: Matt Legrand
[JIRA] [git-plugin] (JENKINS-27668) Multiple repo configuration dont have seperate local repo directory
Mark Waite resolved JENKINS-27668 as Not A Defect Multiple repo configuration dont have seperate local repo directory The git plugin does not directly support checkout of distinct repositories under a single workspace. If you want to support distinct repositories under a single workspace, you'll need to use the multi-SCM's plugin to configure the separate repositories. Change By: Mark Waite (30/Mar/15 4:10 PM) Status: Open Resolved Resolution: Not A Defect 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-26777) Build reports to be running for "45 yr and counting"
dogfood commented on JENKINS-26777 Build reports to be running for "45 yr and counting" Integrated in jenkins_main_trunk #4054 [FIXED JENKINS-26777] Build reports to be running for 45 yr and counting (Revision c2c9a3ef371974ccb5b319c412b35d059974087c) Result = SUCCESS oldelvet : c2c9a3ef371974ccb5b319c412b35d059974087c Files : core/src/test/java/hudson/model/RunTest.java core/src/main/resources/hudson/model/Messages.properties core/src/main/java/hudson/model/Run.java 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27474) BasicStep - FileExistsStep
SCM/JIRA link daemon commented on JENKINS-27474 BasicStep - FileExistsStep Code changed in jenkins User: Jesse Glick Path: CHANGES.md http://jenkins-ci.org/commit/workflow-plugin/205f27b059414466f83ca4de7f99921c93336821 Log: [FIXED JENKINS-27474] Noting. 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27474) BasicStep - FileExistsStep
SCM/JIRA link daemon resolved JENKINS-27474 as Fixed BasicStep - FileExistsStep Change By: SCM/JIRA link daemon (30/Mar/15 4:08 PM) Status: In Progress Resolved Resolution: 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/d/optout.
AVAILABLE CONSULTANT HOTLIST
*Greetings from Humac Inc.,* *Dear business partner, here is the updated list of available consultants from Humac for your daily requirements.* *Kindly contact us over email / **phone for quick response**. Wishing to have a successful business future with you.* *Technology* *Visa* *Relocation* *Availability* *Contact* COGNOS BI DEVELOPER *H1B* *NC, ONLY* *Immediate* *g...@humacinc.com ** / 623-748-4392* -- Gino Senior IT Recruiter Humac Inc Phone: 623-748-4392 Email: g...@humacinc.com -- 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-27474) BasicStep - FileExistsStep
SCM/JIRA link daemon commented on JENKINS-27474 BasicStep - FileExistsStep Code changed in jenkins User: Jesse Glick Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/ReadWriteFileStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/FileExistsStep.java basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/FileExistsStep/config.jelly basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/FileExistsStep/help-file.html http://jenkins-ci.org/commit/workflow-plugin/b351b56e6aee356b8e4bdb9d57001c9f99db3741 Log: Merge pull request #91 from nexus49/master JENKINS-27474 Adding build step File Exists Compare: https://github.com/jenkinsci/workflow-plugin/compare/bf05beb8010f...b351b56e6aee 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/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27474) BasicStep - FileExistsStep
SCM/JIRA link daemon commented on JENKINS-27474 BasicStep - FileExistsStep Code changed in jenkins User: nexus49 Path: aggregator/src/test/java/org/jenkinsci/plugins/workflow/steps/ReadWriteFileStepTest.java basic-steps/src/main/java/org/jenkinsci/plugins/workflow/steps/FileExistsStep.java basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/FileExistsStep/config.jelly basic-steps/src/main/resources/org/jenkinsci/plugins/workflow/steps/FileExistsStep/help-file.html http://jenkins-ci.org/commit/workflow-plugin/95befcbc00014ebf23aaf184f6baad81368f5767 Log: JENKINS-27474 Incorporated pull request feedback 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/d/optout.
AVAILABLE CONSULTANT HOTLIST
*Greetings from Humac Inc.,* *Dear business partner, here is the updated list of available consultants from Humac for your daily requirements.* *Kindly contact us over email / **phone for quick response**. Wishing to have a successful business future with you.* *Technology* *Visa* *Relocation* *Availability* *Contact* COGNOS BI DEVELOPER *H1B* *NC, ONLY* *Immediate* *g...@humacinc.com ** / 623-748-4392* -- Gino Senior IT Recruiter Humac Inc Phone: 623-748-4392 Email: g...@humacinc.com -- 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] [performance-plugin] (JENKINS-27671) java.lang.Error: Unresolved compilation problem: Messages cannot be resolved
David Karlsen created JENKINS-27671 java.lang.Error: Unresolved compilation problem: Messages cannot be resolved Issue Type: Bug Assignee: Manuel Carrasco Components: performance-plugin Created: 30/Mar/15 4:05 PM Description: I get the enclosed exception when I access the url /performance/testsuiteReport/respondingTimeGraphPerTestCaseMode?width=900&height=550&performanceReportPosition=testreport.jtl&performanceReportTest=testreport javax.servlet.ServletException: java.lang.Error: Unresolved compilation problem: Messages cannot be resolved at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:795) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:391) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:745) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:875) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:648) at org.kohsuke.stapler.Stapler.service(Stapler.java:237) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at com.cloudbees.jenkins.support.slowrequest.SlowRequestFilter.doFilter(SlowRequestFilter.java:37) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter._doFilter(OfflineSecurityRealmFilter.java:67) at com.cloudbees.opscenter.client.plugin.OfflineSecurityRealmFilter.doFilter(OfflineSecurityRealmFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.cloudbees.opscenter.security.ClusterSessionFilter._doFilter(ClusterSessionFilter.java:69) at com.cloudbees.opscenter.security.ClusterSessionFilter.doFilter(ClusterSessionFilter.java:44) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:198) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:176) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:85) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:97) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:89) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at jenkins.metrics.impl.MetricsFilter.doFilter(MetricsFilter.java:117) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at com.cloudbees.jenkins.ha.HAHealthCheckFilter.doFilter(HAHealthCheckFilter.java:39) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter
[JIRA] [core] (JENKINS-4409) Hudson test case leaks temp folders
SCM/JIRA link daemon commented on JENKINS-4409 Hudson test case leaks temp folders Code changed in jenkins User: ikedam Path: test/src/main/java/org/jvnet/hudson/test/HudsonTestCase.java test/src/main/java/org/jvnet/hudson/test/JenkinsRule.java http://jenkins-ci.org/commit/jenkins/9bce20951c3ffe8e83a18a5a8d5743e183ebf3a8 Log: [FIXED JENKINS-4409] Disable URLConnection.useCache in tests on Windows. It prevents deleting temporary directories when tests finish. (cherry picked from commit c4e5fbdbc9c644f1afcae031b3b4638ad5297238) 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/d/optout.
[JIRA] [core] (JENKINS-26718) Can't discard promoted-builds Promotions
SCM/JIRA link daemon commented on JENKINS-26718 Can't discard promoted-builds Promotions Code changed in jenkins User: Ryan Campbell Path: core/src/main/java/hudson/diagnosis/OldDataMonitor.java test/src/test/java/hudson/diagnosis/OldDataMonitorTest.java http://jenkins-ci.org/commit/jenkins/5ed111f0bc4aa1b2608b2aa780bc8778ef6ae60a Log: JENKINS-26718 Allow runs to be discarded even if their project can't be found by its fullname (cherry picked from commit 327f7780133b2e6083f49686e43298af83b0dea6) 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/d/optout.
[JIRA] [core] (JENKINS-26684) Maven build step fail to launch mvn process when special chars are present in build variables
SCM/JIRA link daemon commented on JENKINS-26684 Maven build step fail to launch mvn process when special chars are present in build variables Code changed in jenkins User: Oliver Gondža Path: core/src/main/java/hudson/tasks/Maven.java http://jenkins-ci.org/commit/jenkins/9eaba2af9f0fa2649390f83b9b67fe6ee22fe1ad Log: [FIXED JENKINS-26684] Escape special chars in maven build step arguments (cherry picked from commit 58a41bcb182290de681da01ba277b5e0d6211707) 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/d/optout.
[JIRA] [core] (JENKINS-26698) Failure to recover from exception in Publisher.needsToRunAfterFinalized
SCM/JIRA link daemon commented on JENKINS-26698 Failure to recover from exception in Publisher.needsToRunAfterFinalized Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/model/Build.java core/src/main/java/hudson/model/Run.java test/src/test/java/hudson/model/BuildExecutionTest.java http://jenkins-ci.org/commit/jenkins/7e72e7d1218e3443650d8d0c1e20b70d558422b0 Log: JENKINS-26698 Make sure BuildExecution.cleanUp always calls super, to release the workspace lease. Also stop closing the build log in Run.handleFatalBuildProblem; we want to see any subsequent messages too. (cherry picked from commit 62af87b67a1097376b9af554421e621d32f7013f) 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/d/optout.
[JIRA] [build-monitor-plugin] (JENKINS-27183) Deadlock when renaming and updating item in the same view
SCM/JIRA link daemon commented on JENKINS-27183 Deadlock when renaming and updating item in the same view Code changed in jenkins User: Felix Belzunce Arcos Path: core/src/main/java/hudson/model/AbstractItem.java http://jenkins-ci.org/commit/jenkins/f4611b7c3376d23a55e7857c15b3d21c8beef25d Log: JENKINS-27183 Avoid deadlock when using build-monitor-plugin (cherry picked from commit fb5540e38c935676d7f58e9d2ce7a84275bb898f) Compare: https://github.com/jenkinsci/jenkins/compare/dbd262bc0b7d...f4611b7c3376 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/d/optout.
[JIRA] [core] (JENKINS-26684) Maven build step fail to launch mvn process when special chars are present in build variables
SCM/JIRA link daemon commented on JENKINS-26684 Maven build step fail to launch mvn process when special chars are present in build variables Code changed in jenkins User: Oliver Gondža Path: test/src/test/java/hudson/tasks/MavenTest.java http://jenkins-ci.org/commit/jenkins/6e94ee3f5a620a2010dbbcf94eed1e834f1aa114 Log: JENKINS-26684 Reproduce in unittest. (cherry picked from commit fae41b01c9c034ab98216c92ca6bd171b8d81d6b) 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/d/optout.
[JIRA] [core] (JENKINS-26406) Build history text field wrap fails when containing markup
SCM/JIRA link daemon commented on JENKINS-26406 Build history text field wrap fails when containing markup Code changed in jenkins User: tfennelly Path: war/src/main/webapp/css/style.css war/src/main/webapp/scripts/hudson-behavior.js http://jenkins-ci.org/commit/jenkins/446f3cae9f1e660ae48e989a561b7d1ddb722127 Log: [FIXED JENKINS-26406] Build history text field wrap fails when containing markup (cherry picked from commit b31bb1cc1c5a61a3e984e45e33cafa6130517938) 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/d/optout.
[JIRA] [core] (JENKINS-25953) Layout - Tabs in job view are layouted in wrong way
SCM/JIRA link daemon commented on JENKINS-25953 Layout - Tabs in job view are layouted in wrong way Code changed in jenkins User: Piotr Wielgolaski Path: war/src/main/webapp/css/style.css http://jenkins-ci.org/commit/jenkins/f624aab02251fa7d4d97b05d41954d5dc34575a0 Log: JENKINS-25953Tabs in job view are layouted in wrong way make equal height of tab regardless if selected or not (cherry picked from commit 70613202f1177ce83e1d9d724a8b21ca9c222cd3) 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/d/optout.
[JIRA] [mesos-plugin] (JENKINS-27670) Deadlock when calling supervise()
Stefan Eder created JENKINS-27670 Deadlock when calling supervise() Issue Type: Bug Assignee: Vinod Kone Components: mesos-plugin Created: 30/Mar/15 3:27 PM Description: It seems when JenkinsScheduler.statusUpdate() tries to stop the Scheduler and the Retention Timer of a Slave tries to stop a Slave it can somehow end in a deadlock. This is because the Timer locks the MesosImpl instance and statusUpdate() the SUPERVISOR_LOCK. Then MesosImpl tries to terminate the Slave and waits for the SUPERVISOR_LOCK to be freed by the statusUpdate() Thread. However, it seems that statusUpdate() needs a lock on MesosImpl too, when trying to stop the Scheduler. This is the Threaddump (I use a slightly modified version of Mesos plugin 0.6.0, so the linenumbers are probably not 100% right): "Thread-2516073" - Thread t@2898790 java.lang.Thread.State: BLOCKED at org.jenkinsci.plugins.mesos.Mesos$MesosImpl.stopScheduler(Mesos.java:141) - waiting to lock <62132b60> (a org.jenkinsci.plugins.mesos.Mesos$MesosImpl) owned by "jenkins.util.Timer [#9]" t@66 at org.jenkinsci.plugins.mesos.JenkinsScheduler.supervise(JenkinsScheduler.java:749) at org.jenkinsci.plugins.mesos.JenkinsScheduler.statusUpdate(JenkinsScheduler.java:634) Locked ownable synchronizers: - locked <3af5466a> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) "jenkins.util.Timer [#9]" - Thread t@66 java.lang.Thread.State: WAITING at sun.misc.Unsafe.park(Native Method) - waiting to lock <3af5466a> (a java.util.concurrent.locks.ReentrantLock$NonfairSync) owned by "Thread-2516073" t@2898790 at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186) at java.util.concurrent.locks.AbstractQueuedSynchronizer.parkAndCheckInterrupt(AbstractQueuedSynchronizer.java:834) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquireQueued(AbstractQueuedSynchronizer.java:867) at java.util.concurrent.locks.AbstractQueuedSynchronizer.acquire(AbstractQueuedSynchronizer.java:1197) at java.util.concurrent.locks.ReentrantLock$NonfairSync.lock(ReentrantLock.java:214) at java.util.concurrent.locks.ReentrantLock.lock(ReentrantLock.java:290) at org.jenkinsci.plugins.mesos.JenkinsScheduler.supervise(JenkinsScheduler.java:725) at org.jenkinsci.plugins.mesos.JenkinsScheduler.terminateJenkinsSlave(JenkinsScheduler.java:220) - locked <55398768> (a org.jenkinsci.plugins.mesos.JenkinsScheduler) at org.jenkinsci.plugins.mesos.Mesos$MesosImpl.stopJenkinsSlave(Mesos.java:157) - locked <62132b60> (a org.jenkinsci.plugins.mesos.Mesos$MesosImpl) at org.jenkinsci.plugins.mesos.MesosComputerLauncher.terminate(MesosComputerLauncher.java:122) at org.jenkinsci.plugins.mesos.MesosSlave.terminate(MesosSlave.java:91) at org.jenkinsci.plugins.mesos.MesosRetentionStrategy.check(MesosRetentionStrategy.java:70) - locked <75b63404> (a org.jenkinsci.plugins.mesos.MesosRetentionStrategy) at org.jenkinsci.plugins.mesos.MesosRetentionStrategy.check(MesosRetentionStrategy.java:26) at hudson.slaves.ComputerRetentionWork.doRun(ComputerRetentionWork.java:66) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:722) Locked ownable synchronizers: - locked <703c7665> (a java.util.concurrent.ThreadPoolExecutor$Worker) I tried to solve the problem myself, but I somehow got a knot in my brain from all the synchr
[JIRA] [mesos-plugin] (JENKINS-27670) Deadlock when calling supervise()
Stefan Eder updated JENKINS-27670 Deadlock when calling supervise() Change By: Stefan Eder (30/Mar/15 3:27 PM) Priority: Minor Critical 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/d/optout.
[JIRA] [core] (JENKINS-19743) Massive parallel builds sometimes cause errors in LogRotation
Nebu Kadnezar commented on JENKINS-19743 Massive parallel builds sometimes cause errors in LogRotation Hi Daniel, this is not a fix only a working workaround for the issue. See attached Run.txt and LogRotator.txt file for diff 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 -- 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-19743) Massive parallel builds sometimes cause errors in LogRotation
Nebu Kadnezar updated JENKINS-19743 Massive parallel builds sometimes cause errors in LogRotation Change By: Nebu Kadnezar (30/Mar/15 3:16 PM) Attachment: LogRotator.txt Attachment: Run.txt 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/d/optout.
[JIRA] [core] (JENKINS-27616) Installing JDK on Windows Slaves deletes existing Java installation and reboots Slave
Lieven Cardoen commented on JENKINS-27616 Installing JDK on Windows Slaves deletes existing Java installation and reboots Slave The issue also occurred on a version previous to 1.599, but I can't say which one it was. I'm certain it was a 1.59x version. Now I'm on 1.606. 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/d/optout.
[JIRA] [docker-build-step-plugin] (JENKINS-27369) Image push fails with "FATAL: authConfig was not specified"
Kristoffer Peterhänsel commented on JENKINS-27369 Image push fails with "FATAL: authConfig was not specified" Creating an empty credentials entry makes it run for me. But that is just a workaround 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/d/optout.
[JIRA] [support-core-plugin] (JENKINS-27669) Creating an empty logger crashs Jenkins
Yoann Dubreuil created JENKINS-27669 Creating an empty logger crashs Jenkins Issue Type: Bug Assignee: Steven Christou Components: support-core-plugin Created: 30/Mar/15 3:03 PM Description: With support bundle plugin installed, when I create a new logger and let the logger classname field empty, Jenkins crashes when I click Save button. On save, Jenkins starts to write tons of exception logs and is not responsible anymore. Killing the JVM is the only way to stop it doing this. Logged exception looks like this one: Exception in thread "RequestHandlerThread[#10]" java.lang.ClassCircularityError: hudson/logging/LogRecorder at com.cloudbees.jenkins.support.impl.JenkinsLogs$CustomHandler.publish(JenkinsLogs.java:507) at java.util.logging.Logger.log(Logger.java:616) at java.util.logging.Logger.doLog(Logger.java:641) at java.util.logging.Logger.log(Logger.java:730) at org.eclipse.jetty.util.log.JavaUtilLog.warn(JavaUtilLog.java:70) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:698) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:52) at winstone.BoundedExecutorService$1.run(BoundedExecutorService.java:77) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745) On 1.580, faulty configuration is saved on disk. To restart the instance, faulty configuration file $JENKINS_HOME/log/.xml must be removed. On 1.606, configuration is not saved, so restarting the instance works. Environment: core 1.606 support bundle 2.20 Project: Jenkins Labels: robustness Priority: Critical Reporter: Yoann Dubreuil 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/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26802) Copying artifacts from many projects
Joachim Nilsson edited a comment on JENKINS-26802 Copying artifacts from many projects I second this. We have a pipeline of currently 50 integration test jobs that probably will increase to several hundred later. Define one by one? No thanks! Do we need the artifacts? Yes, each integration test job will result in JaCoCo coverage files that should be gathered to generate reports. 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/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-26802) Copying artifacts from many projects
Joachim Nilsson commented on JENKINS-26802 Copying artifacts from many projects I second this. We have a pipeline of currently 50 jobs that probably will increase to several hundred later. Define one by one? No thanks! 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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-25891) Ability to link to individual pipeline
Nick Johns commented on JENKINS-25891 Ability to link to individual pipeline I would like to second this request, we would find this very useful! 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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27667) Unable to view more than 10 pipelines
Nick Johns created JENKINS-27667 Unable to view more than 10 pipelines Issue Type: Improvement Assignee: Patrik Boström Components: delivery-pipeline-plugin Created: 30/Mar/15 1:08 PM Description: Can't see more than 10 pipelines in the past, configuration only allows up to 10 pipelines to be displayed. This means we can't proceed to the next step for builds for older pipelines. We can currently work around this by updating the setting to a larger value in the XML configuration and restarting jenkins. Environment: Jenkins ver. 1.599 Project: Jenkins Priority: Minor Reporter: Nick Johns 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/d/optout.
[JIRA] [git-plugin] (JENKINS-27668) Multiple repo configuration dont have seperate local repo directory
Sagayaraj David created JENKINS-27668 Multiple repo configuration dont have seperate local repo directory Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 30/Mar/15 1:08 PM Description: I have two repos namely - commonlib.git, project1.git, and both of the have the root directories Source and CM. My Jenkins job is MultiGit_Job. I tried to configure a Jenkins job with two repos. During build, the source code for the first project is extracted (found when monitoring during the build execution) and the job fails during the second repo cloning. When I have analyzed the job's workspace, the commonlib.git source is extracted directly under workspace. There is identifier for commonlib repo. Because project1 repo also same root structure, the cloning is failing. It is a critical item for us as we are migrating our projects to GIT now. Thanks Project: Jenkins Labels: Multi-repo multiple-repo Priority: Major Reporter: Sagayaraj David 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/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-27615) Stack trace displayed on build pages
Christian Gnüchtel commented on JENKINS-27615 Stack trace displayed on build pages Yes, we are running version 1.4.7 of the Build Pipeline plugin. Two of the problematic builds are of date 2014/09/26. I cannot remember the exact version which run here on that date. But it should be 1.4.3 or lower according to that page: https://github.com/jenkinsci/build-pipeline-plugin/releases 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/d/optout.
[JIRA] [matrix-project-plugin] (JENKINS-24608) Test result link displays twice on matrix project page
Hema Raghavendra Sai Bonthala commented on JENKINS-24608 Test result link displays twice on matrix project page I already had it in the Post build section only... 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-26777) Build reports to be running for "45 yr and counting"
SCM/JIRA link daemon resolved JENKINS-26777 as Fixed Build reports to be running for "45 yr and counting" Change By: SCM/JIRA link daemon (30/Mar/15 12:19 PM) Status: Open Resolved Resolution: 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-26777) Build reports to be running for "45 yr and counting"
SCM/JIRA link daemon commented on JENKINS-26777 Build reports to be running for "45 yr and counting" Code changed in jenkins User: Richard Mortimer Path: changelog.html core/src/main/java/hudson/model/Run.java core/src/main/resources/hudson/model/Messages.properties core/src/test/java/hudson/model/RunTest.java http://jenkins-ci.org/commit/jenkins/7bb61a248e59c3baa8e06ccb85db9a31fd45272b Log: Merge fix for 'JENKINS-26777' Compare: https://github.com/jenkinsci/jenkins/compare/37964df00664...7bb61a248e59 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-26777) Build reports to be running for "45 yr and counting"
SCM/JIRA link daemon commented on JENKINS-26777 Build reports to be running for "45 yr and counting" Code changed in jenkins User: Richard Mortimer Path: core/src/main/java/hudson/model/Run.java core/src/main/resources/hudson/model/Messages.properties core/src/test/java/hudson/model/RunTest.java http://jenkins-ci.org/commit/jenkins/c2c9a3ef371974ccb5b319c412b35d059974087c Log: [FIXED JENKINS-26777] Build reports to be running for 45 yr and counting 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/d/optout.
[JIRA] [maven-plugin] (JENKINS-26777) Build reports to be running for "45 yr and counting"
Richard Mortimer assigned JENKINS-26777 to Richard Mortimer Build reports to be running for "45 yr and counting" Change By: Richard Mortimer (30/Mar/15 12:18 PM) Assignee: Richard Mortimer 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/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Daniel Beck commented on JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node Would be interesting if you could narrow down the versions of Jenkins the issue originally appeared 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/d/optout.
[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
SCM/JIRA link daemon commented on JENKINS-25127 Hook uninstalled if job is in a subfolder Code changed in jenkins User: Kanstantsin Shautsou Path: src/main/java/com/cloudbees/jenkins/GitHubPushTrigger.java src/main/resources/com/cloudbees/jenkins/GitHubPushTrigger/global.jelly http://jenkins-ci.org/commit/github-plugin/6154cedfe18f265aea25756284a3472696eceaff Log: JENKINS-25127 Add Button for registering all hooks 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/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke updated JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node Added "build-flow-plugin" as a component. Change By: Parag Doke (30/Mar/15 11:27 AM) Component/s: build-flow-plugin 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/d/optout.
[JIRA] [build-flow-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke updated JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node Added "core" as a component. Change By: Parag Doke (30/Mar/15 11:26 AM) Component/s: core 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/d/optout.
[JIRA] [vsphere-cloud-plugin] (JENKINS-27213) Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node
Parag Doke commented on JENKINS-27213 Recent vsphere-cloud plugin and build-flow plugin versions don't identify any node I tried this combination today and it was able to identify a vsphere slave node correctly: vsphere-cloud version 2.3 build-flow plugin version 0.16 Jenkins version 1.583 Out of curiosity, I updated both plugins ... and let Jenkins stay at 1.583. That worked too. So this combination also works: vsphere-slave plugin 2.4 build-flow plugin 0.17 Jenkins version 1.583 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/d/optout.
[JIRA] [build-flow-extensions] (JENKINS-27666) Some jobs can't be started after updating Build Blocker Plugin from 1.4.1 to 1.6
Slawomir Czarko created JENKINS-27666 Some jobs can't be started after updating Build Blocker Plugin from 1.4.1 to 1.6 Issue Type: Bug Assignee: Unassigned Components: build-flow-extensions Created: 30/Mar/15 10:35 AM Description: Nothing in the log. Downgrading back to 1.4.1 fixes the problem. Environment: Jenkins LTS 1.596.2 Project: Jenkins Priority: Major Reporter: Slawomir Czarko 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/d/optout.
[JIRA] [core] (JENKINS-27616) Installing JDK on Windows Slaves deletes existing Java installation and reboots Slave
Daniel Beck updated JENKINS-27616 Installing JDK on Windows Slaves deletes existing Java installation and reboots Slave Adding env-inject component. If you could test whether this issue occurs on Jenkins 1.599, that would be helpful. 1.600 included a change to environment variable handling that is believed to have been fixed, but confirmation would be helpful. Change By: Daniel Beck (30/Mar/15 10:26 AM) Assignee: Gregory Boissinot Component/s: envinject-plugin 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/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-27615) Stack trace displayed on build pages
Daniel Beck commented on JENKINS-27615 Stack trace displayed on build pages Your issue report indicates it's build pipeline as that is referenced in the line you quote as breaking the UI. JENKINS-27537 appears to have the same cause, an incompatible code change in the plugin in the build causes. If you could confirm you have installed Build Pipeline 1.4.6 or newer, and used an older version when the build was created, that would be a strong indication it's the cause. 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/d/optout.
[JIRA] [envinject-plugin] (JENKINS-27665) NPE after updating EnvInject Plugin from 1.90 to 1.91.1
Slawomir Czarko created JENKINS-27665 NPE after updating EnvInject Plugin from 1.90 to 1.91.1 Issue Type: Bug Assignee: Gregory Boissinot Components: envinject-plugin Created: 30/Mar/15 10:20 AM Description: java.lang.NullPointerException at org.jenkinsci.lib.envinject.EnvInjectAction$1.transformEntry(EnvInjectAction.java:94) at org.jenkinsci.lib.envinject.EnvInjectAction$1.transformEntry(EnvInjectAction.java:92) at com.google.common.collect.Maps$TransformedEntriesMap$1$1.apply(Maps.java:1218) at com.google.common.collect.Maps$TransformedEntriesMap$1$1.apply(Maps.java:1216) at com.google.common.collect.Iterators$8.next(Iterators.java:812) at java.util.AbstractMap.putAll(AbstractMap.java:272) at java.util.TreeMap.putAll(TreeMap.java:321) at org.jenkinsci.lib.envinject.service.EnvInjectSavable.saveEnvironment(EnvInjectSavable.java:54) at org.jenkinsci.lib.envinject.EnvInjectAction.writeReplace(EnvInjectAction.java:91) 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:616) at com.thoughtworks.xstream.converters.reflection.SerializationMethodInvoker.callWriteReplace(SerializationMethodInvoker.java:89) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:99) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:88) at com.thoughtworks.xstream.converters.collections.AbstractCollectionConverter.writeItem(AbstractCollectionConverter.java:64) at com.thoughtworks.xstream.converters.collections.CollectionConverter.marshal(CollectionConverter.java:74) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller$1.convertAnother(AbstractReferenceMarshaller.java:84) at hudson.util.RobustReflectionConverter.marshallField(RobustReflectionConverter.java:223) at hudson.util.RobustReflectionConverter$2.writeField(RobustReflectionConverter.java:210) at hudson.util.RobustReflectionConverter$2.visit(RobustReflectionConverter.java:182) at com.thoughtworks.xstream.converters.reflection.PureJavaReflectionProvider.visitSerializableFields(PureJavaReflectionProvider.java:138) at hudson.util.RobustReflectionConverter.doMarshal(RobustReflectionConverter.java:167) at hudson.util.RobustReflectionConverter.marshal(RobustReflectionConverter.java:108) at com.thoughtworks.xstream.core.AbstractReferenceMarshaller.convert(AbstractReferenceMarshaller.java:69) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:58) at com.thoughtworks.xstream.core.TreeMarshaller.convertAnother(TreeMarshaller.java:43) at com.thoughtworks.xstream.core.TreeMarshaller.start(TreeMarshaller.java:82) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.marshal(AbstractTreeMarshallingStrategy.java:37) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1026) at com.thoughtworks.xstream.XStream.marshal(XStream.java:1015) at com.thoughtworks.xstream.XStream.toXML(XStream.java:988) at hudson.XmlFile.write(XmlFile.java:178) at hudson.model.Run.save(Run.java:1929) at hudson.plugins.changelog_history.ChangeLogHistoryRunListener.copyChangeLogs(ChangeLogHistoryRunListener.java:82) at hudson.plugins.changelog_history.ChangeLogHistoryRunListener.onDeleted(ChangeLogHistoryRunListener.java:50) at hudson.plugins.changelog_history.ChangeLogHistoryRunListener.onDeleted(ChangeLogHistoryRunListener.java:40) at hudson.model.listeners.Ru
[JIRA] [build-pipeline-plugin] (JENKINS-27615) Stack trace displayed on build pages
Christian Gnüchtel commented on JENKINS-27615 Stack trace displayed on build pages Just to be curious ... Why do you think the Build Pipeline plugin is the cause? Did you have seen a similar stack trace in the past?! Where can you see the Build Pipeline plugin in the stack trace? 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/d/optout.
[JIRA] [core] (JENKINS-27616) Installing JDK on Windows Slaves deletes existing Java installation and reboots Slave
Lieven Cardoen commented on JENKINS-27616 Installing JDK on Windows Slaves deletes existing Java installation and reboots Slave No, issue doe not appear when I disable the Env-Inject plugin... But I do use that plugin, so what are the next steps? Strange that the plugin messes up core functionality... Kind regards, Lieven Cardoen 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/d/optout.
[JIRA] [core] (JENKINS-27664) Job hanging, killing not possible
Kevin Rancka commented on JENKINS-27664 Job hanging, killing not possible The end of the console output of the job: 10:08:04 [INFO] WEB-INF/web.xml already added, skipping 10:08:04 [JENKINS] Archiving disabled 10:08:04 [INFO] 10:08:04 [INFO] BUILD SUCCESS 10:08:04 [INFO] 10:08:04 [INFO] Total time: 1:10.621s 10:08:04 [INFO] Finished at: Mon Mar 30 10:08:04 CEST 2015 10:08:05 [INFO] Final Memory: 44M/229M 10:08:05 [INFO] 10:08:05 [JENKINS] Archiving disabled 10:08:05 Waiting for Jenkins to finish collecting data 10:08:05 [ssh-agent] Stopped. 10:08:05 channel stopped 10:08:05 [WARNINGS] Parsing warnings in console log with parser Java Compiler (Eclipse) 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/d/optout.
[JIRA] [core] (JENKINS-27664) Job hanging, killing not possible
Kevin Rancka created JENKINS-27664 Job hanging, killing not possible Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Mar/15 8:41 AM Description: I have a job that keeps hanging everytime it builds. The job ran fine in the past. No changes happend and suddenly it started hanging. ThradDump: Executor #0 for Slave_rlx-v121 : executing m_techlog_reporting/zk.mtr.build #945 "Executor #0 for Slave_rlx-v121 : executing m_techlog_reporting/zk.mtr.build #945" Id=79 Group=main RUNNABLE at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4692) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Pattern.java:4556) at java.util.regex.Pattern$Loop.match(Pattern.java:4683) at java.util.regex.Pattern$GroupTail.match(Pattern.java:4615) at java.util.regex.Pattern$Curly.match0(Pattern.java:4170) at java.util.regex.Pattern$Curly.match(Pattern.java:4132) at java.util.regex.Pattern$BmpCharProperty.match(Pattern.java:3715) at java.util.regex.Pattern$Ques.match(Pattern.java:4079) at java.util.regex.Pattern$GroupHead.match(Patte
[JIRA] [github-plugin] (JENKINS-25127) Hook uninstalled if job is in a subfolder
Leandro Lucarella commented on JENKINS-25127 Hook uninstalled if job is in a subfolder I tested the PR and the re-register button seems to work fine, thanks! 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/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-27354) Error communicating to server! timeout
Jouni Rajala commented on JENKINS-27354 Error communicating to server! timeout I have same issue, but noticed it has something to do with my slave confuguration. Jobs that are run on master server are shown in diagram, but anything run on slave machines causes 'error communicating to server! timeout' Configuration consist windows master and multiple windows slave machines. 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/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27662) Double quotes in commit message results in merge failure (Praqma case 12871)
Bue Petersen started work on JENKINS-27662 Double quotes in commit message results in merge failure (Praqma case 12871) Change By: Bue Petersen (30/Mar/15 8:00 AM) Status: Open In Progress 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/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27662) Double quotes in commit message results in merge failure
Bue Petersen commented on JENKINS-27662 Double quotes in commit message results in merge failure This problem could also indirectly be reported as JENKINS-27309 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/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27662) Double quotes in commit message results in merge failure (Praqma case 12871)
Bue Petersen updated JENKINS-27662 Double quotes in commit message results in merge failure (Praqma case 12871) Change By: Bue Petersen (30/Mar/15 7:45 AM) Summary: Double quotes in commit message results in merge failure (Praqma case 12871) 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/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27309) Plugin always leads to merge failure (case 12800)
Bue Petersen commented on JENKINS-27309 Plugin always leads to merge failure (case 12800) This issue could be related to JENKINS-27662. If we don't get further feedback on this issue, we will resolve as dublicate of JENKINS-27662. 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/d/optout.
[JIRA] [core] (JENKINS-27663) Bad execution time for jobs periodically executed
Ludovic Vercruysse created JENKINS-27663 Bad execution time for jobs periodically executed Issue Type: Bug Assignee: Unassigned Components: core Created: 30/Mar/15 7:44 AM Description: Dear, On our platform, we have 3 jenkins instances based on the LTS 1.596.1 On each of these 3 jenkins instances, I have created a free-style job which is periodically executed each 2 minutes. This job does nothing else (no checkout from a repository, no maven build, etc - this is the more basic job which can be done) On the first 2 jenkins instances, the job is well executed every 2 minutes. However, on the third one, it is randomly executed (more or less every 20 minutes). This makes me think that I have a configuration issue on my third jenkins instance. On 27/03, I have added some logs in the Jenkins administration panel and found the following stack trace: cron checking 3/27/15 4:49 AM whereas the date on the server was different: [www@MYSERVER ~]$ date Fri Mar 27 10:32:27 CET 2015 In order to allow me to investigate on this issue and identify the difference between my 3 servers, I would need to know if there is a configuration file or a specific directory which manages the date of the jenkins crontab. Could you please explain how the cron process works inside Jenkins ? Please note that our Jenkins instances use: user.timezone=Europe/Paris Best regards Project: Jenkins Priority: Major Reporter: Ludovic Vercruysse 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/d/optout.
[JIRA] [pretested-integration-plugin] (JENKINS-27662) Double quotes in commit message results in merge failure
Bue Petersen created JENKINS-27662 Double quotes in commit message results in merge failure Issue Type: Bug Assignee: Praqma Support Components: pretested-integration-plugin Created: 30/Mar/15 7:41 AM Description: Merge fails when commit message has "" double quotes. Work around: Modify commits messages and push again. Environment: pretested-integration-plugin-2.2.1 Project: Jenkins Priority: Minor Reporter: Bue Petersen 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/d/optout.
[JIRA] [jenkins-tracker] (JENKINS-27645) High memory usage by Jenkins ver. 1.580.1 & slave error
NARAYAN PRADHAN edited a comment on JENKINS-27645 High memory usage by Jenkins ver. 1.580.1 & slave error I am sorry, but whatever I have put it should consider as bug. 1> highe memory usage 2> and error in downstream job if this need to be put somewhere else, then i may need someones help 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/d/optout.
