[JIRA] [job-dsl-plugin] (JENKINS-27767) No such property: jobManagement for class:
Daniel Spilker commented on JENKINS-27767 No such property: jobManagement for class: Thanks for reporting this. A fix is underway: https://github.com/jenkinsci/job-dsl-plugin/pull/437 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-27262) email is not sent
Ferry Huberts commented on JENKINS-27262 email is not sent I'm sorry, I thought I did describe it better. The mail server is configured as 'mygit' with 'mygit' in /etc/hosts as '1.2.3.4 mygit'. The job is configured to send an email notification to 'proj_myapp' for every unstable build. 'proj_myapp' is an alias that is configured on 'mygit', and to which I can send email without problems. Before this used to work just fine. I don't know which version of Jenkins broke it since I don't regularly update Jenkins and don't have failing builds very often. It still doesn't work for Jenkins 1.607. 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] [packaging] (JENKINS-27776) Packaging doesn't work, 1.608 release is incomplete
Daniel Beck created JENKINS-27776 Packaging doesn't work, 1.608 release is incomplete Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 07/Apr/15 8:19 AM Description: It looks like the release of 1.608 from the new repos didn't work 100%: war/latest still points to 1.607 osx/latest still points to 1.607 windows/latest still points to 1.607 There's no Debian package for 1.608: http://pkg.jenkins-ci.org/debian/ There's no Red Hat package for 1.608: http://pkg.jenkins-ci.org/redhat/ Project: Jenkins Priority: Critical Reporter: Daniel Beck 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] [job-dsl-plugin] (JENKINS-27767) No such property: jobManagement for class:
SCM/JIRA link daemon commented on JENKINS-27767 No such property: jobManagement for class: Code changed in jenkins User: Daniel Spilker Path: job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy http://jenkins-ci.org/commit/job-dsl-plugin/4ec727824ca8a854272b1099c5395598ccb369a6 Log: Merge pull request #437 from CoreMedia/JENKINS-27767 Fixed JENKINS-27767 Compare: https://github.com/jenkinsci/job-dsl-plugin/compare/4c607b8279a8...4ec727824ca8 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] [job-dsl-plugin] (JENKINS-27767) No such property: jobManagement for class:
Daniel Spilker resolved JENKINS-27767 as Fixed No such property: jobManagement for class: Change By: Daniel Spilker (07/Apr/15 8:40 AM) 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] [job-dsl-plugin] (JENKINS-27767) No such property: jobManagement for class:
SCM/JIRA link daemon commented on JENKINS-27767 No such property: jobManagement for class: Code changed in jenkins User: Daniel Spilker Path: job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/publisher/PublisherContext.groovy http://jenkins-ci.org/commit/job-dsl-plugin/0e72825bad5a9c4c480e747521c4db0811650f78 Log: fixed JENKINS-27767 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] [zentimestamp-plugin] (JENKINS-26626) Zentimestamp plugin no longer compatible with Jenkins 1.597
SCM/JIRA link daemon commented on JENKINS-26626 Zentimestamp plugin no longer compatible with Jenkins 1.597 Code changed in jenkins User: Gregory Boissinot Path: pom.xml src/ittest/java/hudson/plugins/zentimestamp/ZenTimestampJobPropertyTest.java src/main/java/hudson/plugins/zentimestamp/ZenTimestampAction.java src/main/java/hudson/plugins/zentimestamp/ZenTimestampEnvironmentContributor.java src/main/java/hudson/plugins/zentimestamp/ZenTimestampFormatBuildWrapper.java src/main/java/hudson/plugins/zentimestamp/ZenTimestampNodeProperty.java src/main/java/hudson/plugins/zentimestamp/ZenTimestampRunListener.java src/main/resources/hudson/plugins/zentimestamp/Messages.properties src/main/resources/hudson/plugins/zentimestamp/ZenTimestampFormatBuildWrapper/help-pattern.html src/main/resources/hudson/plugins/zentimestamp/ZenTimestampJobProperty/config.properties src/main/resources/hudson/plugins/zentimestamp/ZenTimestampJobProperty/help-changeBUILDID.html src/main/resources/index.jelly src/main/webapp/help-node.html http://jenkins-ci.org/commit/zentimestamp-plugin/d0489822ae9081a09b63ccf413302973e25686bb Log: Merge pull request #1 from christ66/JENKINS-26626 JENKINS-26626 Switch to use BUILD_TIMESTAMP environment variable Compare: https://github.com/jenkinsci/zentimestamp-plugin/compare/c04098bcef9f...d0489822ae90 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] [zentimestamp-plugin] (JENKINS-26626) Zentimestamp plugin no longer compatible with Jenkins 1.597
SCM/JIRA link daemon commented on JENKINS-26626 Zentimestamp plugin no longer compatible with Jenkins 1.597 Code changed in jenkins User: christ66 Path: pom.xml src/ittest/java/hudson/plugins/zentimestamp/ZenTimestampJobPropertyTest.java src/main/java/hudson/plugins/zentimestamp/ZenTimestampAction.java src/main/java/hudson/plugins/zentimestamp/ZenTimestampEnvironmentContributor.java src/main/java/hudson/plugins/zentimestamp/ZenTimestampFormatBuildWrapper.java src/main/java/hudson/plugins/zentimestamp/ZenTimestampNodeProperty.java src/main/java/hudson/plugins/zentimestamp/ZenTimestampRunListener.java src/main/resources/hudson/plugins/zentimestamp/Messages.properties src/main/resources/hudson/plugins/zentimestamp/ZenTimestampFormatBuildWrapper/help-pattern.html src/main/resources/hudson/plugins/zentimestamp/ZenTimestampJobProperty/config.properties src/main/resources/hudson/plugins/zentimestamp/ZenTimestampJobProperty/help-changeBUILDID.html src/main/resources/index.jelly src/main/webapp/help-node.html http://jenkins-ci.org/commit/zentimestamp-plugin/3bbe8cfc2c77ee663d68e2f64914edaee5981add Log: JENKINS-26626 Switch to use BUILD_TIMESTAMP environment variable instead of the BUILD_ID. Newer versions of Jenkins use the BUID_ID as being the build number. 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] [jobconfighistory-plugin] (JENKINS-20988) Deadlock inPluginUtils.getHistoryDao
SCM/JIRA link daemon commented on JENKINS-20988 Deadlock inPluginUtils.getHistoryDao Code changed in jenkins User: Thomas de Grenier de Latour Path: src/main/java/hudson/plugins/jobConfigHistory/JobConfigHistorySaveableListener.java src/main/java/hudson/plugins/jobConfigHistory/PluginUtils.java src/test/java/hudson/plugins/jobConfigHistory/JobConfigHistorySaveableListenerTest.java http://jenkins-ci.org/commit/jobConfigHistory-plugin/6358945f3dfdc56a81edecfb7567992140714e3a Log: Avoid calling `User.current()` from `JobConfigHistorySaveableListener` during Jenkins initialization When `jobConfigHistory` is used used together with the `sonar` (2.2) plugin, we get the following stack: ``` hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error WARNING: Failed to instantiate Key[type=hudson.plugins.sonar.SonarPublisher$DescriptorImpl, annotation=[none]]; skipping this component com.google.inject.ProvisionException: Guice provision errors: 1) Tried proxying hudson.plugins.sonar.SonarPublisher$DescriptorImpl to support a circular dependency, but it is not an interface. 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:427) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.InjectorImpl$3.get(InjectorImpl.java:1001) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:389) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:380) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:370) at hudson.ExtensionList.load(ExtensionList.java:300) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.getComponents(ExtensionList.java:154) at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:182) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:253) at hudson.ExtensionList.iterator(ExtensionList.java:143) at hudson.model.User.load(User.java:192) at hudson.model.User.(User.java:143) at hudson.model.User.getOrCreate(User.java:443) at hudson.model.User.current(User.java:487) at hudson.plugins.jobConfigHistory.PluginUtils.getHistoryDao(PluginUtils.java:71) at hudson.plugins.jobConfigHistory.PluginUtils.getHistoryDao(PluginUtils.java:62) at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.getHistoryDao(JobConfigHistorySaveableListener.java:49) at hudson.plugins.jobConfigHistory.JobConfigHistorySaveableListener.onChange(JobConfigHistorySaveableListener.java:28) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:80) at hudson.model.Descriptor.save(Descriptor.java:760) at hudson.plugins.sonar.SonarPublisher$DescriptorImpl.(SonarPublisher.java:420) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:526) at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:86) at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:108) at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:88) at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:269) at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1058) at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40) at com.google.inject.Scopes$1$1.get(Scopes.java:65) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:427) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$3$1.call(InjectorImpl.java:1005) at com.google.inje
[JIRA] [job-dsl-plugin] (JENKINS-27767) No such property: jobManagement for class:
SCM/JIRA link daemon commented on JENKINS-27767 No such property: jobManagement for class: Code changed in jenkins User: Daniel Spilker Path: job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/jobs/MavenJobSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/422b5da60999733875cb849002744bf18da84237 Log: added test for JENKINS-27767 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] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Mattias Vannergård commented on JENKINS-24686 scm-sync-configuration fails if job name contains whitespace Same here. Someone who has a description of how to manually remove the failing commit in git? 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-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Created PR #1641 around efforts to address the issue of huge build histories. Hopefully there'll be a CI build available soon (from CI PR builder). Please try this out and let us know what works, doesn't work, is missing etc 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] [subversion-plugin] (JENKINS-26318) Subversion Plug in 2.5 causes sporadic problems
Tomasz Majchrowski commented on JENKINS-26318 Subversion Plug in 2.5 causes sporadic problems Does anyone notice this problem without BlameSubversion being installed? I recognize that the given class is provided by those two plugins and suspect classloader conflicts $ jar tf ./plugins/subversion/WEB-INF/lib/classes.jar | grep SVNRevisionState hudson/scm/SVNRevisionState.class $ jar tf ./plugins/BlameSubversion/WEB-INF/lib/classes.jar | grep SVNRevisionState hudson/scm/SVNRevisionState.class 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] [promoted-builds-plugin] (JENKINS-24782) Clicking "Build Now" on a Promotion results in a phantom, unkillable build
SCM/JIRA link daemon commented on JENKINS-24782 Clicking "Build Now" on a Promotion results in a phantom, unkillable build Code changed in jenkins User: Stephen Connolly Path: src/main/java/hudson/plugins/promoted_builds/PromotionProcess.java http://jenkins-ci.org/commit/promoted-builds-plugin/2fe54570a00588e28c3cf9549f25af54858099f7 Log: Merge pull request #56 from recampbell/JENKINS-24782 JENKINS-24782 Prevent phantom builds from being scheduled when PromotionProcesses are built directly. Compare: https://github.com/jenkinsci/promoted-builds-plugin/compare/524772c09e5f...2fe54570a005 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-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run It works on some projects now, but it's still way below what we expect. Our main project with a lot of commits hasn't run since last Friday. Might be related to: https://issues.jenkins-ci.org/browse/JENKINS-26208 . I'll upgrade to 1.608. 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] [label-linked-jobs-plugin] (JENKINS-27588) Labels used in Label Factory are shown as not used
SCM/JIRA link daemon commented on JENKINS-27588 Labels used in Label Factory are shown as not used Code changed in jenkins User: Dominique Path: src/main/java/jenkins/plugins/linkedjobs/actions/LabelDashboardAction.java src/main/java/jenkins/plugins/linkedjobs/actions/LabelLinkedJobsAction.java src/main/java/jenkins/plugins/linkedjobs/model/JobsGroup.java src/main/java/jenkins/plugins/linkedjobs/model/LabelAtomData.java src/main/java/jenkins/plugins/linkedjobs/model/NodeData.java src/main/java/jenkins/plugins/linkedjobs/model/TriggeredJob.java src/main/resources/jenkins/plugins/linkedjobs/actions/LabelDashboardAction/index.jelly src/main/resources/jenkins/plugins/linkedjobs/actions/LabelLinkedJobsAction/index.jelly http://jenkins-ci.org/commit/label-linked-jobs-plugin/6ebef7211ee4bf1b61ff55d0b9940789305625f5 Log: JENKINS-27588, Labels Dashboard implementation 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] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Gaston Marengo commented on JENKINS-27100 Regressions in 1.12 and 1.13 Ok, it's half working now. The graphs are there (no error messages at all) but are generated with empty data. 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] [label-linked-jobs-plugin] (JENKINS-27588) Labels used in Label Factory are shown as not used
Dominique Brice commented on JENKINS-27588 Labels used in Label Factory are shown as not used I started working on this improvement and it turns out it's a significant impact to make the plugin compatible with both nodelabelparameter and parameterized-trigger. I hope we're not opening a Pandora box I have already covered the label's page and the main dashboard page, still have to work on the computer's page. Stefan, I have a few questions for you. Do you have a test or staging instance where you could help me to test the plugin before I release it? I created test data based on your comments but I don't use these plugins so it may not be comprehensive. Also, besides the scenario you detailed in your screenshots, is there any other possible interaction (via labels) between labellinkedjobsplugin, nodelabelparameter, and parameterized-trigger? I will attach screenshots of my current progress once Jira let me do so. Disk seems full at the moment. Finally I found a limitation that will remain for now : nodelabelparameter allows use of TokenMacro. From my initial research, TokenMacro requires an AbstractBuild to expand tokens, and I only have access to AbstractProject in my plugin. In other words, I can't trigger a build for all jobs to expand macros to build the label's pages... to be continued. 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] [global-build-stats-plugin] (JENKINS-16475) Build stats graph configuration lost after Jenkins Restart
Christopher Zee commented on JENKINS-16475 Build stats graph configuration lost after Jenkins Restart Same problem for me too: Exception from jenkins.log Mar 17, 2015 8:29:30 PM hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver reloadPlugin SEVERE: Unable to read /opt/jenkins/global-build-stats.xml java.io.IOException: Unable to read /opt/jenkins/global-build-stats.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at hudson.Plugin.load(Plugin.java:241) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.load(GlobalBuildStatsPlugin.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver.reloadPlugin(GlobalBuildStatsPluginSaver.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsBusiness.reloadPlugin(GlobalBuildStatsBusiness.java:382) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener.onLoaded(GlobalBuildStatsPlugin.java:149) at jenkins.model.Jenkins.(Jenkins.java:845) at hudson.model.Hudson.(Hudson.java:82) at hudson.model.Hudson.(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: com.thoughtworks.xstream.converters.ConversionException: : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 Debugging information message : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 cause-exception : com.thoughtworks.xstream.io.StreamException cause-message : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 class : java.util.ArrayList required-type : hudson.plugins.global_build_stats.model.JobBuildResult converter-type : hudson.util.RobustCollectionConverter path: /list/jbr[25971] line number : 311644 version : not available class[1]: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin required-type[1]: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin converter-type[1] : hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter path[1] : /hudson.plugins.global_build_stats.GlobalBuildStatsPlugin line number[1] : 2 --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1044) at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:139) at hudson.plugins.global_build_stats.xstream.migration.AbstractMigrator.readGlobalBuildStatsPOJO(AbstractMigrator.java:35) at hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter.unmarshal(GlobalBuildStatsXStreamConverter.java:159) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xs
[JIRA] [global-build-stats-plugin] (JENKINS-16475) Build stats graph configuration lost after Jenkins Restart
Christopher Zee edited a comment on JENKINS-16475 Build stats graph configuration lost after Jenkins Restart Same problem for me too: Exception from jenkins.log Mar 17, 2015 8:29:30 PM hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver reloadPlugin SEVERE: Unable to read /opt/jenkins/global-build-stats.xml java.io.IOException: Unable to read /opt/jenkins/global-build-stats.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at hudson.Plugin.load(Plugin.java:241) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.load(GlobalBuildStatsPlugin.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver.reloadPlugin(GlobalBuildStatsPluginSaver.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsBusiness.reloadPlugin(GlobalBuildStatsBusiness.java:382) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener.onLoaded(GlobalBuildStatsPlugin.java:149) at jenkins.model.Jenkins.(Jenkins.java:845) at hudson.model.Hudson.(Hudson.java:82) at hudson.model.Hudson.(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: com.thoughtworks.xstream.converters.ConversionException: : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 Debugging information message : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 cause-exception : com.thoughtworks.xstream.io.StreamException cause-message : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 class : java.util.ArrayList required-type : hudson.plugins.global_build_stats.model.JobBuildResult converter-type : hudson.util.RobustCollectionConverter path: /list/jbr[25971] line number : 311644 version : not available class[1]: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin required-type[1]: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin converter-type[1] : hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter path[1] : /hudson.plugins.global_build_stats.GlobalBuildStatsPlugin line number[1] : 2 --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1044) at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:139) at hudson.plugins.global_build_stats.xstream.migration.AbstractMigrator.readGlobalBuildStatsPOJO(AbstractMigrator.java:35) at hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter.unmarshal(GlobalBuildStatsXStreamConverter.java:159) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtwo
[JIRA] [pretested-integration-plugin] (JENKINS-27516) Plugin hangs - reproduced with failed earlier build (Praqma case 12834)
Per Arnold Blaasmo
commented on JENKINS-27516
Plugin hangs - reproduced with failed earlier build (Praqma case 12834)
This happens often on our Jenkins instance.
If one jobs get it, several other jobs using the pretested plugin gets the same problem on the next run.
When I turn on logging I get the following log from the pretested-plugin:
13:54:49 [FINER]PretestedIntegrationBuildWrapper.setUp, 54: ENTRY {0} {1} {2}
13:54:49 [FINER]BuildQueue.getInstance, 24: ENTRY
13:54:49 [FINER]BuildQueue.getInstance, 28: RETURN
13:54:49 [FINER]BuildQueue.enqueueAndWait, 39: ENTRY
13:55:50 [FINER]PretestedIntegrationPostCheckout.needsToRunAfterFinalized, 33: ENTRY
13:55:50 [FINER]PretestedIntegrationPostCheckout.needsToRunAfterFinalized, 34: RETURN
13:55:50 [FINER]PretestedIntegrationPostCheckout.perform, 49: ENTRY {0} {1} {2}
Jenkins core 1.596.2
Master: Linux RHEL 6.5
Slave: Linux Fedora 21
Slave: java-1.8.0-openjdk-1.8.0.25
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] [global-build-stats-plugin] (JENKINS-16475) Build stats graph configuration lost after Jenkins Restart
Christopher Zee edited a comment on JENKINS-16475 Build stats graph configuration lost after Jenkins Restart Same problem for me too on Jenkins v1.580.3-SNAPSHOT and Global Stats Plugin v1.3: Exception from jenkins.log Mar 17, 2015 8:29:30 PM hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver reloadPlugin SEVERE: Unable to read /opt/jenkins/global-build-stats.xml java.io.IOException: Unable to read /opt/jenkins/global-build-stats.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at hudson.Plugin.load(Plugin.java:241) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.load(GlobalBuildStatsPlugin.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver.reloadPlugin(GlobalBuildStatsPluginSaver.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsBusiness.reloadPlugin(GlobalBuildStatsBusiness.java:382) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener.onLoaded(GlobalBuildStatsPlugin.java:149) at jenkins.model.Jenkins.(Jenkins.java:845) at hudson.model.Hudson.(Hudson.java:82) at hudson.model.Hudson.(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: com.thoughtworks.xstream.converters.ConversionException: : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 Debugging information message : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 cause-exception : com.thoughtworks.xstream.io.StreamException cause-message : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 class : java.util.ArrayList required-type : hudson.plugins.global_build_stats.model.JobBuildResult converter-type : hudson.util.RobustCollectionConverter path: /list/jbr[25971] line number : 311644 version : not available class[1]: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin required-type[1]: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin converter-type[1] : hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter path[1] : /hudson.plugins.global_build_stats.GlobalBuildStatsPlugin line number[1] : 2 --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1044) at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:139) at hudson.plugins.global_build_stats.xstream.migration.AbstractMigrator.readGlobalBuildStatsPOJO(AbstractMigrator.java:35) at hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter.unmarshal(GlobalBuildStatsXStreamConverter.java:159) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert
[JIRA] [global-build-stats-plugin] (JENKINS-16475) Build stats graph configuration lost after Jenkins Restart
Christopher Zee edited a comment on JENKINS-16475 Build stats graph configuration lost after Jenkins Restart Same problem for me too on Jenkins v1.580.3-SNAPSHOT and Global Build Stats v1.3: Exception from jenkins.log Mar 17, 2015 8:29:30 PM hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver reloadPlugin SEVERE: Unable to read /opt/jenkins/global-build-stats.xml java.io.IOException: Unable to read /opt/jenkins/global-build-stats.xml at hudson.XmlFile.unmarshal(XmlFile.java:165) at hudson.Plugin.load(Plugin.java:241) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin.load(GlobalBuildStatsPlugin.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsPluginSaver.reloadPlugin(GlobalBuildStatsPluginSaver.java:98) at hudson.plugins.global_build_stats.business.GlobalBuildStatsBusiness.reloadPlugin(GlobalBuildStatsBusiness.java:382) at hudson.plugins.global_build_stats.GlobalBuildStatsPlugin$GlobalBuildStatsItemListener.onLoaded(GlobalBuildStatsPlugin.java:149) at jenkins.model.Jenkins.(Jenkins.java:845) at hudson.model.Hudson.(Hudson.java:82) at hudson.model.Hudson.(Hudson.java:78) at hudson.WebAppMain$3.run(WebAppMain.java:222) Caused by: com.thoughtworks.xstream.converters.ConversionException: : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 Debugging information message : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 cause-exception : com.thoughtworks.xstream.io.StreamException cause-message : : no more data available - expected end tags to close start tag from line 311642 and start tag from line 1, parser stopped on END_TAG seen ...SUCCESS\n ... @311644:3 class : java.util.ArrayList required-type : hudson.plugins.global_build_stats.model.JobBuildResult converter-type : hudson.util.RobustCollectionConverter path: /list/jbr[25971] line number : 311644 version : not available class[1]: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin required-type[1]: hudson.plugins.global_build_stats.GlobalBuildStatsPlugin converter-type[1] : hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter path[1] : /hudson.plugins.global_build_stats.GlobalBuildStatsPlugin line number[1] : 2 --- at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:79) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:50) at com.thoughtworks.xstream.core.TreeUnmarshaller.start(TreeUnmarshaller.java:134) at com.thoughtworks.xstream.core.AbstractTreeMarshallingStrategy.unmarshal(AbstractTreeMarshallingStrategy.java:32) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1189) at hudson.util.XStream2.unmarshal(XStream2.java:113) at com.thoughtworks.xstream.XStream.unmarshal(XStream.java:1173) at com.thoughtworks.xstream.XStream.fromXML(XStream.java:1044) at hudson.plugins.global_build_stats.model.JobBuildResultSharder.load(JobBuildResultSharder.java:139) at hudson.plugins.global_build_stats.xstream.migration.AbstractMigrator.readGlobalBuildStatsPOJO(AbstractMigrator.java:35) at hudson.plugins.global_build_stats.xstream.GlobalBuildStatsXStreamConverter.unmarshal(GlobalBuildStatsXStreamConverter.java:159) at com.thoughtworks.xstream.core.TreeUnmarshaller.convert(TreeUnmarshaller.java:72) at com.thoughtworks.xstream.core.AbstractReferenceUnmarshaller.convert(AbstractReferenceUnmarshaller.java:65) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertAnother(TreeUnmarshaller.java:66) at com.thoughtworks.xstream.core.TreeUnmarshaller.convertA
[JIRA] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Gaston Marengo commented on JENKINS-27100 Regressions in 1.12 and 1.13 Just for your information : Throughput, Responding Time, Percentage of Errors are generated empty. The only one with actual data is the Trend Report 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] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Gaston Marengo edited a comment on JENKINS-27100 Regressions in 1.12 and 1.13 Ok, it's half working now. The graphs are there now but are generated with empty data and the error in the logs are still there : Caused by: java.lang.Error: Unresolved compilation problem: Messages cannot be resolved at hudson.plugins.performance.PerformanceBuildAction.getDisplayName(PerformanceBuildAction.java:47) 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] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Gaston Marengo edited a comment on JENKINS-27100 Regressions in 1.12 and 1.13 I just checked the graphs and only shows the last build info (so no real changes to plot), even I tested a couple so we have actual data to plot. An example : http://tinypic.com/r/pljz9/8 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] [performance-plugin] (JENKINS-27100) Regressions in 1.12 and 1.13
Gaston Marengo commented on JENKINS-27100 Regressions in 1.12 and 1.13 I just checked the graphs and only shows the last build info (so no real changes to plot), even I tested a couple so we have actual data to plot. 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-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Is there a way to check the output of "isClogged()" in a log? Like https://github.com/jenkinsci/jenkins/blob/608517e187cb5bd1566b1c3728a4df0f7ac4dd5c/core/src/main/java/hudson/triggers/SCMTrigger.java#L225 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] [htmlpublisher-plugin] (JENKINS-24057) Jenkins HTML publisher : latest html report not publishing project level when job fails
David Rubio commented on JENKINS-24057 Jenkins HTML publisher : latest html report not publishing project level when job fails Agreed with Andrew Cowlin. That would be a really nice feature to have. 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-plugin] (JENKINS-23301) Cannot connect to Docker using unix protocol
Jesse Glick commented on JENKINS-23301 Cannot connect to Docker using unix protocol Is it now using docker-java and this is solved? 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-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Just saw this in the log. This was in a merge request. We use the Gitlab Merge Request Builder plugin for that. Apr 07, 2015 3:59:42 PM hudson.triggers.Trigger checkTriggers WARNING: org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run() failed for hudson.model.FreeStyleProject@225cf060[myproject] java.lang.NullPointerException at org.jenkinsci.plugins.gitlab.GitlabBuildTrigger.run(GitlabBuildTrigger.java:100) at hudson.triggers.Trigger.checkTriggers(Trigger.java:265) at hudson.triggers.Trigger$Cron.doRun(Trigger.java:214) at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:51) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304) 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:745) 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] [subversion-plugin] (JENKINS-27809) FATAL: Client received SOAP Fault from server: User authentication failed.
Enric Rocabert created JENKINS-27809 FATAL: Client received SOAP Fault from server: User authentication failed. Issue Type: Bug Assignee: Unassigned Components: subversion-plugin Created: 07/Apr/15 2:12 PM Description: Recently the exception below appears in two projects and I don't know why. I supposed it was because of the Subversion plugin I updated it to 2.5 version and worked for a while but it reproduced and then I have downgraded again to 2.4.5 version. The thing is that this exception is reproduced randomly so a pattern of reproduction is not found. FATAL: Client received SOAP Fault from server: User authentication failed. Please see the server log to find more detail regarding exact cause of the failure. com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: User authentication failed. Please see the server log to find more detail regarding exact cause of the failure. at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:124) at com.sun.xml.internal.ws.client.sei.StubHandler.readResponse(StubHandler.java:238) at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:189) at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:276) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:104) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77) at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147) at com.sun.proxy.$Proxy77.getStreams(Unknown Source) at jenkins.plugins.coverity.CIMInstance.getStream(CIMInstance.java:292) at jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:145) at hudson.Launcher.decorateFor(Launcher.java:682) at jenkins.model.Jenkins.createLauncher(Jenkins.java:1323) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:563) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240) Caused by: com.coverity.ces.ws.v6.common.CovRemoteServiceAuthenticationException: Client received an exception from server: User authentication failed. Please see the server log to find more detail regarding exact cause of the failure. at com.coverity.ces.ws.v6.common.ServiceAuthenticationHandlerWSS.handleMessage(ServiceAuthenticationHandlerWSS.java:140) at com.coverity.ces.ws.v6.common.ServiceAuthenticationHandlerWSS.handleMessage(ServiceAuthenticationHandlerWSS.java:58) at com.sun.xml.ws.handler.HandlerProcessor.callHandleMessage(HandlerProcessor.java:284) at com.sun.xml.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:135) at com.sun.xml.ws.handler.ServerSOAPHandlerTube.callHandlersOnRequest(ServerSOAPHandlerTube.java:134) at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:116) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439) at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243) at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:471) at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244) at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135) at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:129) at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:160) at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:641) at javax.
[JIRA] [subversion-plugin] (JENKINS-27809) FATAL: Client received SOAP Fault from server: User authentication failed.
Enric Rocabert
updated JENKINS-27809
FATAL: Client received SOAP Fault from server: User authentication failed.
Change By:
Enric Rocabert
(07/Apr/15 2:15 PM)
Description:
Recently the exception below appears in two projects and I don't know why. I supposed it was because of the Subversion plugin I updated it to 2.5 version and worked for a while but it reproduced again and then I have downgraded the plugin to 2.4.5 version.The thing is that this exception is reproduced randomly so I can't find a pattern of reproduction.
{noformat}FATAL: Client received SOAP Fault from server: User authentication failed. Please see the server log to find more detail regarding exact cause of the failure.com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: User authentication failed. Please see the server log to find more detail regarding exact cause of the failure.at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:124) at com.sun.xml.internal.ws.client.sei.StubHandler.readResponse(StubHandler.java:238) at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:189) at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:276) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:104) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77) at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147) at com.sun.proxy.$Proxy77.getStreams(Unknown Source) at jenkins.plugins.coverity.CIMInstance.getStream(CIMInstance.java:292) at jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:145) at hudson.Launcher.decorateFor(Launcher.java:682) at jenkins.model.Jenkins.createLauncher(Jenkins.java:1323) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:563) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Caused by: com.coverity.ces.ws.v6.common.CovRemoteServiceAuthenticationException: Client received an exception from server: User authentication failed. Please see the server log to find more detail regarding exact cause of the failure. at com.coverity.ces.ws.v6.common.ServiceAuthenticationHandlerWSS.handleMessage(ServiceAuthenticationHandlerWSS.java:140) at com.coverity.ces.ws.v6.common.ServiceAuthenticationHandlerWSS.handleMessage(ServiceAuthenticationHandlerWSS.java:58) at com.sun.xml.ws.handler.HandlerProcessor.callHandleMessage(HandlerProcessor.java:284) at com.sun.xml.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:135) at com.sun.xml.ws.handler.ServerSOAPHandlerTube.callHandlersOnRequest(ServerSOAPHandlerTube.java:134) at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:116) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439) at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243) at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:471) at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244) at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135) at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:129) at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:160) at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:641) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterC
[JIRA] [subversion-plugin] (JENKINS-27809) FATAL: Client received SOAP Fault from server: User authentication failed.
Enric Rocabert
updated JENKINS-27809
FATAL: Client received SOAP Fault from server: User authentication failed.
Change By:
Enric Rocabert
(07/Apr/15 2:14 PM)
Description:
Recently the exception below appears in two projects and I don't know why. I supposed it was because of the Subversion plugin I updated it to 2.5 version and worked for a while but it reproduced
again
and then I have downgraded
again
the plugin
to 2.4.5 version.The thing is that this exception is reproduced randomly so
I can't find
a pattern of reproduction
is not found
.{noformat}FATAL: Client received SOAP Fault from server: User authentication failed. Please see the server log to find more detail regarding exact cause of the failure.com.sun.xml.internal.ws.fault.ServerSOAPFaultException: Client received SOAP Fault from server: User authentication failed. Please see the server log to find more detail regarding exact cause of the failure.at com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:178) at com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFaultBuilder.java:124) at com.sun.xml.internal.ws.client.sei.StubHandler.readResponse(StubHandler.java:238) at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:189) at com.sun.xml.internal.ws.db.DatabindingImpl.deserializeResponse(DatabindingImpl.java:276) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:104) at com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHandler.java:77) at com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:147) at com.sun.proxy.$Proxy77.getStreams(Unknown Source) at jenkins.plugins.coverity.CIMInstance.getStream(CIMInstance.java:292) at jenkins.plugins.coverity.CoverityLauncherDecorator.decorate(CoverityLauncherDecorator.java:145) at hudson.Launcher.decorateFor(Launcher.java:682) at jenkins.model.Jenkins.createLauncher(Jenkins.java:1323) at hudson.model.AbstractBuild$AbstractBuildExecution.createLauncher(AbstractBuild.java:563) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:494) at hudson.model.Run.execute(Run.java:1718) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:89) at hudson.model.Executor.run(Executor.java:240)Caused by: com.coverity.ces.ws.v6.common.CovRemoteServiceAuthenticationException: Client received an exception from server: User authentication failed. Please see the server log to find more detail regarding exact cause of the failure. at com.coverity.ces.ws.v6.common.ServiceAuthenticationHandlerWSS.handleMessage(ServiceAuthenticationHandlerWSS.java:140) at com.coverity.ces.ws.v6.common.ServiceAuthenticationHandlerWSS.handleMessage(ServiceAuthenticationHandlerWSS.java:58) at com.sun.xml.ws.handler.HandlerProcessor.callHandleMessage(HandlerProcessor.java:284) at com.sun.xml.ws.handler.HandlerProcessor.callHandlersRequest(HandlerProcessor.java:135) at com.sun.xml.ws.handler.ServerSOAPHandlerTube.callHandlersOnRequest(ServerSOAPHandlerTube.java:134) at com.sun.xml.ws.handler.HandlerTube.processRequest(HandlerTube.java:116) at com.sun.xml.ws.api.pipe.Fiber.__doRun(Fiber.java:598) at com.sun.xml.ws.api.pipe.Fiber._doRun(Fiber.java:557) at com.sun.xml.ws.api.pipe.Fiber.doRun(Fiber.java:542) at com.sun.xml.ws.api.pipe.Fiber.runSync(Fiber.java:439) at com.sun.xml.ws.server.WSEndpointImpl$2.process(WSEndpointImpl.java:243) at com.sun.xml.ws.transport.http.HttpAdapter$HttpToolkit.handle(HttpAdapter.java:471) at com.sun.xml.ws.transport.http.HttpAdapter.handle(HttpAdapter.java:244) at com.sun.xml.ws.transport.http.servlet.ServletAdapter.handle(ServletAdapter.java:135) at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doGet(WSServletDelegate.java:129) at com.sun.xml.ws.transport.http.servlet.WSServletDelegate.doPost(WSServletDelegate.java:160) at com.sun.xml.ws.transport.http.servlet.WSServlet.doPost(WSServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:641) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catali
[JIRA] [packaging] (JENKINS-27810) attempting to upgrade to 1.608 fails, unable to acquire .war, yet update center connectivity OK
boris ivan created JENKINS-27810 attempting to upgrade to 1.608 fails, unable to acquire .war, yet update center connectivity OK Issue Type: Bug Assignee: Kohsuke Kawaguchi Components: packaging Created: 07/Apr/15 2:26 PM Description: When attempting to upgrade to 1.608 from 1.607, the 'preparation' checks all pass (Checking update center connectivity -> Success). But Jenkins.war = pending, and similarly if I try to update a plugin, they are all pending. Not sure what the problem is, but the fact that the connectivity check to update center passes, yet all subsequent actions fail is concerning. I typically update Jenkins with every new build, and haven't seen this before, and when I noticed that there were changes implemented re: 'packaging' a couple of days ago, the timing seems suspect. Please feel free to transfer this to 'core' if it is truly unrelated to 'packaging'.. Environment: Jenkins 1.607, attempting to upgrade to 1.608. Project: Jenkins Priority: Critical Reporter: boris ivan 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-27262) email is not sent
Alex Earl commented on JENKINS-27262 email is not sent Which mailer plugin are you using? Also, which version of Jenkins did it work on? 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] [cvs-plugin] (JENKINS-25722) CVS update not working (CVS plugin 2.4,2.7) and cvsclient-71-jenkins-11 artifact
Kishore Reddy commented on JENKINS-25722 CVS update not working (CVS plugin 2.4,2.7) and cvsclient-71-jenkins-11 artifact I too faced this issue. Tried running update command with setCleanCopy() to true After deleting a file - file got re created. After modifying the file - .cvsignore and version file(having name of modified file) got created but the file modifications are not reverted back.If i do the same with Tortoise CVS client the changes were reverted. Any idea? 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Thanks Tom. Will keep an eye out for a new release with this fix in and try it out. 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] [subversion-plugin] (JENKINS-27809) FATAL: Client received SOAP Fault from server: User authentication failed.
Enric Rocabert assigned JENKINS-27809 to Unassigned FATAL: Client received SOAP Fault from server: User authentication failed. Change By: Enric Rocabert (07/Apr/15 2:32 PM) Assignee: Enric Rocabert 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] [cvs-plugin] (JENKINS-25722) CVS update not working (CVS plugin 2.4,2.7) and cvsclient-71-jenkins-11 artifact
Kishore Reddy reopened JENKINS-25722 CVS update not working (CVS plugin 2.4,2.7) and cvsclient-71-jenkins-11 artifact Hi Michael, We are having trouble in getting the CVS update worked as expected.It is not reverting the modifications but creating .cvsignore and version files. Am i missing any configuration? Change By: Kishore Reddy (07/Apr/15 2:37 PM) Resolution: Cannot Reproduce Status: Closed 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] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds @Arpit you can get it from the CI server here. 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] [subversion-plugin] (JENKINS-27809) FATAL: Client received SOAP Fault from server: User authentication failed.
Enric Rocabert assigned JENKINS-27809 to Enric Rocabert FATAL: Client received SOAP Fault from server: User authentication failed. Change By: Enric Rocabert (07/Apr/15 2:32 PM) Assignee: Enric Rocabert 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Ah i see. Let me see how i can test this out. I am little hesitant to put a new war in our production instance so will probably setup a test instance where i can play with this release. 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-27262) email is not sent
Ferry Huberts commented on JENKINS-27262 email is not sent mailer = the default Jenkins mailer, currently @ 1.15 which version: (as I said) I don't know. probably a few versions before I filed the bug 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-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds @Arpit for sure ... just download that CI build and test it in a test environment and at least provide some initial feedback. It would be great if we could have a test run against some real data too though so as to test the performance. Do you have a Staging environment where you can test using a clone of some real data? 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Unfortunately not . Have various jenkins masters but they are all production instances. When i mean production they are not externally facing. Its a production instance for our QE group. 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-27262) email is not sent
Alex Earl commented on JENKINS-27262 email is not sent Can you provide a config.xml for the job and a build log? 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-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds @Arpit Can you make a copy of it (or part of it containing an interesting build)? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-27820) Support adding Windows PowerShell build steps
Mark Syms created JENKINS-27820 Support adding Windows PowerShell build steps Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 07/Apr/15 3:41 PM Description: For Windows build slaves it would be good to support PowerShell build steps, these are essentially identical to BatchFile but execute in PowerShell instead of cmd. hudson.plugins.powershell.PowerShell plugin="powershell@1.2"> PowerShell script commands here I have an implementation, a pull request will be following. Environment: Operating System: Windows Project: Jenkins Priority: Minor Reporter: Mark Syms 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Thats a good idea. We are already running backup of jenkins (without the build info) i can use that to set on up and just copy over the builds. Will try to get that running this week. 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-27262) email is not sent
Ferry Huberts commented on JENKINS-27262 email is not sent The xml I can only provide privately. The part relevant to email: "mailer@1.12"> proj_nbsolsrd false false There is nothing special in the build logs. Failed build: Build step 'Execute shell' marked build as failure Archiving artifacts An attempt to send an e-mail to empty list of recipients, ignored. Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: FAILURE Next successful build: Archiving artifacts An attempt to send an e-mail to empty list of recipients, ignored. Started calculate disk usage of build Finished Calculation of disk usage of build in 0 seconds Started calculate disk usage of workspace Finished Calculation of disk usage of workspace in 0 seconds Finished: SUCCESS 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-26445) Browser freezes when clicking more link on a job to see other builds
Tom FENNELLY commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Thanks Arpit. Would it be possible for us to do a screenshare when you are testing so I can see it in action? Skype, Hangouts or whatever would be good. 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-26798) High occurrence of out-sync EC2 slaves
Kevin Cheng commented on JENKINS-26798 High occurrence of out-sync EC2 slaves I am not quite convinced, this "out-of-sync" issue is the same as the Zombie issue. Both issues were reported by me. After applying the v1.27, the great news is that Zombie issue (AWS instance with "no value for name tag" does not have corresponding slave in Jenkins) has been addressed. However, after observing for several days after the upgrade, I still see the out-of-sync situation. 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
Kevin Cheng commented on JENKINS-26797 Zombie instance created by the EC2 plugins Upgraded to v1.27 for 4 days now, I am happy to report that I do not see zombie instances anymore, however, the out-of-sync issue still remains as reported as separate ticket JENKINS-26798 which was marked as dup (as I do not agree they are the same, at least the fix went in did not fix the OOS situation) 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
Christoph Beckmann commented on JENKINS-26797 Zombie instance created by the EC2 plugins @Kevin Cheng Good to hear, we notice the same after ~2 weeks. After fixing this issue I agree JENKINS-26798 is different issue. 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-27821) Docker Build Step Plugin: Unable to correctly install
John Mellor created JENKINS-27821 Docker Build Step Plugin: Unable to correctly install Issue Type: Bug Assignee: vjuranek Components: docker-build-step-plugin Created: 07/Apr/15 5:25 PM Description: Unable to successfully install the docker buildstep plugin - apparent API mismatch. Plugin install log: java.io.IOException: Failed to dynamically deploy this plugin at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1322) at hudson.model.UpdateCenter$DownloadJob.run(UpdateCenter.java:1121) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at hudson.remoting.AtmostOneThreadExecutor$Worker.run(AtmostOneThreadExecutor.java:110) at java.lang.Thread.run(Thread.java:679) Caused by: java.io.IOException: Failed to initialize docker-build-step plugin at hudson.PluginManager.dynamicLoad(PluginManager.java:488) at hudson.model.UpdateCenter$InstallationJob._run(UpdateCenter.java:1318) ... 6 more Caused by: org.jvnet.hudson.reactor.ReactorException: java.lang.Error: java.lang.reflect.InvocationTargetException at org.jvnet.hudson.reactor.Reactor.execute(Reactor.java:269) at jenkins.InitReactorRunner.run(InitReactorRunner.java:44) at hudson.PluginManager.dynamicLoad(PluginManager.java:486) ... 7 more Caused by: java.lang.Error: java.lang.reflect.InvocationTargetException at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:110) at hudson.init.TaskMethodFinder$TaskImpl.run(TaskMethodFinder.java:176) at org.jvnet.hudson.reactor.Reactor.runTask(Reactor.java:282) at org.jvnet.hudson.reactor.Reactor$2.run(Reactor.java:210) at org.jvnet.hudson.reactor.Reactor$Node.run(Reactor.java:117) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) ... 1 more Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:106) ... 7 more Caused by: java.lang.UnsupportedClassVersionError: com/github/dockerjava/api/model/ExposedPort : Unsupported major.minor version 51.0 at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:634) at jenkins.util.AntClassLoader.defineClassFromData(AntClassLoader.java:1138) at hudson.ClassicPluginStrategy$AntClassLoader2.defineClassFromData(ClassicPluginStrategy.java:799) at jenkins.util.AntClassLoader.getClassFromStream(AntClassLoader.java:1309) at jenkins.util.AntClassLoader.findClassInComponents(AntClassLoader.java:1365) at jenkins.util.AntClassLoader.findClass(AntClassLoader.java:1325) at jenkins.util.AntClassLoader.loadClass(AntClassLoader.java:1078) at java.lang.ClassLoader.loadClass(ClassLoader.java:266) at org.jenkinsci.plugins.dockerbuildstep.PluginImpl.addXStreamAliases(PluginImpl.java:19) ... 12 more Environment: Ubuntu 12.04.1, Jenkins 1.607, no out-of-date components Project: Jenkins Labels: plugin exception installation failed Priority: Major Reporter: John Mellor
[JIRA] [core] (JENKINS-27262) email is not sent
Alex Earl commented on JENKINS-27262 email is not sent My guess is that Mailer tries to resolve proj_nbsolsrd to a username, which is can't do and so it replaces it with an empty string. Can you try setting up a user in the Jenkins database with the username proj_nbsolsrd and specify the email address as proj_ngsolsrd and see if that works? 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
arash m commented on JENKINS-26797 Zombie instance created by the EC2 plugins Agreed. This issue is fixed on my side as well. Thank you for the fix. 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] [job-dsl-plugin] (JENKINS-27820) Support adding Windows PowerShell build steps
SCM/JIRA link daemon commented on JENKINS-27820 Support adding Windows PowerShell build steps Code changed in jenkins User: Mark Syms Path: docs/Job-reference.md job-dsl-core/src/main/groovy/javaposse/jobdsl/dsl/helpers/step/StepContext.groovy job-dsl-core/src/test/groovy/javaposse/jobdsl/dsl/helpers/step/StepContextSpec.groovy http://jenkins-ci.org/commit/job-dsl-plugin/ef79f2970dd0ea59bce2a820d431e5efa5f57944 Log: Add support for PowerShell build step in response to JENKINS-27820 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] [job-dsl-plugin] (JENKINS-27820) Support adding Windows PowerShell build steps
Daniel Spilker resolved JENKINS-27820 as Fixed Support adding Windows PowerShell build steps Will be released in 1.32. Change By: Daniel Spilker (07/Apr/15 5:59 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] [core] (JENKINS-27822) cant download any jenkins package from http://pkg.jenkins-ci.org/redhat/
Arpit Gupta created JENKINS-27822 cant download any jenkins package from http://pkg.jenkins-ci.org/redhat/ Issue Type: Bug Assignee: Unassigned Components: core Created: 07/Apr/15 6:07 PM Description: Tried to setup a new jenkins and get a 404 http://pkg.jenkins-ci.org/redhat/jenkins-1.608-1.1.noarch.rpm: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404 Not Found" Trying other mirror. Error Downloading Packages: jenkins-1.608-1.1.noarch: failure: jenkins-1.608-1.1.noarch.rpm from jenkins: [Errno 256] No more mirrors to try. Even through the UI these packages get a 404. Tried a few Project: Jenkins Priority: Blocker Reporter: Arpit Gupta 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Once i have it setup will update the jira with the details. BTW new downloads of jenkins are failing. Logged JENKINS-27822 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] [job-dsl-plugin] (JENKINS-27767) No such property: jobManagement for class:
SCM/JIRA link daemon commented on JENKINS-27767 No such property: jobManagement for class: Code changed in jenkins User: Daniel Spilker Path: docs/Home.md http://jenkins-ci.org/commit/job-dsl-plugin/b57a379b468d434bad5460a3f3e50151bb8957e7 Log: added release notes for JENKINS-27767 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] [scm-sync-configuration-plugin] (JENKINS-24686) scm-sync-configuration fails if job name contains whitespace
Jens Brejner commented on JENKINS-24686 scm-sync-configuration fails if job name contains whitespace Not a solution, but I worked around by disabling the scm-sync repository, then renamed my jobs so spaces where replace with non-whitespace. After that, I reenabled the scm-sync repository 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Ok i have the instance setup. @Tom what time zone are you in? We can figure out a time works for both. Here is my feedback most of its nice to have as i would use this as is. (Have not tried running builds yet to see how this works with that). Love the search feature and works like a charm. 1. Does it make sense to have pagination links available at the top and bottom and with numbers like page 1 of x and total build count displayed and available etc. Do not know what is best way to display it but feel like having that info is useful 2. Does it make sense to show running builds in its own module and completed builds in its own? We can use the search feature also. As i have seen cases where we have had x builds run and are shown and a running build will be on a different page. We can easily just search for it but thought i would bring it up. Since its not a regression from earlier behavior i can log a different jira. 3. Adding some validation when the user does not provide the expected search format will be good to have. All in all this is great. Now when can i get it in the released artifact . 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta edited a comment on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Ok i have the instance setup. @Tom what time zone are you in? We can figure out a time that works for both. Here is my feedback most of its nice to have as i would use this as is. (Have not tried running builds yet to see how this works with that). Love the search feature and works like a charm. 1. Does it make sense to have pagination links available at the top and bottom and with numbers like page 1 of x and total build count displayed and available etc. Do not know what is best way to display it but feel like having that info is useful 2. Does it make sense to show running builds in its own module and completed builds in its own? We can use the search feature also. As i have seen cases where we have had x builds run and are shown and a running build will be on a different page. We can easily just search for it but thought i would bring it up. Since its not a regression from earlier behavior i can log a different jira. 3. Adding some validation when the user does not provide the expected search format will be good to have. All in all this is great. Now when can i get it in the released artifact . 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta edited a comment on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Once i have it setup will update the jira with the details. BTW new downloads of jenkins are failing. Logged INFRA-270 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] [veracode-scanner-plugin] (JENKINS-27823) error while Configuring a Jenkins Job for Veracode Analysis
kineret amor
created JENKINS-27823
error while Configuring a Jenkins Job for Veracode Analysis
Issue Type:
Bug
Assignee:
Mike Bockus
Components:
veracode-scanner-plugin
Created:
07/Apr/15 7:02 PM
Description:
Hey ,
i want to configure a Jenkins Job for Veracode Analysis
and i get error :
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class com.veracode.jenkins.plugin.VeracodeNotifier from {"appname":"HgBpbe/yHpIRMZ7PINv05K+nVUFm9Ibz3z4VWE1UwrM=","createprofile":true,"criticality":"EyfMO+rq6E+xW66bF+ATElZqV96tr36ltWm1DFSfZ1Q=","sandboxname":"r6dVQWb0hvPfPhVYTVTCsw==","createsandbox":false,"version":"emw4tq5QUPrFKrnBzlgyJiIhypRFRgvRqozr1cAIPJo=","uploadincludespattern":"bDDj/V3GHLT8UbeMoISTYLcbo+yPWQY6PJWMaom8VLA=","uploadexcludespattern":"r6dVQWb0hvPfPhVYTVTCsw==","scanincludespattern":"r6dVQWb0hvPfPhVYTVTCsw==","scanexcludespattern":"r6dVQWb0hvPfPhVYTVTCsw==","filenamepattern":"PGaSiDnCGlAQeUJAOtD3ka+nVUFm9Ibz3z4VWE1UwrM=","replacementpattern":"j0awvuMa5UvPW8Zl78snddYIkdPxiXqG6umKs27fcMJ3FkW1fiOi+z76PDlOW5VO","credentials":{"vuser":"CCX2RD+bn1Dd0JhwSapj+FePR5gurmHqCtiTsawx0xcdDKPT7MWdRL+xTGPQfgt9","vpassword":"tD684Mcd7F9C6XPEkllLZB0Mo9PsxZ1Ev7FMY9B+C30="},"stapler-class":"com.veracode.jenkins.plugin.VeracodeNotifier","kind":"com.veracode.jenkins.plugin.VeracodeNotifier","$class":"vvhrZXx9/XAtMIZ89EIg7ucGQfVOYuljjvwB+X5HHnNghkYPMCSg85kie6zfQz6GES2ygN6+Bh7AOizeO3AwCA=="}
at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
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:746)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876)
at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649)
at org.kohsuke.stapler.Stapler.service(Stapler.java:238)
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:123)
at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58)
at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120)
at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84)
at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76)
at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:164)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482)
at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30)
at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474)
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499)
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533)
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428)
at org.eclipse.
[JIRA] [job-dsl-plugin] (JENKINS-27767) No such property: jobManagement for class:
Daniel Spilker closed JENKINS-27767 as Fixed No such property: jobManagement for class: Change By: Daniel Spilker (07/Apr/15 7:05 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] [job-dsl-plugin] (JENKINS-27820) Support adding Windows PowerShell build steps
Daniel Spilker closed JENKINS-27820 as Fixed Support adding Windows PowerShell build steps Change By: Daniel Spilker (07/Apr/15 7:05 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] [core] (JENKINS-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Oh and here is another 4. Allow the user to define how many builds per page. Ideally defaults defined at jenkins config level and allow override at job level. The defaults can be what the defaults are today. 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-27262) email is not sent
Ferry Huberts commented on JENKINS-27262 email is not sent I really don't want to do that for real. I can try it for a test but not as a solution. Tomorrow I can try. Mailer shouldn't ever try to resolve the name, the MTA will return an error when the name is not valid, it's not Jenkins' business to try to do the MTA's work. As I said, proj_xxx is a valid alias on the MTA, the MTA can resolve it just fine. 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] [description-setter-plugin] (JENKINS-27824) Build Descriptions containing are no longer rendered correctly on project page (but are renedered correctly on build page)
M Chon created JENKINS-27824 Build Descriptions containing are no longer rendered correctly on project page (but are renedered correctly on build page) Issue Type: Bug Assignee: huybrechts Attachments: multi-line.PNG, single-line.PNG Components: description-setter-plugin Created: 07/Apr/15 7:27 PM Description: We make extensive use of multi-line build descriptions. E.g. inside one of our projects, we might have something like: echo "BUILD DESCRIPTION IS Branch: $GIT_BRANCH$FOOBAR_DESCRIBEPRODUCTION: $PRODUCTION" Then, in the Set Build description area, for Regular _expression_ we have: BUILD DESCRIPTION IS (.*) On the Build page for any individual build, this will correctly be rendered as, for example: Branch: refs/remotes/origin/grunt-copy-production v3.3.1-20-g7494bddb PRODUCTION: true But on the Project Page, where the builds are listed, the are no longer rendered. See attached screen shots. This is true of the new (black) Jenkins UI. In the old (blue) Jenkins UI, the would cause the multi-line description to be rendered on multiple lines. Environment: Jenkins 1.596.1, description-setter 1.9 Project: Jenkins Priority: Minor Reporter: M Chon 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-27821) Docker Build Step Plugin: Unable to correctly install
Daniel Beck commented on JENKINS-27821 Docker Build Step Plugin: Unable to correctly install It looks like the Docker-Java library requires Java 7 to run. 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] [description-setter-plugin] (JENKINS-27824) Build Descriptions containing are no longer rendered correctly on project page (but are renedered correctly on build page)
M Chon commented on JENKINS-27824 Build Descriptions containing are no longer rendered correctly on project page (but are renedered correctly on build page) Others may be affected: http://jenkins-ci.361315.n4.nabble.com/setting-multi-line-build-desc-using-Set-build-description-plugin-td3927685.html 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] [zentimestamp-plugin] (JENKINS-26626) Zentimestamp plugin no longer compatible with Jenkins 1.597
Steven Christou resolved JENKINS-26626 as Fixed Zentimestamp plugin no longer compatible with Jenkins 1.597 The PR was merged, so I am marking as fixed. The Zentimestamp plugin will use the `BUILD_TIMESTAMP` environment variable instead of the `BUILD_ID`. Change By: Steven Christou (07/Apr/15 7:36 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] [packaging] (JENKINS-27810) attempting to upgrade to 1.608 fails, unable to acquire .war, yet update center connectivity OK
Daniel Beck resolved JENKINS-27810 as Duplicate attempting to upgrade to 1.608 fails, unable to acquire .war, yet update center connectivity OK Duplicates INFRA-270. Change By: Daniel Beck (07/Apr/15 7:36 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-26445) Browser freezes when clicking more link on a job to see other builds
Daniel Beck commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds 4. Allow the user to define how many builds per page. Ideally defaults defined at jenkins config level and allow override at job level. The defaults can be what the defaults are today. Should probably be postponed until it works well and we see whether there's an actual need for this. I cannot remember anybody requesting a different number of builds shown by default for the current UI, so my guess is this is not really necessary. 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-26445) Browser freezes when clicking more link on a job to see other builds
Arpit Gupta commented on JENKINS-26445 Browser freezes when clicking more link on a job to see other builds Makes sense. I would say all my points except for #3 probably can be done as improvements based on larger feedback. Even #3 is not that big a deal. 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] [script-security-plugin] (JENKINS-27307) Unclassified methods in sandboxed mode
Jesse Glick resolved JENKINS-27307 as Duplicate Unclassified methods in sandboxed mode More convenient to handle them together, since they probably reflect the same underlying bug. Change By: Jesse Glick (07/Apr/15 8:09 PM) Status: Reopened Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- 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-27747) workflow plugin snippet generator does not display git additional behaviors
Jesse Glick resolved JENKINS-27747 as Not A Defect workflow plugin snippet generator does not display git additional behaviors There was a reply on Feb 18. The git step is very simple and does not support those options. The checkout step with GitSCM does support them; Snippet Generator support for that was broken initially but fixed in 1.4. Change By: Jesse Glick (07/Apr/15 8:08 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] [docker-build-step-plugin] (JENKINS-27821) Docker Build Step Plugin: Unable to correctly install
vjuranek resolved JENKINS-27821 as Fixed Docker Build Step Plugin: Unable to correctly install yes, docker-java library is built for JDK7. I released 1.22 with docker-java rebuilt with JDK6, but as it's a 3rd party dependency, I'm not going to fix and rebuilt it every time (and hardly to push it into docker-java upstream as JDK6 is 2 year EOL), so this is probably the only release with JDK6 support. Change By: vjuranek (07/Apr/15 8:21 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] [core] (JENKINS-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
SCM/JIRA link daemon commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value Code changed in jenkins User: Jesse Glick Path: core/src/main/resources/jenkins/model/CoreEnvironmentContributor/buildEnv.properties http://jenkins-ci.org/commit/jenkins/77327a5e37a10244f4ad2bc23988b96982caf200 Log: JENKINS-26520 Documentation for $BUILD_ID did not reflect current reality. 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-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
SCM/JIRA link daemon commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value Code changed in jenkins User: Jesse Glick Path: core/src/main/resources/jenkins/model/CoreEnvironmentContributor/buildEnv.properties http://jenkins-ci.org/commit/jenkins/e80c69c433a4b90e18af234c154eec44803cafd1 Log: Merge pull request #1637 from jglick/BUILD_ID-JENKINS-26520 JENKINS-26520 Documentation fix for $BUILD_ID Compare: https://github.com/jenkinsci/jenkins/compare/c2e9423b95cb...e80c69c433a4 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-27262) email is not sent
Alex Earl commented on JENKINS-27262 email is not sent It ALWAYS tries to resolve the address. You can claim its not Jenkins' job to do that, but its a feature that is heavily used by many people. It's not something that is going to be removed. 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] [zentimestamp-plugin] (JENKINS-26626) Zentimestamp plugin no longer compatible with Jenkins 1.597
Steven Christou assigned JENKINS-26626 to Steven Christou Zentimestamp plugin no longer compatible with Jenkins 1.597 Change By: Steven Christou (07/Apr/15 8:38 PM) Assignee: Gregory Boissinot Steven Christou 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-27262) email is not sent
Ferry Huberts commented on JENKINS-27262 email is not sent then it should just assume entries that it can't resolve to be valid. removing such entries really is a mistake 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-26520) Environment Variables BUILD_ID and BUILD_NUMBER now return the same value
Steven Christou commented on JENKINS-26520 Environment Variables BUILD_ID and BUILD_NUMBER now return the same value Poulet Fabrice and others, PR 1 in the Zentimestamp plugin now uses BUILD_TIMESTAMP as an environment variable instead of the BUILD_ID. 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-27825) Can Jenkins invoke Cigital SecureAssist reports?
Jeremy Rojas created JENKINS-27825 Can Jenkins invoke Cigital SecureAssist reports? Issue Type: New Feature Assignee: Unassigned Components: core Created: 07/Apr/15 9:00 PM Description: Cigital SecureAssist is a plugin that can generate reports that point out security vulnerabilities. Does Jenkins have the ability to invoke these reports? I could not find any information on this online. thanks in advanced. Project: Jenkins Priority: Minor Reporter: Jeremy Rojas 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-27825) Can Jenkins invoke Cigital SecureAssist reports?
Daniel Beck resolved JENKINS-27825 as Not A Defect Can Jenkins invoke Cigital SecureAssist reports? This is an issue tracker, not a support site. Change By: Daniel Beck (07/Apr/15 9:23 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] [core] (JENKINS-27262) email is not sent
Alex Earl commented on JENKINS-27262 email is not sent Its just a theory, i don't know for sure. I don't maintain mailer, just trying to help out. 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] [buildtriggerbadge-plugin] (JENKINS-26186) Last Build Trigger Column does not print author name
J John commented on JENKINS-26186 Last Build Trigger Column does not print author name Awesome. So, we can look forward to a global and local configuration for the column behavior? 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] [sauce-ondemand-plugin] (JENKINS-27111) Sauce Connect intermittently fails to launch
Michael Merritt resolved JENKINS-27111 as Fixed Sauce Connect intermittently fails to launch This appears to be resolved with Sauce Connect 4.3.8 Will continue to test and re-open if we see it again. Thanks for your help Ross. Change By: Michael Merritt (07/Apr/15 11:13 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] [core] (JENKINS-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Ben Hines commented on JENKINS-27223 Clicking Login when you have 30+ slaves defaults you to the bottom of the web page We have hundreds of slaves, and this is super annoying. 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-27223) Clicking Login when you have 30+ slaves defaults you to the bottom of the web page
Daniel Beck commented on JENKINS-27223 Clicking Login when you have 30+ slaves defaults you to the bottom of the web page You should be able to scroll to the top by pressing the Home key. 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] [packaging] (JENKINS-27776) Packaging doesn't work, 1.608 release is incomplete
Kohsuke Kawaguchi resolved JENKINS-27776 as Fixed Packaging doesn't work, 1.608 release is incomplete I've fixed this in reaction to INFRA-270 Change By: Kohsuke Kawaguchi (08/Apr/15 12:08 AM) 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] [description-setter-plugin] (JENKINS-27824) Build Descriptions containing are no longer rendered correctly on project page (but are renedered correctly on build page)
Daniel Beck commented on JENKINS-27824 Build Descriptions containing are no longer rendered correctly on project page (but are renedered correctly on build page) Is this specific to Description Setter Plugin, or does it affect manually set build descriptions as well? What markup formatter is selected in the global security options? 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] [tfs-plugin] (JENKINS-23033) TFS Password visible in view source
Olivier Dagenais updated JENKINS-23033 TFS Password visible in view source Change By: Olivier Dagenais (08/Apr/15 12:35 AM) Labels: password security Assignee: redsolo Olivier Dagenais 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] [label-linked-jobs-plugin] (JENKINS-27588) Labels used in Label Factory are shown as not used
Dominique Brice updated JENKINS-27588 Labels used in Label Factory are shown as not used Change By: Dominique Brice (08/Apr/15 12:36 AM) Attachment: DashboardLabels.png Attachment: DashboardOrphanedSingleNode.png Attachment: LabelStatus.png 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] [tfs-plugin] (JENKINS-23344) TFS plugin does not create label as trigger value is not saved in config
Olivier Dagenais assigned JENKINS-23344 to Olivier Dagenais TFS plugin does not create label as trigger value is not saved in config Change By: Olivier Dagenais (08/Apr/15 12:36 AM) Assignee: redsolo Olivier Dagenais 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.
