[JIRA] [promoted-builds-plugin] (JENKINS-12528) Started-By Environment Variable Plugin does not work in manually approved promoted builds
Title: Message Title Hua Zhang closed an issue as Won't Fix Out of date and no more relevant. Closed. Jenkins / JENKINS-12528 Started-By Environment Variable Plugin does not work in manually approved promoted builds Change By: Hua Zhang Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ircbot-plugin] (JENKINS-10966) IRC notification in promotion process multiplies the number of channel everytime the job configure is saved
Title: Message Title Hua Zhang closed an issue as Won't Fix Closed. Out of date and becoming irrelevant. Jenkins / JENKINS-10966 IRC notification in promotion process multiplies the number of channel everytime the job configure is saved Change By: Hua Zhang Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jacoco-plugin] (JENKINS-23066) Allow cleaning up parts of Jacoco report artifcats retained
Title: Message Title Hua Zhang commented on JENKINS-23066 Re: Allow cleaning up parts of Jacoco report artifcats retained Same here. Does anybody have a workaround in the mean time? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Hua Zhang commented on JENKINS-23693 Cannot delete workspace I added a screenshot of the job configuration. The input field "External Deletion Command" is empty, no whitespaces in there. And in config.xml: "ws-cleanup@0.20"> APPLICATION/artifacts INCLUDE true Nothing looks suspicious to me. I will try upgrade again to see if this is only an one-time issue. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Hua Zhang updated JENKINS-23693 Cannot delete workspace Change By: Hua Zhang (08/Jul/14 7:18 AM) Attachment: ws-cleanup-config.png This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Hua Zhang updated JENKINS-23693 Cannot delete workspace Change By: Hua Zhang (07/Jul/14 12:34 PM) Attachment: cannot-delete-workspace-config.zip This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Hua Zhang commented on JENKINS-23693 Cannot delete workspace Please find the configuration in attachment. No, I am not using any other external programs for cleanup. FWIW: the slaves are all Debian boxes (not VM), the master is a Debian VM, and JENKINS_HOME is on a NFS partition This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Hua Zhang
updated JENKINS-23693
Cannot delete workspace
Change By:
Hua Zhang
(07/Jul/14 12:31 PM)
Description:
After updating Jenkins from 1.567 to 1.570 and Workspace Cleanup Plugin from 0.20 to 0.21, all jobs using workspace cleanup are failing:{code}
...
00:00:
00.508 Baue auf Slave comitdev1 (karma git linux fast 64bit) in Arbeitsbereich /home/jenkins-slave/jenkins-slave-fs-root/workspace/SD-289300:00:00.508 00:00:00.508 Deleting project workspace... Using command: /home/jenkins-slave/jenkins-slave-fs-root/workspace/SD-2893/APPLICATION/artifacts 00:00:03.932 Using command: /home/jenkins-slave/jenkins-slave-fs-root/workspace/SD-2893/APPLICATION/artifacts 00:00:
06.
941 Using command: /home/jenkins-slave/jenkins-slave-fs-root/workspace/SD-2893/APPLICATION/artifacts 00:00:06.
943 Cannot delete workspace: java.io.IOException: Cannot run program "/home/jenkins-slave/jenkins-slave-fs-root/workspace/SD-2893/APPLICATION/artifacts": java.io.IOException: error=13, Permission denied00:00:06.945 ERROR: Cannot delete workspace: java.io.IOException: Cannot run program "/home/jenkins-slave/jenkins-slave-fs-root/workspace/SD-2893/APPLICATION/artifacts": java.io.IOException: error=13, Permission denied
00:00:06.945 [FINDBUGS] Skipping publisher since build result is FAILURE00:00:06.946 [PMD] Skipping publisher since build result is FAILURE...
{code}I have checked the workspace, everything looks ok, file permissions are all correct. Downgrade the plugin back to 0.20 fixed the problem.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [ws-cleanup] (JENKINS-23693) Cannot delete workspace
Hua Zhang created JENKINS-23693 Cannot delete workspace Issue Type: Bug Affects Versions: current Assignee: vjuranek Components: ws-cleanup Created: 07/Jul/14 6:47 AM Description: After updating Jenkins from 1.567 to 1.570 and Workspace Cleanup Plugin from 0.20 to 0.21, all jobs using workspace cleanup are failing: 00:00:06.943 Cannot delete workspace: java.io.IOException: Cannot run program "/home/jenkins-slave/jenkins-slave-fs-root/workspace/SD-2893/APPLICATION/artifacts": java.io.IOException: error=13, Permission denied 00:00:06.945 ERROR: Cannot delete workspace: java.io.IOException: Cannot run program "/home/jenkins-slave/jenkins-slave-fs-root/workspace/SD-2893/APPLICATION/artifacts": java.io.IOException: error=13, Permission denied I have checked the workspace, everything looks ok, file permissions are all correct. Downgrade the plugin back to 0.20 fixed the problem. Environment: Jenkins 1.570, workspace clean up plugin 0.2.1, Debian wheezy (master+slave) Project: Jenkins Priority: Major Reporter: Hua Zhang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds] (JENKINS-15947) Promoted builds *list* should also be requestable via REST
Hua Zhang commented on JENKINS-15947 Promoted builds *list* should also be requestable via REST This issue seems to have been (at least partially) fixed[1]. [1] https://github.com/jenkinsci/promoted-builds-plugin/commit/4f35bcfef3997f75949d08667236b909299f32a6 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-jira-issue-updater] (JENKINS-21514) Add fixed version support to jira issue updater plugin
Hua Zhang resolved JENKINS-21514 as Fixed Add fixed version support to jira issue updater plugin PR merged and released with version 1.7. Change By: Hua Zhang (17/Feb/14 1:51 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] [analysis-collector] (JENKINS-21803) Oops stacktrace on job screen
Hua Zhang
updated JENKINS-21803
Oops stacktrace on job screen
Change By:
Hua Zhang
(13/Feb/14 4:20 PM)
Description:
After upgrading static analysis plugin suite to the latest version (from the previous version), statcktrace shows on the job screen:{code}A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejavax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8899-jenkins.war-_jenkins-any-/webapp/WEB-INF/lib/jenkins-core-1.547.jar!/hudson/model/AbstractProject/main.jelly:79:66: hudson/plugins/checkstyle/CheckStyleProjectAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionC
[JIRA] [analysis-collector] (JENKINS-21803) Oops stacktrace on job screen
Hua Zhang
updated JENKINS-21803
Oops stacktrace on job screen
Change By:
Hua Zhang
(13/Feb/14 4:16 PM)
Description:
After upgrading static analysis plugin suite to the latest version
(from the previous version)
, statcktrace shows on the job screen:{code}A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened.Stack tracejavax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8899-jenkins.war-_jenkins-any-/webapp/WEB-INF/lib/jenkins-core-1.547.jar!/hudson/model/AbstractProject/main.jelly:79:66: hudson/plugins/checkstyle/CheckStyleProjectAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ApiTokenFilter.doFilter(ApiTokenFilter.java:64) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessio
[JIRA] [analysis-collector] (JENKINS-21803) Oops stacktrace on job screen
Hua Zhang created JENKINS-21803 Oops stacktrace on job screen Issue Type: Bug Assignee: Ulli Hafner Components: analysis-collector Created: 13/Feb/14 4:15 PM Description: After upgrading static analysis plugin suite to the latest version, statcktrace shows on the job screen: A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/tmp/jetty-0.0.0.0-8899-jenkins.war-_jenkins-any-/webapp/WEB-INF/lib/jenkins-core-1.547.jar!/hudson/model/AbstractProject/main.jelly:79:66: hudson/plugins/checkstyle/CheckStyleProjectAction at org.kohsuke.stapler.jelly.JellyClassTearOff.serveIndexJelly(JellyClassTearOff.java:117) at org.kohsuke.stapler.jelly.JellyFacet.handleIndexRequest(JellyFacet.java:127) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:717) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:248) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:728) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:858) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:631) at org.kohsuke.stapler.Stapler.service(Stapler.java:225) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:96) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:203) at net.bull.javamelody.MonitoringFilter.doFilter(MonitoringFilter.java:181) at net.bull.javamelody.PluginMonitoringFilter.doFilter(PluginMonitoringFilter.java:86) at org.jvnet.hudson.plugins.monitoring.HudsonMonitoringFilter.doFilter(HudsonMonitoringFilter.java:90) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:66) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:99) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:88) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) 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.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.basicauth.BasicProcessingFilter.doFilter(BasicProcessingFilter.java:174) at hudson.security.ChainedServletFilter$1.doFilter
[JIRA] [jenkins-jira-issue-updater] (JENKINS-21514) Add fixed version support to jira issue updater plugin
Hua Zhang assigned JENKINS-21514 to Laszlo Miklosik Add fixed version support to jira issue updater plugin Change By: Hua Zhang (11/Feb/14 8:43 AM) Assignee: Laszlo Miklosik This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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-jira-issue-updater] (JENKINS-21514) Add fixed version support to jira issue updater plugin
Hua Zhang created JENKINS-21514 Add fixed version support to jira issue updater plugin Issue Type: Improvement Assignee: Unassigned Attachments: jira-issue-update-pr.png Components: jenkins-jira-issue-updater Created: 27/Jan/14 1:57 PM Description: Pull request: https://github.com/jenkinsci/jira-issue-updater-plugin/pull/1 This PR added the possibility to update fixed versions of jira issues: appends the versions to / overwrites the original fixed versions environment/build variable substitution supported (as the plugin already did) non-applicable versions (since versions are project specific) are ignored, error messages are logged. Reviews and comments are greatly appreciated. Project: Jenkins Priority: Major Reporter: Hua Zhang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [analysis-core] (JENKINS-21510) Plugin result icons on build page are broken
Hua Zhang commented on JENKINS-21510 Plugin result icons on build page are broken Looks similar to JENKINS-6416. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [analysis-core] (JENKINS-21510) Plugin result icons on build page are broken
Hua Zhang created JENKINS-21510 Plugin result icons on build page are broken Issue Type: Bug Assignee: Ulli Hafner Attachments: status-icon-missing.png Components: analysis-core Created: 27/Jan/14 9:31 AM Description: The icon of plugin result on the build page is broken. Should be: https://my.jenkins.server/jenkins/static/bc778632/images/16x16/blue.png but was https://my.jenkins.server/static/bc778632/images/16x16/blue.png Jenkins URL in global configuration is https://my.jenkins.server/jenkins/ Jenkins is running on debian, started with "--prefix=/jenkins" and behind apache reverse proxy. Environment: Jenkins 1.547, analysis-core 1.54, pmd 3.37, findbugs 4.51, dry 2.38, tasks 4.38 Project: Jenkins Priority: Minor Reporter: Hua Zhang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang commented on JENKINS-18715 scandir being triggered by FingerPrint.save Please feel free to close the 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] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang commented on JENKINS-18715 scandir being triggered by FingerPrint.save Seems to me that the PR improves the performance a lot. At least for my situation, I cannot recognise the difference between with and without the include pattern. On the other hand, I also cannot confirm whether scandir still be triggered by the fingerprinting, or it is just fast enough. Anyway, the performance problem is gone. Thanks for the quick fix! This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang updated JENKINS-18715 scandir being triggered by FingerPrint.save Change By: Hua Zhang (13/Jul/13 6:55 AM) Environment: Jenkins 1.518 SCM Sync Configuration Plugin 0.0.7.1 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang commented on JENKINS-18715 scandir being triggered by FingerPrint.save The first test of this PR looks good. The fingerprinting was fast enough not giving me enough time to take a thread dump via GUI (next week I will be able to put this on field test). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang edited a comment on JENKINS-18715 scandir being triggered by FingerPrint.save Well, this behavior is documented in the online help (I didnt read it carefully enough), now I am not sure whether this is a bug or not. But improvement on this spot would be very desirable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang commented on JENKINS-18715 scandir being triggered by FingerPrint.save Well, this behavior is documented in the online help (I didnt read it carefully enough), now I am not sure whether this is a bug or not. But improvement on his spot would be very desirable. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang
updated JENKINS-18715
scandir being triggered by FingerPrint.save
Change By:
Hua Zhang
(11/Jul/13 4:19 PM)
Description:
We were experiencing extrem slow fingerprinting in post-build step. It turns out that the include pattern of scm sync configure plugin is triggered by FingerPrint.save() (details see discussion in mailing list[1]).
So the include pattern may significantly impact the speed.
Here is a thread dump:{code}Executor #1 for comitdev16 : executing SD-2112 #3" Id=62 Group=main RUNNABLE at java.io.UnixFileSystem.list(Native Method) at java.io.File.list(File.java:973) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1257) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1211) at org.apache.tools.ant.DirectoryScanner.checkIncludePatterns(DirectoryScanner.java:1030) at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:909) - locked org.apache.tools.ant.DirectoryScanner@34cf6c49 at hudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matchingFilesFrom(PatternsEntityMatcher.java:41) at hudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matches(PatternsEntityMatcher.java:25) at hudson.plugins.scm_sync_configuration.strategies.AbstractScmSyncStrategy.isSaveableApplicable(AbstractScmSyncStrategy.java:53) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getStrategyForSaveable(ScmSyncConfigurationPlugin.java:277) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationSaveableListener.onChange(ScmSyncConfigurationSaveableListener.java:22) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78) at hudson.model.Fingerprint.save(Fingerprint.java:862) - locked hudson.model.Fingerprint@281c2370 at hudson.model.Fingerprint.(Fingerprint.java:597) at hudson.model.FingerprintMap.create(FingerprintMap.java:90) at hudson.model.FingerprintMap.create(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.get(KeyedDataStorage.java:156) at hudson.model.FingerprintMap.get(FingerprintMap.java:79) at hudson.model.FingerprintMap.get(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.getOrCreate(KeyedDataStorage.java:108) at hudson.model.FingerprintMap.getOrCreate(FingerprintMap.java:65) at hudson.tasks.Fingerprinter$1Record.addRecord(Fingerprinter.java:210) at hudson.tasks.Fingerprinter.record(Fingerprinter.java:254) at hudson.tasks.Fingerprinter.perform(Fingerprinter.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241){code}I think reacting to all SaveableListener.fireOnChange might be too aggressive, since in this paticular case, no configuration changes are involved.[1] https://groups.google.com/forum/#!topic/jenkinsci-users/AftANOOYgt8
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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_
[JIRA] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang commented on JENKINS-18715 scandir being triggered by FingerPrint.save Careful use of the include pattern may avoid huge negative performance impact. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [scm-sync-configuration] (JENKINS-18715) scandir being triggered by FingerPrint.save
Hua Zhang created JENKINS-18715 scandir being triggered by FingerPrint.save Issue Type: Bug Assignee: Frédéric Camblor Components: scm-sync-configuration Created: 11/Jul/13 4:14 PM Description: We were experiencing extrem slow fingerprinting in post-build step. It turns out that the include pattern of scm sync configure plugin is triggered by FingerPrint.save() (details see discussion in mailing list[1]). So the include pattern may significantly impact the speed. Here is a thread dump: Executor #1 for comitdev16 : executing SD-2112 #3" Id=62 Group=main RUNNABLE at java.io.UnixFileSystem.list(Native Method) at java.io.File.list(File.java:973) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1257) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1287) at org.apache.tools.ant.DirectoryScanner.scandir(DirectoryScanner.java:1211) at org.apache.tools.ant.DirectoryScanner.checkIncludePatterns(DirectoryScanner.java:1030) at org.apache.tools.ant.DirectoryScanner.scan(DirectoryScanner.java:909) - locked org.apache.tools.ant.DirectoryScanner@34cf6c49 at hudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matchingFilesFrom(PatternsEntityMatcher.java:41) at hudson.plugins.scm_sync_configuration.strategies.model.PatternsEntityMatcher.matches(PatternsEntityMatcher.java:25) at hudson.plugins.scm_sync_configuration.strategies.AbstractScmSyncStrategy.isSaveableApplicable(AbstractScmSyncStrategy.java:53) at hudson.plugins.scm_sync_configuration.ScmSyncConfigurationPlugin.getStrategyForSaveable(ScmSyncConfigurationPlugin.java:277) at hudson.plugins.scm_sync_configuration.extensions.ScmSyncConfigurationSaveableListener.onChange(ScmSyncConfigurationSaveableListener.java:22) at hudson.model.listeners.SaveableListener.fireOnChange(SaveableListener.java:78) at hudson.model.Fingerprint.save(Fingerprint.java:862) - locked hudson.model.Fingerprint@281c2370 at hudson.model.Fingerprint.(Fingerprint.java:597) at hudson.model.FingerprintMap.create(FingerprintMap.java:90) at hudson.model.FingerprintMap.create(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.get(KeyedDataStorage.java:156) at hudson.model.FingerprintMap.get(FingerprintMap.java:79) at hudson.model.FingerprintMap.get(FingerprintMap.java:45) at hudson.util.KeyedDataStorage.getOrCreate(KeyedDataStorage.java:108) at hudson.model.FingerprintMap.getOrCreate(FingerprintMap.java:65) at hudson.tasks.Fingerprinter$1Record.addRecord(Fingerprinter.java:210) at hudson.tasks.Fingerprinter.record(Fingerprinter.java:254) at hudson.tasks.Fingerprinter.perform(Fingerprinter.java:133) at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:19) at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:804) at hudson.model.AbstractBuild$AbstractBuildExecution.performAllBuildSteps(AbstractBuild.java:776) at hudson.model.Build$BuildExecution.post2(Build.java:183) at hudson.model.AbstractBuild$AbstractBuildExecution.post(AbstractBuild.java:726) at hudson.model.Run.execute(Run.java:1601) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:46) at hudson.model.ResourceController.execute(ResourceController.java:88) at hudson.model.Executor.run(Executor.java:241) I think reacting to all SaveableListener.fireOnChange might be too aggressive, since in this paticular case, no configuration changes are involved. [1] https://groups.google.com/forum/#!topic/jenkinsci-users/AftANOOYgt8 Environment: Jenkins 1.518 Project: Jenkins Labels: fingerprints Priority: Minor
[JIRA] [jira] (JENKINS-18268) Error saving Jenkins config after updated to latest version of Jira Plugin
Hua Zhang commented on JENKINS-18268 Error saving Jenkins config after updated to latest version of Jira Plugin I also had a very similar problem with 1.36, the topmost exception is something else, but the root exception is the same "no protocol:" (can provide stacktrace if required). Downgrade to 1.35 also fixed the problem. I have Jenkins 1.517. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [promoted-builds] (JENKINS-9259) Include promotion status in the JSON/XML for a build
Hua Zhang edited a comment on JENKINS-9259 Include promotion status in the JSON/XML for a build One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine. I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks: job//promotion/latest//api/json and eventually information of every promoted build: job///promotion//promotionBuild//api/json But the response does not contain any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get. It would be nice if the following information could be exposed through remote access api: a) promotion status for each build, and/or b) a summary/history of all promotion builds with reference to the being promoted build number. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-9259) Include promotion status in the JSON/XML for a build
Hua Zhang
edited a comment on JENKINS-9259
Include promotion status in the JSON/XML for a build
One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine.
I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks:
{{job/[jobname]/promotion/latest/[PromotionName]/api/json}}
and eventually information of every promoted build:
{{job/[jobname]/[JobBuildNumber]/promotion/[PromotionName]/promotionBuild/[PromotionBuildNumber]/api/json}}
But the response does not contain any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get.
It would be nice if the following information could be exposed through remote access api:
a) promotion status for each build, and/or
b) a summary/history of all promotion builds with reference to the being promoted build number.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-9259) Include promotion status in the JSON/XML for a build
Hua Zhang
edited a comment on JENKINS-9259
Include promotion status in the JSON/XML for a build
One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine.
I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks:
{{ job/[jobname]/promotion/latest/[PromotionName]/api/json}}
and eventually information of every promoted build:
{{ job/[jobname]/[JobBuildNumber]/promotion/[PromotionName]/promotionBuild/[PromotionBuildNumber]/api/json}}
But the response does not contain any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get.
It would be nice if the following information could be exposed through remote access api:
a) promotion status for each build, and/or
b) a summary/history of all promotion builds with reference to the being promoted build number.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [promoted-builds] (JENKINS-9259) Include promotion status in the JSON/XML for a build
Hua Zhang edited a comment on JENKINS-9259 Include promotion status in the JSON/XML for a build One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine. I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks: job/[jobname]/promotion/latest/[PromotionName]/api/json and eventually information of every promoted build: job/[jobname]/[JobBuildNumber]/promotion/[PromotionName]/promotionBuild/num/api/json But the response does not contain any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get. It would be nice if the following information could be exposed through remote access api: a) promotion status for each build, and/or b) a summary/history of all promotion builds with reference to the being promoted build number. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sounds] (JENKINS-13825) Sounds plugin configuration "System command" is empty
Hua Zhang commented on JENKINS-13825 Sounds plugin configuration "System command" is empty I personally think auto-sense is a little bit better than Hudson.getVersion(). Or is it possible to reorgnize the config page, so that the same json structure can be produced for all versions? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] [sounds] (JENKINS-13825) Sounds plugin configuration "System command" is empty
Hua Zhang
edited a comment on JENKINS-13825
Sounds plugin configuration "System command" is empty
I also suspected that the reason might be the behaviour change of the XML serializaton in some underlying library. IIRC, the plugin config was broken after I upgraded Jenkins, not the plugin itself. My best guess is some version near 1.463 since I upgrade Jenkins quite frequently, so I tend to believe that this occurs between 1.45x - 1.463, of course I could very probably be wrong for its so long time ago.
I debugged against 1.460, the JSONObject is not a flat structure (was it before?), so playMethod is now a child node of the json object, therefore directly json.optString("systemCommand") would return null.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [sounds] (JENKINS-13825) Sounds plugin configuration "System command" is empty
Hua Zhang
commented on JENKINS-13825
Sounds plugin configuration "System command" is empty
I also suspected that the reason might be the behaviour change of the XML serializaton in some underlying library. IIRC, the plugin was broken after I upgraded Jenkins, not the plugin itself. My best guess is some version near 1.463 since I upgrade Jenkins quite frequently, so I tend to believe that this occurs between 1.45x - 1.463, of course I could very probably be wrong for its so long time ago.
I debugged against 1.460, the JSONObject is not a flat structure (was it before?), so playMethod is now a child node of the json object, therefore directly json.optString("systemCommand") would return null.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this 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] [sounds] (JENKINS-13825) Sounds plugin configuration "System command" is empty
Hua Zhang commented on JENKINS-13825 Sounds plugin configuration "System command" is empty It turns out to be a bug in the plugin itself, has nothing to do with core changes as I suspected. The parameters from configure page are not correctly retrieved from the json object. The attached patch should fix this bug, and it passed my local test. I also sent a pull quest https://github.com/jenkinsci/sounds-plugin/pull/2 unfortunately the pre-commit build failed due to some Maven issue: https://buildhive.cloudbees.com/job/jenkinsci/job/sounds-plugin/5/console This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [sounds] (JENKINS-13825) Sounds plugin configuration "System command" is empty
Hua Zhang updated JENKINS-13825 Sounds plugin configuration "System command" is empty Change By: Hua Zhang (18/May/13 8:20 AM) Attachment: FIXED-JENKINS13825-get-the-correct-parameters-from-J.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-9259) Include promotion status in the JSON/XML for a build
Hua Zhang edited a comment on JENKINS-9259 Include promotion status in the JSON/XML for a build One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine. I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks: job/[jobname]/promotion/latest/[PromotionName]/api/json and eventually information of every promoted build: job/[jobname]/[PromotionName]/promotion/[PromotionName]/promotionBuild/num/api/json But the response does not contain any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get. It would be nice if the following information could be exposed through remote access api: a) promotion status for each build, and/or b) a summary/history of all promotion builds with reference to the being promoted build number. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-9259) Include promotion status in the JSON/XML for a build
Hua Zhang commented on JENKINS-9259 Include promotion status in the JSON/XML for a build One of my projects depends heavily on the jsonp interface (pure xhtml/_javascript_), using jenkins as backend engine. I only discovered some promotion information accessible through json api: the latest promotion build number (not the build number of the job being promoted) from permalinks: job/[jobname]/promotion/latest/[PromotionName]/api/json and eventually information of every promoted build: job/[jobname]/[PromotionName]/promotion/[PromotionName]/promotionBuild/num/api/json But the response does not contain the any information related to build number of the origin job being promoted, so I basically cannot tell which build has been promoted by which promotion build, which is exactly the information I want to get. It would be nice if the following information could be exposed through remote access api: a) promotion status each build, and/or b) a summary/history of all promotion builds with reference to the being promoted build number. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-11972) Cannot create job with promoted build plugin automatically using jenkins API
Hua Zhang commented on JENKINS-11972 Cannot create job with promoted build plugin automatically using jenkins API We work around this by using CLI copy-job. The copy-job command does copy all promotion configurations. I suspect the sshd command would do the same, but I have not tested 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-15119) Duration sorting is incorrect in TestNG report
Hua Zhang commented on JENKINS-15119 Duration sorting is incorrect in TestNG report The sorting is now correct. 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
[JIRA] (JENKINS-13825) Sounds plugin configuration "System command" is empty
Hua Zhang commented on JENKINS-13825 Sounds plugin configuration "System command" is empty I think the stacktrace in the description was irrelevant to the sounds plugin, because that was clearly a problem of warning plugin, and there is no stacktrace any more in recent versions. IIRC, the plugin was broken since v1.463, in this version the new GUI feature was introduced. I suspect this change breaks the persistence of the plugin configuration. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15119) Duration sorting is incorrect in TestNG report
Hua Zhang updated JENKINS-15119 Duration sorting is incorrect in TestNG report TestNG results sorted by duration Change By: Hua Zhang (11/Sep/12 4:01 PM) Attachment: testng-sort-by-duration-1.png Attachment: testng-sort-by-duration-2.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
[JIRA] (JENKINS-15119) Duration sorting is incorrect in TestNG report
Hua Zhang created JENKINS-15119 Duration sorting is incorrect in TestNG report Issue Type: Bug Affects Versions: current Assignee: nalin_makar Components: testng Created: 11/Sep/12 3:59 PM Description: TestNG results (a freestyle job) are not currectly sorted by duration. See the screenshots. Test results are generated by TestNG 6.5.1. Environment: testng-plugin 0.32 Jenkins 1.478 Project: Jenkins Priority: Major Reporter: Hua Zhang This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-13825) Sounds plugin configuration "System command" is empty
[
https://issues.jenkins-ci.org/browse/JENKINS-13825?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hua Zhang reassigned JENKINS-13825:
---
Assignee: oxcafebabe
> Sounds plugin configuration "System command" is empty
> -
>
> Key: JENKINS-13825
> URL: https://issues.jenkins-ci.org/browse/JENKINS-13825
> Project: Jenkins
> Issue Type: Bug
> Components: sounds
> Environment: Jenkins 1.463, Jenkins Sounds plugin 0.4
>Reporter: Hua Zhang
>Assignee: oxcafebabe
>
> Jenkins 1.463, Jenkins Sounds Plugin 0.4.
> On the global configuration page, the value of input field "System command"
> is not saved. Set the value directly in
> {{net.hurstfrost.hudson.sounds.HudsonSoundsNotifier.xml}} and load config
> from disk seems to temporarily solve the problem. But eventually it becomes
> emtpy again if the configuration is changed and saved.
> Visiting the configure page causes the following stacktrace in log.
> {code}
> 18.05.2012 15:41:25 hudson.ExpressionFactory2$JexlExpression evaluate
> WARNUNG: Caught exception evaluating:
> descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason:
> java.lang.reflect.InvocationTargetException
> java.lang.reflect.InvocationTargetException
> at sun.reflect.GeneratedMethodAccessor502.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
> at
> org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
> at
> org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
> at
> org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
> at
> org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
> at
> org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
> at
> org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
> at
> org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
> at
> hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
> at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
> at
> org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
> at
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at
> org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
> at
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at
> org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
> at
> org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
> at org.apache.commons.je
[JIRA] (JENKINS-13825) Sounds plugin configuration "System command" is empty
Hua Zhang created JENKINS-13825:
---
Summary: Sounds plugin configuration "System command" is empty
Key: JENKINS-13825
URL: https://issues.jenkins-ci.org/browse/JENKINS-13825
Project: Jenkins
Issue Type: Bug
Components: sounds
Environment: Jenkins 1.463, Jenkins Sounds plugin 0.4
Reporter: Hua Zhang
Jenkins 1.463, Jenkins Sounds Plugin 0.4.
On the global configuration page, the value of input field "System command" is
not saved. Set the value directly in
{{net.hurstfrost.hudson.sounds.HudsonSoundsNotifier.xml}} and load config from
disk seems to temporarily solve the problem. But eventually it becomes emtpy
again if the configuration is changed and saved.
Visiting the configure page causes the following stacktrace in log.
{code}
18.05.2012 15:41:25 hudson.ExpressionFactory2$JexlExpression evaluate
WARNUNG: Caught exception evaluating:
descriptor.getPropertyType(instance,field).itemTypeDescriptorOrDie. Reason:
java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
at sun.reflect.GeneratedMethodAccessor502.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.apache.commons.jexl.util.PropertyExecutor.execute(PropertyExecutor.java:125)
at
org.apache.commons.jexl.util.introspection.UberspectImpl$VelGetterImpl.invoke(UberspectImpl.java:314)
at
org.apache.commons.jexl.parser.ASTArrayAccess.evaluateExpr(ASTArrayAccess.java:185)
at
org.apache.commons.jexl.parser.ASTIdentifier.execute(ASTIdentifier.java:75)
at
org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83)
at
org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57)
at
org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51)
at
org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80)
at
hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:72)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.ChooseTag.doTag(ChooseTag.java:38)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105)
at
org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:119)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at
org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:98)
at
org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.core.WhenTag.doTag(WhenTag.java:46)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:270)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:161)
at org.apache.commons.jelly.tags.
[JIRA] (JENKINS-11491) Email of Jenkins user should not be set from email of git user
[ https://issues.jenkins-ci.org/browse/JENKINS-11491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161749#comment-161749 ] Hua Zhang commented on JENKINS-11491: - We also have this problem, the user email is getting overwritten. In our case, this does not seem to be always happening, i didn't figure out when the email is getting overwritten, when not. > Email of Jenkins user should not be set from email of git user > -- > > Key: JENKINS-11491 > URL: https://issues.jenkins-ci.org/browse/JENKINS-11491 > Project: Jenkins > Issue Type: Bug > Components: git >Reporter: Elliot Winkler >Assignee: abayer >Priority: Minor > > Hi all - so it seems there are still some issues with how the git plugin > handles emails. Here's my particular case. All of the people in my company > have configured their git clients to use their personal email addresses, and > they use this even when committing to our company projects. I don't want to > them to have to reconfigure git to use their company email address because > some of us also have personal git projects we work on. However, I want emails > coming from Jenkins to go to their company email address. I was expecting > that if I create a user in Jenkins whose name matches the name portion of a > git author string, that would be good enough, and I could set the email of > that Jenkins user to whatever I wanted and Jenkins would send email to that > user. However, that does not seem to be happening -- the Jenkins user's email > is getting overwritten with the git author email every time. > I found a bug that was placed a while back, JENKINS-7156, for which this > behavior was implemented. I also realize that there have been a few other > related issues filed since then, and so what should happen when a git commit > is processed isn't so cut and dry. I just don't think the current behavior > makes sense -- there shouldn't be any reason that the git plugin should > overwrite what I set in Jenkins -- otherwise there's no point in being able > to set an email. Right? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
