[JIRA] (JENKINS-13125) HTTP Content-Range Header one byte past file length
Pei-Tang Huang commented on JENKINS-13125 HTTP Content-Range Header one byte past file length Same problem in 1.504. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17223) Failed build unity3d project with message "Building Player from editor scripts requires Unity PRO"
Roy Inganta Ginting commented on JENKINS-17223 Failed build unity3d project with message "Building Player from editor scripts requires Unity PRO" Yes of couse. Anyway, Thank you so much for your help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17248) java.lang.NullPointerException by start
Matteo Corti commented on JENKINS-17248 java.lang.NullPointerException by start I would move the plugin back. This is not a "global-build-stats" problem but mainly a core problem. The application should not completely crash because of a plugin error! It should start by disabling it. At the moment the web interface is completely unavailable without even a hint on what the problem could be. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17223) Failed build unity3d project with message "Building Player from editor scripts requires Unity PRO"
lacostej commented on JENKINS-17223 Failed build unity3d project with message "Building Player from editor scripts requires Unity PRO" Roy, given that you have set up another jenkins server, should I conclude we will stop troubleshooting that issue on the old server ? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16979) "Discard old builds" broken in 1.503
Bruce Edge reopened JENKINS-16979 "Discard old builds" broken in 1.503 Happens in 1.506 as well. Also reported by http://stackoverflow.com/questions/15268736/error-publisher-org-jenkinsci-plugins-discardbuild-discardbuildpublisher-aborte Change By: Bruce Edge (19/Mar/13 5:36 AM) Resolution: Fixed Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-16979) "Discard old builds" broken in 1.503
Bruce Edge commented on JENKINS-16979 "Discard old builds" broken in 1.503 Looks like it's broken again in 1.506 Discard old builds... ERROR: Publisher org.jenkinsci.plugins.discardbuild.DiscardBuildPublisher aborted due to exception java.lang.UnsupportedOperationException at java.util.AbstractList.add(AbstractList.java:148) at java.util.AbstractList.add(AbstractList.java:108) at org.jenkinsci.plugins.discardbuild.DiscardBuildPublisher.perform(DiscardBuildPublisher.java:148) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:820) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:792) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:739) at hudson.model.Run.execute(Run.java:1592) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
domi commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Although I really understand what Richard is saying, I think using a java implementation for for git has many advantages (as it has for subversion). The administrator not having to setup git on every single slave is just one of the best advantages. An other one is the short commings of the CLI version when it comes to use multiple users for different checkouts on the same slave - in other words security. But any way as so many users are affected by this issues and as the current version already provides a flag to switch back to the CLI version, I think we should just make that flag more easily configurable in the UI and probably change the default back to the CLI version. Maybe this could even be done with a "Git Installation" in the System Configuration and have a provided version (Java) in the dropdown as a selection. This way a admin would be able to choose whether version he wants to use per job and not per Jenkins installation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic edited a comment on JENKINS-17186 Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly I updated to plugins git 1.3.0 and git-client 1.0.4, then updated the git-client to the 1.0.5 test snapshot, then restarted Jenkins and re-triggered an affected build. The test failed, though differently than before (output below). Note: after this, I did have the option to downgrade git-client to 1.0.3, just like 1.2.0 for git. I clicked both, then restarted, but again the git-client never actually downgraded (and I lost the option to downgrade that one after the reboot). Strange. I manually downgraded it to restore normal functionality. Commencing build of Revision 2c09adc94ac7245ae8dacdaac82227443ce0d7bc (mybranch) Checking out Revision 2c09adc94ac7245ae8dacdaac82227443ce0d7bc (mybranch) FATAL: Could not checkout 2c09adc94ac7245ae8dacdaac82227443ce0d7bc hudson.plugins.git.GitException: Could not checkout 2c09adc94ac7245ae8dacdaac82227443ce0d7bc at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:68) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1273) at hudson.plugins.git.GitSCM.access$1100(GitSCM.java:57) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1232) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1208) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1208) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: apt/spec/fixtures/modules/apt/.gitignore at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:246) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:64) ... 16 more Caused by: org.eclipse.jgit.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: apt/spec/fixtures/modules/apt/.gitignore at org.eclipse.jgit.dircache.DirCacheCheckout.cleanUpConflicts(DirCacheCheckout.java:1011) at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:413) at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:391) at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:242) ... 17 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly I updated to plugins git 1.3.0 and git-client 1.0.4, then updated the git-client to this snapshot, then restarted Jenkins and re-triggered an affected build. The test failed, though differently than before (output below). Note: after this, I did have the option to downgrade git-client to 1.0.3, just like 1.2.0 for git. I clicked both, then restarted, but again the git-client never actually downgraded (and I lost the option to downgrade that one after the reboot). Strange. I manually downgraded it to restore normal functionality. Commencing build of Revision 2c09adc94ac7245ae8dacdaac82227443ce0d7bc (mybranch) Checking out Revision 2c09adc94ac7245ae8dacdaac82227443ce0d7bc (mybranch) FATAL: Could not checkout 2c09adc94ac7245ae8dacdaac82227443ce0d7bc hudson.plugins.git.GitException: Could not checkout 2c09adc94ac7245ae8dacdaac82227443ce0d7bc at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:68) at hudson.plugins.git.GitAPI.checkout(GitAPI.java:208) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1273) at hudson.plugins.git.GitSCM.access$1100(GitSCM.java:57) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1232) at hudson.plugins.git.GitSCM$4.invoke(GitSCM.java:1208) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1208) at hudson.model.AbstractProject.checkout(AbstractProject.java:1353) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:683) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:88) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:588) at hudson.model.Run.execute(Run.java:1567) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: apt/spec/fixtures/modules/apt/.gitignore at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:246) at org.jenkinsci.plugins.gitclient.JGitAPIImpl.checkout(JGitAPIImpl.java:64) ... 16 more Caused by: org.eclipse.jgit.errors.CheckoutConflictException: Checkout conflict with file: Cannot delete file: apt/spec/fixtures/modules/apt/.gitignore at org.eclipse.jgit.dircache.DirCacheCheckout.cleanUpConflicts(DirCacheCheckout.java:1011) at org.eclipse.jgit.dircache.DirCacheCheckout.doCheckout(DirCacheCheckout.java:413) at org.eclipse.jgit.dircache.DirCacheCheckout.checkout(DirCacheCheckout.java:391) at org.eclipse.jgit.api.CheckoutCommand.call(CheckoutCommand.java:242) ... 17 more This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17264) m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject
Jason Spotswood created JENKINS-17264 m2release build fails with java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Issue Type: Bug Assignee: teilo Components: m2release Created: 19/Mar/13 3:39 AM Description: When trying to release a Maven component or application (via the Perform Maven Release link), the following error is generated: Status Code: 500 Exception: java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject Stacktrace: javax.servlet.ServletException: java.lang.ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:719) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.MetaClass$12.dispatch(MetaClass.java:384) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) 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:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) 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:677) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:770) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:583) at org.kohsuke.stapler.Stapler.service(Stapler.java:214) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:304) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:95) 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:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) 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:124) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at hudson.security.ChainedServletFilter$1.doFil
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Richard Buckle commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ What is the proper channel to request that the main Jenkins repo be rolled back to Git plugin v1.2.0 and client v1.0.3? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17164) Failed to record SCM polling for hudson.model.FreeStyleProject
Peter Eisentraut reopened JENKINS-17164 Failed to record SCM polling for hudson.model.FreeStyleProject Change By: Peter Eisentraut (19/Mar/13 2:56 AM) Resolution: Not A Defect Status: Resolved Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Takayuki Okazaki commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files Ah, That's make sense. Thanks This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17251) No parser appear when click Add button
yufei Q updated JENKINS-17251 No parser appear when click Add button Change By: yufei Q (19/Mar/13 2:36 AM) Attachment: Update Center [Jenkins].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/groups/opt_out.
[JIRA] (JENKINS-17251) No parser appear when click Add button
yufei Q commented on JENKINS-17251 No parser appear when click Add button I used Chrome and IE, both of them have problems. I have upload all my installed plugin capture, can you find something conflict with Warning-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-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Dallas Gutauckis commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files If you're using a master/slave configuration you need to set the argument in your slave configuration 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-17198) Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files
Takayuki Okazaki commented on JENKINS-17198 Caused by: org.eclipse.jgit.api.errors.CheckoutConflictException: Checkout conflict with files In our environment, this workaround doesn't solve this issue. -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true However, we solved with combination below, which described at http://mrkn.hatenablog.com/entry/2013/03/18/225556 (Japanese). Git Plugin : 1.3.0 Git Client Plugin : 1.0.3 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Peter Loron commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ What @Richard said. I'm not saying JGit can't work. However, there are a ton of different environments out there using Jenkins with Git. In my case a Windows slave talking to a git server via HTTPS with authentication. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-7056) On test specific page attachments should be filtered by the test name
Christopher Orr commented on JENKINS-7056 On test specific page attachments should be filtered by the test name I'm not sure whether there is more to document. What is the unexpected behaviour you're seeing at the moment? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17192) Add support for phpunit3 coverage
sogabe resolved JENKINS-17192 as Not A Defect Add support for phpunit3 coverage Change By: sogabe (19/Mar/13 12:43 AM) 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/groups/opt_out.
[JIRA] (JENKINS-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Richard Buckle commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ I must respectfully say that I find the argument for JGit over CLI Git very unconvincing. I've no evidence whatsoever of CLI Git causing issues, yet this page is full of users for which JGit broke everything. Arguments that "using an external process introduce[s] some major issues" are particularly unconvincing. Jenkins is a CI system. That means that its core role is to invoke external processes and integrate them. Any plugin should be able to invoke external processes and deal with their output. That's the core job of a plug-in. Statements like "I guess it's stable enough…" are also a cause for concern. This is my CI system: I don't want guessing, I want solid code, such as just calling CLI Git. CLI Git gets a huge amount of oversight and testing. It's rock solid. It's become clear that JGit is nowhere near as well-tested or as solid, and frankly it has lost my trust. More importantly, I want confidence that Jenkins is using the exact same tools that I would use if building manually. No-one in their right mind would think of re-implementing gcc or Clang/LLVM in Java, so why re-implement CLI 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/groups/opt_out.
[JIRA] (JENKINS-7056) On test specific page attachments should be filtered by the test name
Luke Daley commented on JENKINS-7056 On test specific page attachments should be filtered by the test name I'm struggling to get this to work. Would you mind updating the documentation for the plugin (https://wiki.jenkins-ci.org/display/JENKINS/JUnit+Attachments+Plugin) for this? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17248) java.lang.NullPointerException by start
Mark Waite updated JENKINS-17248 java.lang.NullPointerException by start Change By: Mark Waite (18/Mar/13 11:36 PM) Component/s: global-build-stats Component/s: core This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17263) "Leave this machine for tied jobs only" does not stick on "(master)"
dogfood commented on JENKINS-17263 "Leave this machine for tied jobs only" does not stick on "(master)" Integrated in jenkins_main_trunk #2386 [FIXED JENKINS-17263] Correctly display current Jenkins.mode. (Revision f2508b36ed38c548debad02d12205b72f5840c59) Result = SUCCESS Jesse Glick : f2508b36ed38c548debad02d12205b72f5840c59 Files : core/src/main/resources/jenkins/model/Jenkins/MasterComputer/configure.jelly 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-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
dogfood commented on JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they don't exist Integrated in jenkins_main_trunk #2386 JENKINS-10502 This was an RFE, not a bug. (Revision 98869558a3c7b6183c60f492153b45384dd36db5) Result = SUCCESS Jesse Glick : 98869558a3c7b6183c60f492153b45384dd36db5 Files : 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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Brad Freyberg commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Same issue as original poster, same versions, on Linux mint 14, brand new setup. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17263) "Leave this machine for tied jobs only" does not stick on "(master)"
SCM/JIRA link daemon commented on JENKINS-17263 "Leave this machine for tied jobs only" does not stick on "(master)" Code changed in jenkins User: Jesse Glick Path: changelog.html core/src/main/resources/jenkins/model/Jenkins/MasterComputer/configure.jelly http://jenkins-ci.org/commit/jenkins/f2508b36ed38c548debad02d12205b72f5840c59 Log: [FIXED JENKINS-17263] Correctly display current Jenkins.mode. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17263) "Leave this machine for tied jobs only" does not stick on "(master)"
SCM/JIRA link daemon resolved JENKINS-17263 as Fixed "Leave this machine for tied jobs only" does not stick on "(master)" Change By: SCM/JIRA link daemon (18/Mar/13 10:32 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-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
SCM/JIRA link daemon commented on JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they don't exist Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/98869558a3c7b6183c60f492153b45384dd36db5 Log: JENKINS-10502 This was an RFE, not a 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/groups/opt_out.
[JIRA] (JENKINS-17263) "Leave this machine for tied jobs only" does not stick on "(master)"
Jesse Glick created JENKINS-17263 "Leave this machine for tied jobs only" does not stick on "(master)" Issue Type: Bug Assignee: Jesse Glick Components: core Created: 18/Mar/13 10:24 PM Description: Node usage mode can be set for the master computer but the current mode is not displayed when you revisit the configuration page. Project: Jenkins Priority: Minor Reporter: Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17262) Remotely triggered build with parameters failing with extended choice parameters
Shaun Kruger created JENKINS-17262 Remotely triggered build with parameters failing with extended choice parameters Issue Type: Bug Assignee: Unassigned Components: extended-choice-parameter Created: 18/Mar/13 10:19 PM Description: I have converted one of the parameters in my project from a statically defined Choice dropdown box to an Extended Choice Parameter in Single select mode. When I execute builds from the web interface everything works fine. When I try to remotely trigger a build using the HTTP GET interface I get an error and my extended choice parameter does not appear in the list of parameters for the build. I did notice that I'm running one minor release behind, but there was nothing in the diff from 0.26 to 0.27 that made me think it could impact this issue. I will be upgrading as soon as there are not currently executing jobs. Environment: Jenkins 1.500 Extended Choice Parameter 0.26 Project: Jenkins Priority: Major Reporter: Shaun Kruger This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.
Mark Waite commented on JENKINS-16693 Heap error while polling Git Plug-in after upgrade to 1.1.26. Yes, if you want to use the new version (1.3.0), then you'll need to stop using include/exclude paths/users. The new version (1.3.0) still uses "git show" to compute "isRevExcluded" just as versions 1.1.25 and later did. In your case, you're probably best to stay with 1.1.21 until there is evidence that the problem is resolved. The new version (1.3.0) is still in the midst of a refactoring which will allow it to use JGit or the command line interface. That refactoring has caused some instability and loss of functionality compared to 1.1.26. You may want to avoid the new version (1.3.0) until it stabilizes further. Refer to JENKINS-17204, JENKINS-17242, JENKINS-17198, JENKINS-16941, and others in the git plugin bug list. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15518) Jenkins Cobertura-1.7 fails to get the coverage result
Liya Katz commented on JENKINS-15518 Jenkins Cobertura-1.7 fails to get the coverage result [Cobertura] Publishing Cobertura coverage report... FATAL: Unable to find coverage results java.io.IOException: /opt/jenkins/jobs/xxx/workspace/xxx/xxx/target/coverage/index.html is not a cobertura coverage report, please check your report pattern at hudson.plugins.cobertura.CoberturaPublisher$ParseReportCallable.invoke(CoberturaPublisher.java:546) at hudson.plugins.cobertura.CoberturaPublisher$ParseReportCallable.invoke(CoberturaPublisher.java:519) at hudson.FilePath.act(FilePath.java:865) at hudson.FilePath.act(FilePath.java:838) at hudson.plugins.cobertura.CoberturaPublisher.perform(CoberturaPublisher.java:337) at hudson.tasks.BuildStepMonitor$3.perform(BuildStepMonitor.java:36) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:814) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:786) at hudson.maven.MavenModuleSetBuild$MavenModuleSetBuildExecution.post2(MavenModuleSetBuild.java:947) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:733) at hudson.model.Run.execute(Run.java:1592) at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:477) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:237) [Cobertura] No coverage results were found using the pattern '**/target/coverage/index.html' relative to '/opt/jenkins/jobs/xxx/workspace'. Did you enter a pattern relative to the correct directory? Did you generate the XML report(s) for Cobertura? [Cobertura] Skipped cobertura reports. Build step 'Publish Cobertura Coverage Report' changed build result to FAILURE This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17204) GIT plugin fetch failing since update Git Plugin to 1.2.0+
Peter Loron commented on JENKINS-17204 GIT plugin fetch failing since update Git Plugin to 1.2.0+ Also having this issue with save versions as OP. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-14546) Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated
Jesse Glick resolved JENKINS-14546 as Duplicate Regular users (others than admin) can't see any nested-views (other than the default one) with role-based authorization strategy activated JENKINS-13429 was fixed in 1.467. @martinkutter your comment about getACL is missing the point, which is that you need to grant View.READ for people to see the views. The block you quote is only for backward compatibility with old versions of Jenkins that did not define View.READ at all. Change By: Jesse Glick (18/Mar/13 8:51 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-16847) Support for copying artifacts from other builds being part of the same MultiJob (previous phases)
Emmanuel Grumbach commented on JENKINS-16847 Support for copying artifacts from other builds being part of the same MultiJob (previous phases) I would also be very interested in this feature This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-12924) FSTrigger triggers builds on jenkins restart
Ghenadie Dumitru commented on JENKINS-12924 FSTrigger triggers builds on jenkins restart Hi, The issue was isolated. It happens every time the Master is restarted (Jenkins master is started under Tomcat) and master has a number of slaves connected through SSH on different machines: all machines (master+slave) are CentOS. I have configured few jobs on each master, jobs are tied to specific slaves. On some slaves, jobs are triggered to run as described in issue once the master is restarted. Not on all slaves, which is little weird. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15423) Instance type selector should be text field
David Walend commented on JENKINS-15423 Instance type selector should be text field I'm interested in cr1.8xlarge myself. The better long-term fix would be to use an AWS API, but there doesn't seem to be one yet. https://forums.aws.amazon.com/message.jspa?messageID=385373 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.
Don Ross commented on JENKINS-16693 Heap error while polling Git Plug-in after upgrade to 1.1.26. So, my only resource if I want to use the new version is to stop using included/exclude paths? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17086) Use IAM Role when creating instance
David Walend commented on JENKINS-17086 Use IAM Role when creating instance I was about to put in a request for this feature, too. As well as having the Jenkins master use its own IAM role instead of being a user. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15826) CVS plugin excluded regions no longer match on the file path
Michael Clarke commented on JENKINS-15826 CVS plugin excluded regions no longer match on the file path I can't see why there would be an issue here - the upgraded CVS plugin uses Matcher#matches so looks for the full String to match. Could you try re-applying your exclude regions and see if you still get the same 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-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.
Nick Holloway commented on JENKINS-16693 Heap error while polling Git Plug-in after upgrade to 1.1.26. The change from "whatchanged" to "show" was made after 1.1.25 to address JENKINS-13368. Before this the plugin only used the most recent commit to evaluate included paths and could omit builds. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Tan Nguyen commented on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 Well, you can vote for it. During the transition you can apply the patch above yourself or take the patched hpi and replace it in your jenkins/hudson installation. hth This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17259) Option for not expanding parameters
Stefan Eder edited a comment on JENKINS-17259 Option for not expanding parameters In the meantime I did a workaround to prevent this error: Upgraded to token-macro plugin 1.6 Used "expandAll" method with the "throwException" parameter set to "false" This will return the value of the parameter, if no defined build or environment variable is found. It might be a cheap solution for the stated problem but might not be the behaviour every user of this plugin is looking for (e.g. would pass on ${someVar} if not expandable to the script instead of stopping with an error). However it works for me. I attached the patch file. Maybe it is of some use. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17259) Option for not expanding parameters
Stefan Eder updated JENKINS-17259 Option for not expanding parameters In the meantime I did a workaround to prevent this error: Upgraded to token-macro plugin 1.6 Used "expandAll" method with the "throwException" parameter set to "false" This will return the value of the parameter, if no defined build or environment variable is found. It might be a cheap solution for the stated problem but might not be the behaviour every user of this plugin is looking for (would pass on ${someVar} if not expanded instead of stopping with an error). However it works for me. I attached the patch file. Maybe it is of some use. Change By: Stefan Eder (18/Mar/13 6:38 PM) Attachment: scriptler-plugin_no_token_exceptions.patch This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Bruno Medeiros commented on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 I have the same issue. Any expected release date for the pull request above? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-10266) Set grails.work.dir to something unique by default
Mark Takacs edited a comment on JENKINS-10266 Set grails.work.dir to something unique by default I'd actually like the ability to do this as well. Consider two builds (one from a legacy branch, one from a current branch). Both builds will store their work.dir stuff in the same location, causing confusion. see http://jira.grails.org/browse/GRAILS-5359 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-10266) Set grails.work.dir to something unique by default
Mark Takacs commented on JENKINS-10266 Set grails.work.dir to something unique by default I'd actually like the ability to do this as well. Consider two builds (one from a legacy branch, one from a current branch). Both builds will store their work.dir stuff in the same location, causing confusion. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-14901) Emulator start failed on Ubuntu (SDK 20.0.3)
recampbell commented on JENKINS-14901 Emulator start failed on Ubuntu (SDK 20.0.3) We were having this precise issue. As indicated by this stackoverflow thread, we fixed the issue by setting the LD_LIBRARY_PATH as follows (using EnvInject): LD_LIBRARY_PATH=/opt/android/android-sdk-linux/tool/lib I think the fix is for the Android Emulator plugin to populate this for us? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16693) Heap error while polling Git Plug-in after upgrade to 1.1.26.
Don Ross commented on JENKINS-16693 Heap error while polling Git Plug-in after upgrade to 1.1.26. Upgrading our test environment to the entirely-new version 1.3.0 of the plug-in still shows the same behavior. For now, we are okay with keeping our production environment at version 1.1.21, but the time will come when we want some feature available in a new version, and we won't be able to upgrade. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17261) Trac plugin not working with Jenkins 1.506
Mark S. created JENKINS-17261 Trac plugin not working with Jenkins 1.506 Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: trac Created: 18/Mar/13 5:05 PM Description: The first strange thing I detected was that there is no possibility to enter the trac frontend url when choosing trac as a repository browser for subversion on the jobs configuration page. In addition to that, I cannot see any links either on the job overview page or in the changes/history display. I'm using svn://$ip/..-style svn urls. Project: Jenkins Priority: Major Reporter: Mark S. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17260) Mercurial Push Notifications: URLs should be compared in canonical form
Elifarley updated JENKINS-17260 Mercurial Push Notifications: URLs should be compared in canonical form Change By: Elifarley (18/Mar/13 4:57 PM) Description: The comparison of a job's repository URL and the URL passed to notifyCommit will fail when the 2 URLs differ slightly, even though they point to the same place.Example that triggers the problem:Repository URL (in job configuration screen) : http://mymercurialrepo.com.br/hg/main/myproj/hook configuration:[hooks]commit.jenkins = wget -q -O /dev/null http://myjenkins.com.br/jenkins/mercurial/notifyCommit?url="">incoming.jenkins = wget -q -O /dev/null http://myjenkins.com.br/jenkins/mercurial/notifyCommit?url="">The URL comparison should first transform both URLs to their canonical form (by appending a slash at the end if one is missing, for instance).I guess it will also fail if one of the URLs includes an HTTP redirect. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17260) Mercurial Push Notifications: URLs should be compared in canonical form
Elifarley updated JENKINS-17260 Mercurial Push Notifications: URLs should be compared in canonical form Change By: Elifarley (18/Mar/13 4:56 PM) Environment: Linux, Jenkis 1.506, Mercurial extension v. 1.44, mercurial 2.2 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17260) Mercurial Push Notifications: URLs should be compared in canonical form
Elifarley created JENKINS-17260 Mercurial Push Notifications: URLs should be compared in canonical form Issue Type: Bug Affects Versions: current Assignee: Jesse Glick Components: mercurial Created: 18/Mar/13 4:55 PM Description: The comparison of a job's repository URL and the URL passed to notifyCommit will fail when the 2 URLs differ slightly, even though they point to the same place. Example that triggers the problem: Repository URL: http://mymercurialrepo.com.br/hg/main/myproj/ hook configuration: [hooks] commit.jenkins = wget -q -O /dev/null http://myjenkins.com.br/jenkins/mercurial/notifyCommit?url=""> incoming.jenkins = wget -q -O /dev/null http://myjenkins.com.br/jenkins/mercurial/notifyCommit?url=""> The URL comparison should first transform both URLs to their canonical form (by appending a slash at the end if one is missing, for instance). I guess it will also fail if one of the URLs includes an HTTP redirect. Project: Jenkins Priority: Major Reporter: Elifarley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17258) Mercurial repository is always cloned instead of being updated
Elifarley assigned JENKINS-17258 to Jesse Glick Mercurial repository is always cloned instead of being updated Change By: Elifarley (18/Mar/13 4:56 PM) Assignee: Kohsuke Kawaguchi Jesse Glick This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17259) Option for not expanding parameters
Stefan Eder created JENKINS-17259 Option for not expanding parameters Issue Type: New Feature Assignee: domi Components: scriptler, token-macro Created: 18/Mar/13 4:45 PM Description: When executing a groovy script which accepts some parameters as input and some parameters contain a '$' (e.g. some$pass!) the following happens: 17:04:13 Execution of script [somescript.groovy] failed - Unrecognized macro 'pass' in 'some$pass!'org.jenkinsci.plugins.tokenmacro.MacroEvaluationException: Unrecognized macro 'pass' in 'some$pass!' 17:04:13 at org.jenkinsci.plugins.tokenmacro.TokenMacro.expand(TokenMacro.java:185) 17:04:13 at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:219) 17:04:13 at org.jenkinsci.plugins.tokenmacro.TokenMacro.expandAll(TokenMacro.java:208) 17:04:13 at org.jenkinsci.plugins.scriptler.builder.ScriptlerBuilder.perform(ScriptlerBuilder.java:104) If I understand the code correctly the behaviour of the token-macro plugin trying to expand the contents of the parameters is wanted (JENKINS-11914 is related to this). However it is problematic when passing on parameters which contain a '$' and should not be expanded. Therefore a feature which lets the user define whether a specific parameter or all parameters should be expanded would be useful. Environment: scriptler 2.5.1, token-macro 1.6 Project: Jenkins Priority: Minor Reporter: Stefan Eder This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17258) Mercurial repository is always cloned instead of being updated
Elifarley commented on JENKINS-17258 Mercurial repository is always cloned instead of being updated Adding the "--quiet" option will probably fix it, as in: hg --quiet showconfig paths.default This way the output should be stable no matter what the system-level hgrc file says about ui.debug This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17258) Mercurial repository is always cloned instead of being updated
Elifarley updated JENKINS-17258 Mercurial repository is always cloned instead of being updated Change By: Elifarley (18/Mar/13 4:38 PM) Description: My system-level hgrc file sets debug to on: hg showconfig|grep ui.debug/etc/mercurial/hgrc:28: ui.debug=true This seems to cause problems when parsing the output of hg. Here's the log output:13:25:37 Building remotely on myslave in workspace /var/data/jenkins-slave/workspace/MYJOB-2.8.413:25:38 $ hg clone --rev 2.8.4 --noupdate http://mymercurialrepo.com.br/hg/main/myjob /var/data/jenkins-slave/workspace/MYJOB-2.8.413:25:38 using http://mymercurialrepo.com.br/hg/main/myjob13:25:38 sending capabilities command13:25:38 sending lookup command13:25:38 query 1; heads13:25:38 sending batch command13:25:38 sending getbundle command13:25:38 adding changesets13:25:38 changesets: 1 chunks13:25:38 add changeset e1cfb9e9c39a13:25:38 changesets: 2 chunks[...] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17258) Mercurial repository is always cloned instead of being updated
Elifarley updated JENKINS-17258 Mercurial repository is always cloned instead of being updated Change By: Elifarley (18/Mar/13 4:36 PM) Description: hg showconfig|grep ui.debug/etc/mercurial/hgrc:28: ui.debug=true Here's the log output:13:25:37 Building remotely on myslave in workspace /var/data/jenkins-slave/workspace/MYJOB-2.8.413:25:38 $ hg clone --rev 2.8.4 --noupdate http://mymercurialrepo.com.br/hg/main/myjob /var/data/jenkins-slave/workspace/MYJOB-2.8.413:25:38 using http://mymercurialrepo.com.br/hg/main/myjob13:25:38 sending capabilities command13:25:38 sending lookup command13:25:38 query 1; heads13:25:38 sending batch command13:25:38 sending getbundle command13:25:38 adding changesets13:25:38 changesets: 1 chunks13:25:38 add changeset e1cfb9e9c39a13:25:38 changesets: 2 chunks[...] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17258) Mercurial repository is always cloned instead of being updated
Elifarley updated JENKINS-17258 Mercurial repository is always cloned instead of being updated Change By: Elifarley (18/Mar/13 4:33 PM) Environment: Linux, Jenkis 1. 458 506 , mercurial Mercurial extension v. 1. 7 44, mercurial 2.2 Description: JENKINS-4672 gives possibility to setup Marcurial debug flag.When I switch it on, the all mercurial call is done with option "--debug".The first command, during the build, checks if configuration of repository wasn Here ' t changed.This check is done by comparision result of commad "hg showconfig paths.default" with jenkins configuration.But there is a different output if s the debug option is ON.Without debug option log output : $ hg showconfig paths.default https 13 : 25:37 Building remotely on myslave in workspace / var / hg data / hg jenkins-slave / zpis workspace/MYJOB-2.8.4 With debug option 13 : 25:38 $ hg clone -- debug showconfig paths rev 2 . default read config from 8.4 --noupdate http : / etc / mercurial/hgrc read config from: /data/hudson/ mymercurialrepo . hgrc none: https: com.br / / hg/ hg main / zpisSo with the debug option, the mercurial configuration is always different as jenkins configuration.Result is : ---Building in workspace myjob / var/ data/ hudson/jobs/vlk jenkins - pokus slave /workspace [workspace] $ hg /MYJOB - -debug showconfig paths 2 . default 8.4 read config from 13 : /etc/mercurial/hgrcread config from 25 : 38 using http: / data / hudson/ mymercurialrepo . hgrcnone: https: com.br / / hg/ hg main / zpis myjob which looks different than https 13 : //hg/hg/zpis 25:38 sending capabilities command so falling back to fresh clone rather than incremental update 13:25:38 sending lookup command 13:25:38 query 1; heads 13:25:38 sending batch command Workaround 13 : Switch off the degug option. 25:38 sending getbundle command 13:25:38 adding changesets 13:25:38 changesets: 1 chunks13:25:38 add changeset e1cfb9e9c39a13:25:38 changesets: 2 chunks[...] This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17258) Mercurial repository is always cloned instead of being updated
Elifarley created JENKINS-17258 Mercurial repository is always cloned instead of being updated Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Components: mercurial Created: 18/Mar/13 4:30 PM Description: JENKINS-4672 gives possibility to setup Marcurial debug flag. When I switch it on, the all mercurial call is done with option "--debug". The first command, during the build, checks if configuration of repository wasn't changed. This check is done by comparision result of commad "hg showconfig paths.default" with jenkins configuration. But there is a different output if the debug option is ON. Without debug option : $ hg showconfig paths.default https://hg/hg/zpis With debug option : hg --debug showconfig paths.default read config from: /etc/mercurial/hgrc read config from: /data/hudson/.hgrc none: https://hg/hg/zpis So with the debug option, the mercurial configuration is always different as jenkins configuration. Result is : --- Building in workspace /data/hudson/jobs/vlk-pokus/workspace [workspace] $ hg --debug showconfig paths.default read config from: /etc/mercurial/hgrc read config from: /data/hudson/.hgrc none: https://hg/hg/zpis which looks different than https://hg/hg/zpis so falling back to fresh clone rather than incremental update Workaround : Switch off the degug option. Environment: Linux, Jenkis 1.458, mercurial 1.7 Project: Jenkins Priority: Minor Reporter: Elifarley This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
dogfood commented on JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they don't exist Integrated in jenkins_main_trunk #2381 JENKINS-10502 Option to make the build NOT fail if there is nothing to archive (Revision d3096819f6a70c107399fbcf2df23718098c926e) JENKINS-10502 Noting. (Revision e88932956f78dc8c89835256b820cca671756286) Result = SUCCESS pjrodriguezt : d3096819f6a70c107399fbcf2df23718098c926e Files : test/src/test/java/hudson/tasks/ArtifactArchiverTest.java test/src/test/java/hudson/model/AbstractProjectTest.java core/src/main/java/hudson/tasks/ArtifactArchiver.java core/src/main/resources/hudson/tasks/ArtifactArchiver/config.properties core/src/main/resources/hudson/tasks/ArtifactArchiver/config.jelly test/src/test/java/hudson/tasks/LogRotatorTest.java Jesse Glick : e88932956f78dc8c89835256b820cca671756286 Files : 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-17257) EC2 plugin fails to launch slave (IndexOutOfBoundsException)
Jai Ram Rideout created JENKINS-17257 EC2 plugin fails to launch slave (IndexOutOfBoundsException) Issue Type: Bug Assignee: Francis Upton Components: ec2 Created: 18/Mar/13 4:20 PM Description: Using the latest dev version of the EC2 plugin from GitHub, the launching of slaves sometimes fails due to an IndexOutOfBoundsException. Relevant stack trace from Jenkins logs: WARNING: Provisioned slave QIIME 1.6.0 AMI (Ubuntu 64-bit) (ami-10b12f79) failed to launch java.util.concurrent.ExecutionException: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:252) at java.util.concurrent.FutureTask.get(FutureTask.java:111) at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:344) at hudson.plugins.ec2.EC2Cloud$1.call(EC2Cloud.java:329) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) at java.util.concurrent.FutureTask.run(FutureTask.java:166) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1146) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:679) Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0 at java.util.ArrayList.rangeCheck(ArrayList.java:571) at java.util.ArrayList.get(ArrayList.java:349) at hudson.plugins.ec2.EC2Computer._describeInstanceOnce(EC2Computer.java:142) at hudson.plugins.ec2.EC2Computer._describeInstance(EC2Computer.java:125) at hudson.plugins.ec2.EC2Computer.getState(EC2Computer.java:101) at hudson.plugins.ec2.EC2ComputerLauncher.launch(EC2ComputerLauncher.java:56) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) ... 5 more This results in a disconnected node (from Jenkins' point of view) but the instance is still running on Amazon EC2. The Jenkins logs indicate that the slave is idle, but it is never terminated by the EC2 plugin, even though I have the idle termination time set to 10 minutes: ... QIIME 1.6.0 AMI (Ubuntu 64-bit) (i-54fb093e) idle: 32412220 QIIME 1.6.0 AMI (Ubuntu 64-bit) (i-54fb093e) idle: 32532221 ... Other slaves using the same AMI are automatically launched just fine after this failure occurs. Environment: Ubuntu 12.04 LTS (64-bit) Jenkins 1.505 EC2 plugin from GitHub repo (commit 76c95f9c4a02917d09e28e4e4efa705c845f30df) Project: Jenkins Labels: plugin slave jenkins exception plugins Priority: Major Reporter: Jai Ram Rideout This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17256) Unexpected error in launching a slave (NegativeArraySizeException)
bogdan d created JENKINS-17256 Unexpected error in launching a slave (NegativeArraySizeException) Issue Type: Bug Affects Versions: current Assignee: Kohsuke Kawaguchi Attachments: System Information [Jenkins].htm, Thread dump [Jenkins].htm Components: ssh, ssh-slaves Created: 18/Mar/13 3:57 PM Description: Jenkins running on Windows and trying to start OSx slave via ssh (using private key) LOG: [03/18/13 17:45:56] [SSH] Opening SSH connection to 192.168.1.35:22. [03/18/13 17:45:56] [SSH] Authenticating as Jenkins with C:\Jenkins\ssh_keys\private.ppk. ERROR: Unexpected error in launching a slave. This is probably a bug in Jenkins. java.lang.NegativeArraySizeException at org.kohsuke.putty.KeyReader.read(KeyReader.java:59) at org.kohsuke.putty.KeyReader.readInt(KeyReader.java:71) at org.kohsuke.putty.PuTTYKey.toOpenSSH(PuTTYKey.java:198) at hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:730) at hudson.plugins.sshslaves.SSHLauncher.launch(SSHLauncher.java:278) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:222) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) [03/18/13 17:45:56] [SSH] Connection closed. Environment: CPU:Intel Xeon OS:Windows Server 2008 R2 Standard Project: Jenkins Priority: Major Reporter: bogdan d This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16314) cvs plugin removes sticky branch tag
James Morgan commented on JENKINS-16314 cvs plugin removes sticky branch tag Thanks for looking into this This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-17248) java.lang.NullPointerException by start
Matteo Corti commented on JENKINS-17248 java.lang.NullPointerException by start Removing the global-build-stats plugin I was able to restart Jenkins. Although the problem is caused by a plugin the application should not crash. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
SCM/JIRA link daemon commented on JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they don't exist Code changed in jenkins User: Jesse Glick Path: changelog.html http://jenkins-ci.org/commit/jenkins/e88932956f78dc8c89835256b820cca671756286 Log: JENKINS-10502 Noting. Compare: https://github.com/jenkinsci/jenkins/compare/aeb887c12d60...e88932956f78 – 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-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
SCM/JIRA link daemon resolved JENKINS-10502 as Fixed Add an option to make archiving the artifacts non-fatal if they don't exist Change By: SCM/JIRA link daemon (18/Mar/13 3: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/groups/opt_out.
[JIRA] (JENKINS-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
SCM/JIRA link daemon commented on JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they don't exist Code changed in jenkins User: Jesse Glick Path: core/src/main/java/hudson/tasks/ArtifactArchiver.java core/src/main/resources/hudson/tasks/ArtifactArchiver/config.jelly core/src/main/resources/hudson/tasks/ArtifactArchiver/config.properties core/src/main/resources/hudson/tasks/ArtifactArchiver/help-allowEmptyArchive.html test/src/test/groovy/hudson/matrix/MatrixProjectTest.groovy test/src/test/java/hudson/model/AbstractProjectTest.java test/src/test/java/hudson/tasks/ArtifactArchiverTest.java test/src/test/java/hudson/tasks/LogRotatorTest.java http://jenkins-ci.org/commit/jenkins/aeb887c12d60987745ed40a55d0f6ddcee503426 Log: Merge pull request #732 from pjrt/JENKINS-10502 [FIXED JENKINS-10502] Option to make the build not fail if there is nothing to archive Compare: https://github.com/jenkinsci/jenkins/compare/77e011a3dae3...aeb887c12d60 – 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-10502) Add an option to make archiving the artifacts non-fatal if they don't exist
SCM/JIRA link daemon commented on JENKINS-10502 Add an option to make archiving the artifacts non-fatal if they don't exist Code changed in jenkins User: Pedro Rodriguez Path: core/src/main/java/hudson/tasks/ArtifactArchiver.java core/src/main/resources/hudson/tasks/ArtifactArchiver/config.jelly core/src/main/resources/hudson/tasks/ArtifactArchiver/config.properties test/src/test/java/hudson/model/AbstractProjectTest.java test/src/test/java/hudson/tasks/ArtifactArchiverTest.java test/src/test/java/hudson/tasks/LogRotatorTest.java http://jenkins-ci.org/commit/jenkins/d3096819f6a70c107399fbcf2df23718098c926e Log: JENKINS-10502 Option to make the build NOT fail if there is nothing to archive This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16475) Build stats graph configuration lost after Jenkins Restart
Jason Karney commented on JENKINS-16475 Build stats graph configuration lost after Jenkins Restart I am experiencing a similar – or perhaps the same – problem. I just noticed it last week, because I happened to be reviewing the Jenkins (tomcat) log and noticed a SEVERE startup error related to global-build-stats. We are running Jenkins 1.455 and global build stats 1.3. We have been using this same version of Jenkins and plugin for many months now. I did some testing, and the problems seems to be that one of our jobResults.xml files contained the value "null." That is, the file jobResults-2012-01.xml contained one line, and it was "". Renaming the file did not help, but removing the file allowed Jenkins to start without reporting the error. Further testing is required to verify that chart data is saved after restart. Interestingly, this error was occurring on two Jenkins servers, both of which are kept to identical configuration in terms of plugins but not jobs. The specific error in the Jenkins log at startup time is: SEVERE: Unable to read jenkins/home/global-build-stats.xml hudson.util.IOException2: Unable to read jenkins/home/global-build-stats.xml ... [stacktrace] Caused by: com.thoughtworks.xstream.converters.ConversionException: null : null I'm sure it is showing that "" couldn't be unmarshalled. The question is, why is that jobResult.xml's value null to begin with? Maxfield – if you could check your JENKINS_HOME/global-build-stats/jobresults directory for file(s) with the value null, you might verify having the same problem; and try to fix it by removing any "null" files. I'd be curious to see if you have the same thing happening. I hope this helps. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17073) Support specifying logger for phing
sogabe commented on JENKINS-17073 Support specifying logger for phing I've just released Phing Plugin 0.12. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17255) Dropdwon not compatible with cloudbees folder
Nicolas De Loof created JENKINS-17255 Dropdwon not compatible with cloudbees folder Issue Type: Bug Assignee: jieryn Components: dropdown-viewstabbar Created: 18/Mar/13 2:47 PM Description: views inside Folders (cloudbees folder plugin), appear as tabs, not dropdwon. Can be reproduced installing the cloudbees FREE plugins Seems dropdown-views-tabbar don't handle nested ItemGroups in Jenkins Project: Jenkins Priority: Minor Reporter: Nicolas De Loof This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17255) Dropdwon not compatible with cloudbees folder
Nicolas De Loof updated JENKINS-17255 Dropdwon not compatible with cloudbees folder Change By: Nicolas De Loof (18/Mar/13 2:48 PM) Labels: folders This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17177) wrong build result in post build steps after failed pre build step in maven project
Steve Boardwell commented on JENKINS-17177 wrong build result in post build steps after failed pre build step in maven project Thanks for the quick response. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16967) Allow environment variables in phing properties
SCM/JIRA link daemon resolved JENKINS-16967 as Fixed Allow environment variables in phing properties Change By: SCM/JIRA link daemon (18/Mar/13 2:30 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-16967) Allow environment variables in phing properties
SCM/JIRA link daemon commented on JENKINS-16967 Allow environment variables in phing properties Code changed in jenkins User: Seiji Sogabe Path: src/main/java/hudson/plugins/phing/PhingBuilder.java http://jenkins-ci.org/commit/phing-plugin/720a99e5e4e9616d0a3e307068ea62d5b0dccaa0 Log: [FIXED JENKINS-16967] Allow environment variables in phing properties – 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-15826) CVS plugin excluded regions no longer match on the file path
Jeremy Michelson commented on JENKINS-15826 CVS plugin excluded regions no longer match on the file path Sorry I wasn't clear. The issue is that the build doesn't run if excluded regions are set. Suppose you've the hierarchy file.c dir1/ dir1/file1.c dir2/ dir2/file2.c ... With version 1.6 of the CVS plugin, one could set an excluded region of "[^/]*.c". Then changes to "file.c" would (correctly!) not trigger a build, but changes to "dir1/file1.c" would trigger a build. Now, neither triggers a build. I'm not sure how useful the job config would be. Because of this bug, we had to remove the excluded regions (at the cost of a large increase in spurious builds) in order to get the builds we needed, due to changes in subdirectories. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17254) Multijob view last succes / last failure columns shows status instead of #of days/hours since
Jurgen Van Bouchaute updated JENKINS-17254 Multijob view last succes / last failure columns shows status instead of #of days/hours since Change By: Jurgen Van Bouchaute (18/Mar/13 1:55 PM) Summary: Multijon Multijob view last succes / last failure columns shows status instead of #of days/hours since This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17254) Multijon view last succes / last failure columns shows status instead of #of days/hours since
Jurgen Van Bouchaute created JENKINS-17254 Multijon view last succes / last failure columns shows status instead of #of days/hours since Issue Type: Bug Assignee: Unassigned Attachments: 18-03-2013 14-50-04.png Components: jenkins-multijob-plugin Created: 18/Mar/13 1:55 PM Description: The last success / last failure columns on the multijob view should mention the number of days / hours since this last success/failure, not a status ball See screenshot. Project: Jenkins Priority: Major Reporter: Jurgen Van Bouchaute This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-3907) Mercurial updates on matrix projects aren't synced properly
Jesse Glick commented on JENKINS-3907 Mercurial updates on matrix projects aren't synced properly So much for Kohsuke’s original proposal to generalize this, I guess. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17247) Exception while trigger downstream projects
Jesse Glick updated JENKINS-17247 Exception while trigger downstream projects Change By: Jesse Glick (18/Mar/13 1:45 PM) Assignee: Jesse Glick Component/s: core Component/s: secret This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17221) "You must use POST method to trigger builds" warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParam
Jesse Glick commented on JENKINS-17221 "You must use POST method to trigger builds" warning message pops up preventing remote triggering of builds with parameters using wget URL http://server/job/myjob/buildWithParameters?PARAMETER=Value Edited. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17253) In tomcat localhost logs "java.lang.IllegalStateException: getOutputStream() has already been called for this response"
Danny Staple created JENKINS-17253 In tomcat localhost logs "java.lang.IllegalStateException: getOutputStream() has already been called for this response" Issue Type: Bug Assignee: Unassigned Components: core Created: 18/Mar/13 1:32 PM Description: In our localhost..log files, we are seeing it flooded with errors like this: Mar 3, 2013 12:04:12 AM org.apache.catalina.core.StandardWrapperValve invoke SEVERE: Servlet.service() for servlet Stapler threw exception java.lang.IllegalStateException: getOutputStream() has already been called for this response at org.apache.catalina.connector.Response.getWriter(Response.java:610) at org.apache.catalina.connector.ResponseFacade.getWriter(ResponseFacade.java:198) at javax.servlet.ServletResponseWrapper.getWriter(ServletResponseWrapper.java:112) at org.kohsuke.stapler.compression.CompressionServletResponse.getWriter(CompressionServletResponse.java:58) at org.kohsuke.stapler.compression.CompressionFilter.reportException(CompressionFilter.java:68) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:53) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:433) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11AprProcessor.process(Http11AprProcessor.java:859) at org.apache.coyote.http11.Http11AprProtocol$Http11ConnectionHandler.process(Http11AprProtocol.java:574) at org.apache.tomcat.util.net.AprEndpoint$Worker.run(AprEndpoint.java:1527) at java.lang.Thread.run(Thread.java:619) We are seeing them approximately twice a minute, and have had performance issues on the master node. Environment: Jenkins ver. 1.480.2, Tomcat 6, Linux X86_64 Project: Jenkins Priority: Major Reporter: Danny Staple This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-15518) Jenkins Cobertura-1.7 fails to get the coverage result
Jesse Glick commented on JENKINS-15518 Jenkins Cobertura-1.7 fails to get the coverage result @liya please show the exact error message you now get, so developers can confirm that you are really running 1.8, and that the error is really the same. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-13669) NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith
SCM/JIRA link daemon commented on JENKINS-13669 NPE in hudson.plugins.mercurial.MercurialSCM.compareRemoteRevisionWith Code changed in jenkins User: Jesse Glick Path: src/main/java/hudson/plugins/mercurial/MercurialSCM.java http://jenkins-ci.org/commit/mercurial-plugin/1576c70a2c753480857391757b8c059b39fda880 Log: JENKINS-13669 willemv advocates simply failing the polling operation if possiblyCachedRepo is null. – 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-17073) Support specifying logger for phing
Alexander Obuhovich commented on JENKINS-17073 Support specifying logger for phing What is the approximate date of 0.12 version release (I think this fix will go into that 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-17073) Support specifying logger for phing
SCM/JIRA link daemon commented on JENKINS-17073 Support specifying logger for phing Code changed in jenkins User: Seiji Sogabe Path: src/main/java/hudson/plugins/phing/PhingBuilder.java src/main/resources/hudson/plugins/phing/PhingBuilder/config.jelly src/main/resources/hudson/plugins/phing/PhingBuilder/config_ja.properties src/test/java/hudson/plugins/phing/PhingBuilderConfigSubmitTest.java http://jenkins-ci.org/commit/phing-plugin/0c5382aedae969c9bca903d15b4becd0a7ccfcdf Log: [FIXED JENKINS-17073] added Options field to specify logger Compare: https://github.com/jenkinsci/phing-plugin/compare/ffdc5f67a923...0c5382aedae9 – 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-17073) Support specifying logger for phing
SCM/JIRA link daemon resolved JENKINS-17073 as Fixed Support specifying logger for phing Change By: SCM/JIRA link daemon (18/Mar/13 1:16 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-17101) Not able to login with chrome, chromium, opera - Only works with firefox
Martin K. commented on JENKINS-17101 Not able to login with chrome, chromium, opera - Only works with firefox Upgraded to Jenkins ver. 1.506 => still not possible to login. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17250) Issue with QAR (our case 8835)
Mads Nielsen resolved JENKINS-17250 as Fixed Issue with QAR (our case 8835) This has been resolved. Turns out that the symlink was put in an inaccessible location for the jenkins instance. Change By: Mads Nielsen (18/Mar/13 11:55 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-13465) Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0
Gabriel Landais commented on JENKINS-13465 Unable perform release: ClassCastException: net.sf.json.JSONNull cannot be cast to net.sf.json.JSONObject on Hudson 2.2.0 Submitted pull request https://github.com/jenkinsci/m2release-plugin/pull/9 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17251) No parser appear when click Add button
Ulli Hafner commented on JENKINS-17251 No parser appear when click Add button Which browser are you using? Are there any problems reported when using a _javascript_ Debugger like Firebug? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17211) HTTP authentication is not possible with JGit implementation of git-client plugin
Olivier Kuhn updated JENKINS-17211 HTTP authentication is not possible with JGit implementation of git-client plugin Change By: Olivier Kuhn (18/Mar/13 10:27 AM) Issue Type: Bug Improvement This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17252) JGit checkout poor performaces
Olivier Kuhn created JENKINS-17252 JGit checkout poor performaces Issue Type: Improvement Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 18/Mar/13 10:26 AM Description: Hello, I have just updated the Git client to 1.0.4 and noticed that my build was hanging on the step: Checking out Revision 9c65124b7c042f2427702e19ef9b24b2d7151191 (origin/branch) After some investigation, it was running well, but the "checkout" was very slow. The thread call stack was often in I/O and zip related classes. Previously the complete build of the project took 2 minutes, now with JGit the checkout was not completed after 20 minutes... I have found a workaround (not tested yet) in JENKINS-17211: -Dorg.jenkinsci.plugins.gitclient.Git.useCLI=true Would it be a way to optimize this step in the plugin or provide a property in the Jenkins configuration interface to use the git command line tool ? Environment: Suse 11 Project: Jenkins Labels: plugin jgit Priority: Minor Reporter: Olivier Kuhn This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17186) Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly
Martin Falatic commented on JENKINS-17186 Linux: if there is a recursive directory within the git repo you're building, the initial checkout will fail badly And that makes sense - once Jgit is up to the challenge. Judging by the number and age of the currently open bugs against Jgit I have to question its current stability but I'm sure eventually it'll be made to work as well or even better than native git despite the shortcomings of doing git in Java (this very bug reflects the fact that Java takes a lot of coaxing (and external hooks) to work seamlessly at a low level with a given operating system and its filesystem structures). As for dependencies, it appears Jgit requires extensive backward compatibility with various flavors of Java. Looks like it's just trading one kind of fragility for another right now. This isn't the place for a discussion of the merits of this change, other than to suggest that such a fundamental change get more visibility when it happens. I certainly didn't expect a minor point release of Jenkins to make this large of a change. I'll monitor the new Jgit bugs closely before we commit to updating to future point releases, and I'll let you know once we've tested this patch. Does this patch fix any other issues due to Jgit in Jenkins or just this one? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17251) No parser appear when click Add button
yufei Q commented on JENKINS-17251 No parser appear when click Add button I have checked. Nothing seems related. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17251) No parser appear when click Add button
Ulli Hafner commented on JENKINS-17251 No parser appear when click Add button Can you please check your console or the Jenkins log too see if there is an exception thrown? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-17251) No parser appear when click Add button
yufei Q created JENKINS-17251 No parser appear when click Add button Issue Type: Bug Assignee: Ulli Hafner Attachments: snapshot.png Components: warnings Created: 18/Mar/13 9:24 AM Description: The thing is that I have installed Warnings Plug-in 4.23,and I can see it in my job configuration.But it will do nothing when I click Add button to add Scan console. Nothing appears. Do you have any idea about this problem? Thanks a lot. Project: Jenkins Priority: Major Reporter: yufei Q This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-16835) jenkins.war version 1.500: windows slave connection issue
Linards L commented on JENKINS-16835 jenkins.war version 1.500: windows slave connection issue Comment above should be added to FAQ ! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.