[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
nickithewatt updated JENKINS-16499 NPE when new job by copy from existing one Change By: nickithewatt (02/Feb/13 8:41 AM) Priority: Major Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
nickithewatt commented on JENKINS-16499 NPE when new job by copy from existing one I confirm that this appears to be a problem regardless of which plugins are installed. The core needs fixing. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16609) Backup buuild results/artifacts only for Keep this build forever marked builds
Thomas Fürer created JENKINS-16609 Backup buuild results/artifacts only for Keep this build forever marked builds Issue Type: Improvement Assignee: Thomas Fürer Components: thinBackup Created: 02/Feb/13 9:07 AM Description: original ask by rjnichols and finally also implemented by himself Project: Jenkins Priority: Major Reporter: Thomas Fürer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16609) Backup build results/artifacts only for Keep this build forever marked builds
Thomas Fürer updated JENKINS-16609 Backup build results/artifacts only for Keep this build forever marked builds Change By: Thomas Fürer (02/Feb/13 9:08 AM) Summary: Backup buuild build results/artifactsonlyforKeepthisbuildforevermarkedbuilds Description: original ask asked byrjnicholsandfinallyalsoimplementedbyhimself This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16609) Backup build results/artifacts only for Keep this build forever marked builds
SCM/JIRA link daemon commented on JENKINS-16609 Backup build results/artifacts only for Keep this build forever marked builds Code changed in jenkins User: Thomas Fuerer Path: src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink.java src/main/java/org/jvnet/hudson/plugins/thinbackup/ThinBackupPluginImpl.java src/main/java/org/jvnet/hudson/plugins/thinbackup/backup/HudsonBackup.java src/main/resources/org/jvnet/hudson/plugins/thinbackup/ThinBackupMgmtLink/backupsettings.jelly src/main/webapp/help/help-backupBuildToKeepOnly.html src/test/java/org/jvnet/hudson/plugins/thinbackup/backup/TestBackupMatrixJob.java src/test/java/org/jvnet/hudson/plugins/thinbackup/backup/TestBackupWithCloudBeesFolder.java src/test/java/org/jvnet/hudson/plugins/thinbackup/backup/TestHudsonBackup.java http://jenkins-ci.org/commit/thin-backup-plugin/7bc0dc254f0b2dccf1ce3bac1fe80c98fce75e96 Log: Merge pull request #2 from rjnichols/master JENKINS-16609: New feature - only back up build results/artifacts on builds which are marked "Keep this build forever" Compare: https://github.com/jenkinsci/thin-backup-plugin/compare/9b940cb5daba...7bc0dc254f0b You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
[JIRA] (JENKINS-16609) Backup build results/artifacts only for Keep this build forever marked builds
Thomas Fürer resolved JENKINS-16609 as Fixed Backup build results/artifacts only for Keep this build forever marked builds Change By: Thomas Fürer (02/Feb/13 9:11 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/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
kutzi assigned JENKINS-16499 to kutzi NPE when new job by copy from existing one Change By: kutzi (02/Feb/13 9:18 AM) Assignee: kutzi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
kutzi commented on JENKINS-16499 NPE when new job by copy from existing one Using the steps mentioned in the 1st comment results in a different stack trace, but still a NPE: javax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:598) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1367) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338) 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:1338) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:50) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1338) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:484) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:119) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:499) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1065) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:413) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:192) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:999) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117) at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:250) at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:149) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:111) at org.eclipse.jetty.server.Server.handle(Server.java:350) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:454) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:900) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:954) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:851) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:77) at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:620) at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:46) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:603) at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:538) at java.lang.Thread.run(Thread.java:662) Caused by: java.lang.NullPointerException at hudson.model.AbstractProject.getLastBuild(AbstractProject.java:1021) at hudson.maven.AbstractMavenProject.createTransientActions(AbstractMavenProject.java:184) at hudson.maven.MavenModuleSet.createTransientActions(MavenModuleSet.java:448) at hudson.model.AbstractProject.updateTransientActions(AbstractProject.java:688) at
[JIRA] (JENKINS-14112) The execution (build) of Project will fail on mkdir on remote disk.
Sami Tikka commented on JENKINS-14112 The execution (build) of Project will fail on mkdir on remote disk. Have you read https://wiki.jenkins-ci.org/display/JENKINS/My+software+builds+on+my+computer+but+not+on+Jenkins ? My understanding is that drive mappings done by the logged-in user are not necessarily available for the Jenkins user. I think you have two possibilities: Run Jenkins in CMD window in your logged-in user session or Use something like https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep to set up network drives so they exist before checkout happens. Still, I fail to see why this is a Jenkins bug. Maybe a Jenkins feature request but also I haven't yet seen what the feature would be. Maybe more clarification is needed? (By the way, personally I would always try to check out and build code on local disk. Network disk can rarely offer comparable performance to local disk and build speed is essential for continuous integration.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
kutzi assigned JENKINS-16499 to Kohsuke Kawaguchi NPE when new job by copy from existing one AbstractProject#onLoad calls super#onLoad which in turn calls AbstractProject#save which (in the maven case) tries to access the not-yet-initialized 'builds' RunMap. This pattern of doing stuff on incompletely initialized objects is IMO highly fragile and bound to create all sort of problems. However, I've got no clue how to fix that now, so assigning to Kohsuke. Change By: kutzi (02/Feb/13 10:07 AM) Assignee: kutzi KohsukeKawaguchi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
SCM/JIRA link daemon commented on JENKINS-16499 NPE when new job by copy from existing one Code changed in jenkins User: Christoph Kutzinski Path: test/src/test/java/hudson/maven/MavenProjectTest.java http://jenkins-ci.org/commit/jenkins/7d422e60d9b3b2c678e6baf066e0780a29b027aa Log: Added testcase for JENKINS-16499 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
[JIRA] (JENKINS-16610) Unable to use variables for polling SCM Cron when using template workflow plugin
nickithewatt created JENKINS-16610 Unable to use variables for polling SCM Cron when using template workflow plugin Issue Type: Improvement Assignee: Unassigned Attachments: polling-scm-issue.JPG Components: core Created: 02/Feb/13 10:25 AM Description: I am current making use of the template workflow plugin which quite nicely allows you to define a workflow out a set of template jobs and then have specific instances of these workflows and new jobs created based on the template. The plugin allows you to mark a job as a "template job". Within this template job, in order to provide for template based variable substitution, it expects you to specify variables in the form of @@VAR_NAME@@, which when the plugin runs, will substitute these values for specific values defined for each workflow instance. The issue is that this works fine for most areas where @@VAR_NAME@@ type variables are defined, for example in the "description" and even in the "Repository URL" field for subversion. Although a red UI error message is displayed, you are still able to save the template. Unfortunately when trying to use the @@VAR_NAME@@ format in the Polling SCM field, an exception is thrown upon saving and the template cannot be saved. The exception is as follows Status Code: 500 Exception: java.lang.RuntimeException: Failed to instantiate class hudson.triggers.SCMTrigger from {"ignorePostCommitHooks":false,"scmpoll_spec":"@@J_SCM_POLLING_CRON@@"} Stacktrace: javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class hudson.triggers.SCMTrigger from {"ignorePostCommitHooks":false,"scmpoll_spec":"@@J_SCM_POLLING_CRON@@"} at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:615) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:241) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:573) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:658) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:487) at org.kohsuke.stapler.Stapler.service(Stapler.java:164) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:206) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:179) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:84) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:98) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:87) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:47) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:166) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-12174) GUI misses failed builds
evernat commented on JENKINS-12174 GUI misses failed builds Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10777) On M2 job, with only one sudmodule built, link to maven site failed with 404 message.
evernat commented on JENKINS-10777 On M2 job, with only one sudmodule built, link to maven site failed with 404 message. Is it reproduced with a recent Jenkins version? If yes, can you upload a zip file of the project to reproduce it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
dogfood commented on JENKINS-16499 NPE when new job by copy from existing one Integrated in jenkins_main_trunk #2237 Added testcase for JENKINS-16499 (Revision 7d422e60d9b3b2c678e6baf066e0780a29b027aa) Result = UNSTABLE Christoph Kutzinski : 7d422e60d9b3b2c678e6baf066e0780a29b027aa Files : test/src/test/java/hudson/maven/MavenProjectTest.java This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7669) Hudson executes multiple Builds the same time
evernat commented on JENKINS-7669 Hudson executes multiple Builds the same time Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10446) Cannot save a job in Jenkins
evernat commented on JENKINS-10446 Cannot save a job in Jenkins Is it still an issue? Or can we close it? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10539) windows path separators not correctly escaped in Maven properties configuration
evernat updated JENKINS-10539 windows path separators not correctly escaped in Maven properties configuration Change By: evernat (02/Feb/13 11:23 AM) Assignee: olamy This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16610) Unable to use variables for polling SCM Cron when using template workflow plugin
nickithewatt updated JENKINS-16610 Unable to use variables for polling SCM Cron when using template workflow plugin Change By: nickithewatt (02/Feb/13 11:25 AM) Attachment: polling-scm-issue.JPG This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10539) windows path separators not correctly escaped in Maven properties configuration
evernat commented on JENKINS-10539 windows path separators not correctly escaped in Maven properties configuration Hi Olivier, (or should we say Oliver now?) What do you think of this old issue on builds.apache.org? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10302) Incorrect Downstream Projects for Maven 3 multi-module Project
evernat commented on JENKINS-10302 Incorrect Downstream Projects for Maven 3 multi-module Project @Scott Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10376) When running Windows JNLP slaves, all of my remote builds fail with java.lang.IllegalArgumentException: Unable to locate class file for class hudson.remoting.Launcher
evernat commented on JENKINS-10376 When running Windows JNLP slaves, all of my remote builds fail with java.lang.IllegalArgumentException: Unable to locate class file for class hudson.remoting.Launcher Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10413) Add the item number in queue API
evernat resolved JENKINS-10413 as Duplicate Add the item number in queue API Change By: evernat (02/Feb/13 11:56 AM) 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/groups/opt_out.
[JIRA] (JENKINS-6354) test history graphs can be generated without any y labels, providing minimal meaning
evernat commented on JENKINS-6354 test history graphs can be generated without any y labels, providing minimal meaning reproduced with Jenkins v1.500 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-6842) Tooltips not updated in history graph of test results
evernat commented on JENKINS-6842 Tooltips not updated in history graph of test results reproduced with Jenkins 1.500 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8818) PMD results history grap wipedout on build failure
evernat assigned JENKINS-8818 to Ulli Hafner PMD results history grap wipedout on build failure Change By: evernat (02/Feb/13 12:35 PM) Assignee: UlliHafner This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8818) PMD results history grap wipedout on build failure
evernat commented on JENKINS-8818 PMD results history grap wipedout on build failure Is it reproduced with recent versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9824) Incorrect character encoding in subversion output
evernat commented on JENKINS-9824 Incorrect character encoding in subversion output Is it reproduced with recent versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9816) Emulate clean checkout deletes versioned files if more than one module is checked out
evernat commented on JENKINS-9816 Emulate clean checkout deletes versioned files if more than one module is checked out And is it reproduced with recent versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9746) Failed to retrieve Subversion credentials
evernat commented on JENKINS-9746 Failed to retrieve Subversion credentials Is it reproduced with recent versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9754) Poll SCM with too few values - Exception
evernat commented on JENKINS-9754 Poll SCM with too few values - Exception reproduced with jenkins 1.500 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9275) execute shell: javax.servlet.ServletException: This page expects a form submission
evernat commented on JENKINS-9275 execute shell: javax.servlet.ServletException: This page expects a form submission Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9717) Main build finished but it appears jenkins still thinks the module is still running
evernat resolved JENKINS-9717 as Duplicate Main build finished but it appears jenkins still thinks the module is still running Change By: evernat (02/Feb/13 1:13 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/groups/opt_out.
[JIRA] (JENKINS-9660) SVNCancelException: svn: authentication cancelled
evernat commented on JENKINS-9660 SVNCancelException: svn: authentication cancelled Is it reproduced with recent versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9680) http://jenkins.example.com/job/example/build/api/json hits http 302 redirect loop.
evernat commented on JENKINS-9680 http://jenkins.example.com/job/example/build/api/json hits http 302 redirect loop. Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9640) Slave Squatter Plugin prevents safe restart of Jenkins
evernat updated JENKINS-9640 Slave Squatter Plugin prevents safe restart of Jenkins Change By: evernat (02/Feb/13 1:21 PM) Component/s: slave-squatter Component/s: plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9015) latest-link for plugins are broken
evernat resolved JENKINS-9015 as Not A Defect latest-link for plugins are broken I do not think that this is a defect. This works: http://updates.jenkins-ci.org/latest/perfpublisher.hpi from http://updates.jenkins-ci.org/download/plugins/perfpublisher/ Better yet, this works: http://mirrors.jenkins-ci.org/plugins/perfpublisher/latest/perfpublisher.hpi Change By: evernat (02/Feb/13 1:30 PM) Status: InProgress Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9451) Connection reset - windows slave exits from time to time
evernat commented on JENKINS-9451 Connection reset - windows slave exits from time to time Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9452) Jenkins 1.408 doesn't execute build, when it is a shell script, but claims to be successful
evernat commented on JENKINS-9452 Jenkins 1.408 doesnt execute build, when it is a shell script, but claims to be successful Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9234) Unable to change project name
evernat commented on JENKINS-9234 Unable to change project name Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9276) Often jenkings returns 324 (net::ERR_EMPTY_RESPONSE) instead of the project page being requested, refreshing
evernat commented on JENKINS-9276 Often jenkings returns 324 (net::ERR_EMPTY_RESPONSE) instead of the project page being requested, refreshing Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9081) revision history feature consumes large amount of heap
evernat commented on JENKINS-9081 revision history feature consumes large amount of heap It it probably better now with the recent lazy-loading of builds. Is this still an issue for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9349) Viewing large console logs with timestamper plugin cause Jenkins to crash
stevengbrown closed JENKINS-9349 as Fixed Viewing large console logs with timestamper plugin cause Jenkins to crash Change By: stevengbrown (02/Feb/13 2:23 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/groups/opt_out.
[JIRA] (JENKINS-14932) Compact encoding for timestamps, alternative to console note encoding
stevengbrown closed JENKINS-14932 as Fixed Compact encoding for timestamps, alternative to console note encoding Change By: stevengbrown (02/Feb/13 2:26 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/groups/opt_out.
[JIRA] (JENKINS-14931) Allow the elapsed time (since the build started) to be displayed
stevengbrown closed JENKINS-14931 as Fixed Allow the elapsed time (since the build started) to be displayed Change By: stevengbrown (02/Feb/13 2:25 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/groups/opt_out.
[JIRA] (JENKINS-9137) Add option to prevent timestamp from being highlighted in console log
stevengbrown closed JENKINS-9137 as Fixed Add option to prevent timestamp from being highlighted in console log Change By: stevengbrown (02/Feb/13 2:28 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/groups/opt_out.
[JIRA] (JENKINS-16053) Timestamper conflict with AnsiColor plugin
stevengbrown closed JENKINS-16053 as Fixed Timestamper conflict with AnsiColor plugin Change By: stevengbrown (02/Feb/13 2:27 PM) Status: Resolved Closed Assignee: Pei-TangHuang stevengbrown This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16611) Release plugin not compatible with MultiJob plugin
Florian Herbel created JENKINS-16611 Release plugin not compatible with MultiJob plugin Issue Type: Bug Assignee: Peter Hayes Components: release Created: 02/Feb/13 5:06 PM Description: A MultiJob cannot be configured as release build. As the MultiJob-Plugin enables you to easily set up builds with sub-jobs that are executed in parallel it would be great to be able to use the release plugin with it. https://wiki.jenkins-ci.org/display/JENKINS/Multijob+Plugin Project: Jenkins Priority: Major Reporter: Florian Herbel This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-10539) windows path separators not correctly escaped in Maven properties configuration
olamy commented on JENKINS-10539 windows path separators not correctly escaped in Maven properties configuration oh good ping. I didn't test that again on last jenkins version. I will try This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
SCM/JIRA link daemon commented on JENKINS-16499 NPE when new job by copy from existing one Code changed in jenkins User: Christoph Kutzinski Path: core/src/main/java/hudson/model/Job.java http://jenkins-ci.org/commit/jenkins/12efbc3a9bbcd613dc1e4391283b6839cc79990a Log: FIXED JENKINS-16499 Assuming that: save() is not strictly necessary here. config.xml might be saved later or not - doesn't really matter this else branch should only be entered when migrating from very old Hudson instances This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
SCM/JIRA link daemon resolved JENKINS-16499 as Fixed NPE when new job by copy from existing one Change By: SCM/JIRA link daemon (02/Feb/13 5:29 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/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
SCM/JIRA link daemon commented on JENKINS-16499 NPE when new job by copy from existing one Code changed in jenkins User: Christoph Kutzinski Path: changelog.html test/src/test/java/hudson/maven/MavenProjectTest.java http://jenkins-ci.org/commit/jenkins/432c63d9851cadb7e93a110a9a22716b0e033d87 Log: Changelog and fixed test for JENKINS-16499 Compare: https://github.com/jenkinsci/jenkins/compare/7d422e60d9b3...432c63d9851c You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
kutzi commented on JENKINS-16499 NPE when new job by copy from existing one Found now a simple fix for it. However Kohsuke might still have a look on it, as I'm not 101% sure that this won't cause any regression. Also you might want to find out, why this else-branch in Job#onLoad is entered after all. According to the comment that should only happen when migrating old instances. However, it looks like the nextBuildNumber file is not created directly after creating a job. Maybe that should be fixed as the root cause. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13165) Cloning workspace loses hidden files/directories
Dave Hunt resolved JENKINS-13165 as Duplicate Cloning workspace loses hidden files/directories Please correct me if I'm wrong, but I believe this was fixed by JENKINS-13888 Change By: Dave Hunt (02/Feb/13 5:44 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/groups/opt_out.
[JIRA] (JENKINS-16586) Cannot copy existing job when creating a new job (jenkins 1.500)
kutzi resolved JENKINS-16586 as Duplicate Cannot copy existing job when creating a new job (jenkins 1.500) Change By: kutzi (02/Feb/13 5:53 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/groups/opt_out.
[JIRA] (JENKINS-8853) don't try to include all of history when previous commit no longer exists
evernat resolved JENKINS-8853 as Fixed dont try to include all of history when previous commit no longer exists It is committed, so I suppose it is fixed. Change By: evernat (02/Feb/13 5:56 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/groups/opt_out.
[JIRA] (JENKINS-16554) Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file
kutzi updated JENKINS-16554 Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file Change By: kutzi (02/Feb/13 6:00 PM) Priority: Major Blocker This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16554) Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file
kutzi assigned JENKINS-16554 to kutzi Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file Change By: kutzi (02/Feb/13 6:00 PM) Assignee: kutzi This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16206) Upgrade to Apache Commons Codec 1.7
kutzi commented on JENKINS-16206 Upgrade to Apache Commons Codec 1.7 1.6 should be fine as the Commons Codec bug is reported to be fixed in 1.5 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8821) Remote API to createItem configuration inconsistant
evernat commented on JENKINS-8821 Remote API to createItem configuration inconsistant In config.xml of a Maven job, I see "goals" but not "defaultGoal". Are you sure that this a defect? And is this still a problem for you? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16567) Error 500 while cloning a maven job
kutzi resolved JENKINS-16567 as Duplicate Error 500 while cloning a maven job Change By: kutzi (02/Feb/13 6:06 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/groups/opt_out.
[JIRA] (JENKINS-8800) Jenkins does not start after upgrading from Hudson
evernat resolved JENKINS-8800 as Fixed Jenkins does not start after upgrading from Hudson It seems to me that Jenkins currently uses "jmdns-3.4.0-jenkins-3.jar". So this should be fixed. Change By: evernat (02/Feb/13 6:05 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/groups/opt_out.
[JIRA] (JENKINS-16551) NPE during copy project
kutzi resolved JENKINS-16551 as Duplicate NPE during copy project Change By: kutzi (02/Feb/13 6:07 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/groups/opt_out.
[JIRA] (JENKINS-16542) java.lang.ClassFormatError: Failed to load org.apache.commons.codec.binary.Base64OutputStream
kutzi resolved JENKINS-16542 as Duplicate java.lang.ClassFormatError: Failed to load org.apache.commons.codec.binary.Base64OutputStream Change By: kutzi (02/Feb/13 6:08 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/groups/opt_out.
[JIRA] (JENKINS-16546) NPE when creating job from another job
kutzi resolved JENKINS-16546 as Duplicate NPE when creating job from another job Change By: kutzi (02/Feb/13 6:09 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/groups/opt_out.
[JIRA] (JENKINS-16524) JENKINS VERSION 1.500 NOT WORKING CORRECTLY
kutzi commented on JENKINS-16524 JENKINS VERSION 1.500 NOT WORKING CORRECTLY You know that writing all in Caps is considered as rude? If you want to use a better tested version, use the LTS releases. And if you want this bug to be fixed, we need more info - like error messages in the logfile. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8321) Windows service restarts fail
evernat commented on JENKINS-8321 Windows service restarts fail Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16510) NPE on Maven3 Project - after Upgrading from 1.489 to 1.500
kutzi resolved JENKINS-16510 as Duplicate NPE on Maven3 Project - after Upgrading from 1.489 to 1.500 Change By: kutzi (02/Feb/13 6:14 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/groups/opt_out.
[JIRA] (JENKINS-16504) Builds were failing
kutzi commented on JENKINS-16504 Builds were failing "java.lang.OutOfMemoryError: Java heap space" Provide more heap sapce to your build! And please use the users mailing list for questions! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16504) Builds were failing
kutzi resolved JENKINS-16504 as Not A Defect Builds were failing Change By: kutzi (02/Feb/13 6:16 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16479) SVN Check Out Hung
kutzi resolved JENKINS-16479 as Not A Defect SVN Check Out Hung Not a Jenkins issue Change By: kutzi (02/Feb/13 6:17 PM) Status: Open Resolved Resolution: NotADefect This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8510) FATAL: Could not initialize class hudson.util.jna.GNUCLibrary when archiving artifacts from Windows JNLP Slave into Linux Server
evernat commented on JENKINS-8510 FATAL: Could not initialize class hudson.util.jna.GNUCLibrary when archiving artifacts from Windows JNLP Slave into Linux Server Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16601) NPE when loading a Matrix Project
kutzi updated JENKINS-16601 NPE when loading a Matrix Project Change By: kutzi (02/Feb/13 6:21 PM) Component/s: jobconfighistory This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16499) NPE when new job by copy from existing one
dogfood commented on JENKINS-16499 NPE when new job by copy from existing one Integrated in jenkins_main_trunk #2238 FIXED JENKINS-16499 Assuming that: (Revision 12efbc3a9bbcd613dc1e4391283b6839cc79990a) Changelog and fixed test for JENKINS-16499 (Revision 432c63d9851cadb7e93a110a9a22716b0e033d87) Result = SUCCESS Christoph Kutzinski : 12efbc3a9bbcd613dc1e4391283b6839cc79990a Files : core/src/main/java/hudson/model/Job.java Christoph Kutzinski : 432c63d9851cadb7e93a110a9a22716b0e033d87 Files : test/src/test/java/hudson/maven/MavenProjectTest.java changelog.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/groups/opt_out.
[JIRA] (JENKINS-16554) Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file
SCM/JIRA link daemon resolved JENKINS-16554 as Fixed Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file Change By: SCM/JIRA link daemon (02/Feb/13 6:49 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/groups/opt_out.
[JIRA] (JENKINS-16554) Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file
SCM/JIRA link daemon commented on JENKINS-16554 Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file Code changed in jenkins User: Christoph Kutzinski Path: changelog.html core/pom.xml http://jenkins-ci.org/commit/jenkins/41fc8a10bb8eb0e7b106e25eb643481376ac1829 Log: FIXED JENKINS-16554 Restored Java 5 compatibility by downgrading to commons codec 1.6 You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
[JIRA] (JENKINS-16206) Upgrade to Apache Commons Codec 1.7
Fernando Ribeiro commented on JENKINS-16206 Upgrade to Apache Commons Codec 1.7 I am fine with 1.6 as well. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16206) Upgrade to Apache Commons Codec 1.7
kutzi resolved JENKINS-16206 as Fixed Upgrade to Apache Commons Codec 1.7 Downgraded to codec 1.6 Change By: kutzi (02/Feb/13 7:04 PM) Status: Reopened 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/groups/opt_out.
[JIRA] (JENKINS-16206) Upgrade to Apache Commons Codec 1.7
Fernando Ribeiro updated JENKINS-16206 Upgrade to Apache Commons Codec 1.7 Change By: Fernando Ribeiro (02/Feb/13 7:10 PM) Description: ThereisanastybuginApacheCommonsCodec1.4reported at https://issues.apache.org/jira/browse/CODEC-89thatispreventingacustomplugintowork.Ivetriedswitchingtotheplugin-firststrategybutfacedmoreproblems,speciallybecausethepluginusesJAXB.Pleaseevaluateupgrading. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16554) Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file
dogfood commented on JENKINS-16554 Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file Integrated in jenkins_main_trunk #2239 FIXED JENKINS-16554 Restored Java 5 compatibility by downgrading to commons codec 1.6 (Revision 41fc8a10bb8eb0e7b106e25eb643481376ac1829) Result = SUCCESS Christoph Kutzinski : 41fc8a10bb8eb0e7b106e25eb643481376ac1829 Files : core/pom.xml changelog.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/groups/opt_out.
[JIRA] (JENKINS-8642) Defaults for unstable, still unstable, failing and still failing are a bit harsh :-)
Mirko Friedenhagen commented on JENKINS-8642 Defaults for unstable, still unstable, failing and still failing are a bit harsh :-) Hello Alex, maybe to rephrase my use case: Given developers A and B are members in a team of a project with slow development (only few commits) and both are on the recipient list. When B pushes a commit which fails then I expect B to receive a mail immediately but A should not receive this to give B the chance to fix this without bothering A. When however B does not fix the build and a daily build is triggered and the build still fails then I expect A and B to receive a mail as B might be on vacation, e.g. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16554) Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file
Ulli Hafner edited a comment on JENKINS-16554 Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file Hmm, didn't we agree to move to Java 1.6 quite some time ago? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16554) Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file
Ulli Hafner commented on JENKINS-16554 Migrating to Jenkins 1.500 break JDK5 compatibility - UnsupportedClassVersionError: Bad version number in .class file Hmm, didn't we agree to move to 1.6 dependency quite some time ago? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8504) New Maven version download hangs when completed
evernat commented on JENKINS-8504 New Maven version download hangs when completed Is it reproduced recently? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8642) Defaults for unstable, still unstable, failing and still failing are a bit harsh :-)
Alex Earl resolved JENKINS-8642 as Fixed Defaults for unstable, still unstable, failing and still failing are a bit harsh :-) Changed the default settings. Change By: Alex Earl (02/Feb/13 9:09 PM) Status: Open Resolved Assignee: AlexEarl 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/groups/opt_out.
[JIRA] (JENKINS-8642) Defaults for unstable, still unstable, failing and still failing are a bit harsh :-)
SCM/JIRA link daemon commented on JENKINS-8642 Defaults for unstable, still unstable, failing and still failing are a bit harsh :-) Code changed in jenkins User: Alex Earl Path: src/main/java/hudson/plugins/emailext/ExtendedEmailPublisher.java src/main/java/hudson/plugins/emailext/plugins/trigger/FailureTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/StillFailingTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/StillUnstableTrigger.java src/main/java/hudson/plugins/emailext/plugins/trigger/UnstableTrigger.java http://jenkins-ci.org/commit/email-ext-plugin/e46a5402955de00f4fa937599fd36f10670c82ed Log: Fix JENKINS-8642 Changed defaults for the Failing, Still Failing, Unstable and Still Unstable triggers. You received this message because you are subscribed to the Google Groups "Jenkins Commits" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-commits+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_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/groups/opt_out.
[JIRA] (JENKINS-9594) Should be able to send test e-mail based on previous build
Alex Earl assigned JENKINS-9594 to Alex Earl Should be able to send test e-mail based on previous build Change By: Alex Earl (02/Feb/13 9:19 PM) Assignee: AlexEarl This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8404) Java heap space when recording the JUnit test results
evernat commented on JENKINS-8404 Java heap space when recording the JUnit test results wow, 400 000 unit tests! Is it better with a recent Jenkins version? Except increasing Xmx of Maven, do you think of a solution? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8370) Job is getting stuck before it can even start building
evernat commented on JENKINS-8370 Job is getting stuck before it can even start building Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8303) ANT_OPTS are not set when building with JDK-1.4.2_18
evernat resolved JENKINS-8303 as Wont Fix ANT_OPTS are not set when building with JDK-1.4.2_18 hmm, jdk 1.4.2. First, it would be interesting to know if it is the same with a recent Jenkins version or if you have found a workaround. Then, I would say that 1.4.2 probably means "won't fix". Change By: evernat (02/Feb/13 9:33 PM) Status: Open Resolved Resolution: WontFix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8277) Impossible to create a task with create right without configure.
evernat commented on JENKINS-8277 Impossible to create a task with create right without configure. Is it reproduced with a recent Jenkins version? If yes, do you still think that this is problematic? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8217) Ant Setting aren't reloaded form the hudson.tasks.Ant.xml
evernat commented on JENKINS-8217 Ant Setting arent reloaded form the hudson.tasks.Ant.xml Is it reproduced with a recent Jenkins version? If yes, this issue seems important to me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8217) Ant Settings aren't reloaded from hudson.tasks.Ant.xml
evernat updated JENKINS-8217 Ant Settings arent reloaded from hudson.tasks.Ant.xml Change By: evernat (02/Feb/13 9:42 PM) Summary: Ant Setting Settings arentreloaded formthe from hudson.tasks.Ant.xml This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8203) UTF-8 not supported as source files
evernat commented on JENKINS-8203 UTF-8 not supported as source files Have you set the source encoding for the violations plugin in the configuration of the project? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8115) javax.mail.internet.AddressException: Illegal address in string
evernat commented on JENKINS-8115 javax.mail.internet.AddressException: Illegal address in string Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16372) Password parameter is malformed
Gregory Boissinot commented on JENKINS-16372 Password parameter is malformed Yes, it seems to be a core 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/groups/opt_out.
[JIRA] (JENKINS-8026) hudson-cli.jar conncet to hudson issue using groovy script
evernat resolved JENKINS-8026 as Incomplete hudson-cli.jar conncet to hudson issue using groovy script I do not think that this issue can be understood. Please reopen if needed. Change By: evernat (02/Feb/13 10:22 PM) Status: Open Resolved Resolution: Incomplete This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-8019) When hudson is a private build, the version check for plugin updates doesn't work
evernat commented on JENKINS-8019 When hudson is a private build, the version check for plugin updates doesnt work Is it reproduced with a recent Jenkins version? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-7907) Captcha does not work on openjdk
evernat commented on JENKINS-7907 Captcha does not work on openjdk duplicate of JENKINS-3947 see also JENKINS-9915 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-3947) Captcha Not Rendering with OpenJDK 1.6.0.0-b12
evernat updated JENKINS-3947 Captcha Not Rendering with OpenJDK 1.6.0.0-b12 Change By: evernat (02/Feb/13 10:33 PM) Component/s: jcaptcha Component/s: security This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.