[JIRA] [configure-job-column-plugin] (JENKINS-28050) Getting Error while Trying to save anything from any of the Jenkins jobs Configuration
Daniel Beck resolved JENKINS-28050 as Not A Defect Getting Error while Trying to save anything from any of the Jenkins jobs Configuration Unrelated to Configure Job Column Plugin. Enable Maven Plugin, it's a dependency of Job Config History, clearly documented on https://wiki.jenkins-ci.org/display/JENKINS/JobConfigHistory+Plugin Change By: Daniel Beck (23/Apr/15 6:53 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/d/optout.
[JIRA] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Daniel Beck commented on JENKINS-25340 lost trend history after skipping build Builds still need to be loaded from disk to show the tests, so nothing changed AFAICT. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28049) Cannot save job config with copyartifact step
Daniel Beck resolved JENKINS-28049 as Duplicate Cannot save job config with copyartifact step Change By: Daniel Beck (23/Apr/15 6:49 AM) Status: Open Resolved Assignee: Dominik Bartholdi Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Daniel Beck commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x The intention of the fix was to make it work with the original dpkg. If you worked around that by upgrading to a non-default dpkg, that's great, but irrelevant for this 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] [extended-choice-parameter-plugin] (JENKINS-28045) Provide predefined lists of values in Manage Jenkins -> Configure System
Daniel Beck commented on JENKINS-28045 Provide predefined lists of values in Manage Jenkins -> Configure System I'm not a maintainer of this plugin, but duplicating some kind of templating functionality (which could be offered much better in a dedicated plugin) in every plugin that has job-specific configuration makes little sense to me. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-26343) Workflow integration for HTMLPublisher
Oleg Nenashev started work on JENKINS-26343 Workflow integration for HTMLPublisher Change By: Oleg Nenashev (23/Apr/15 6:20 AM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [htmlpublisher-plugin] (JENKINS-26343) Workflow integration for HTMLPublisher
Oleg Nenashev assigned JENKINS-26343 to Oleg Nenashev Workflow integration for HTMLPublisher Change By: Oleg Nenashev (23/Apr/15 6:20 AM) Assignee: mcrooney Oleg Nenashev This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [delivery-pipeline-plugin] (JENKINS-28055) Pipeline arrows are not displaying or displayed incorrectly
Jan Vansteenkiste created JENKINS-28055 Pipeline arrows are not displaying or displayed incorrectly Issue Type: Bug Assignee: Patrik Boström Attachments: jenkins_layout_fail.png Components: delivery-pipeline-plugin Created: 23/Apr/15 6:16 AM Description: After the update to the latest LTS (v1.596.2), the arrows are no longer displaying correctly. Project: Jenkins Priority: Minor Reporter: Jan Vansteenkiste This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [active-directory-plugin] (JENKINS-13058) E-mail to individuals who broke the build is sent to wrong address
Markus closed JENKINS-13058 as Cannot Reproduce E-mail to individuals who broke the build is sent to wrong address I'm sorry, but we do not see this issue anymore and have not for years. I'll therefore close this as cannot reproduce since I as reporter cannot reproduce it. Given the time that has passed since I reported this, I suspect your problem would have a different root cause. (If this is a very wrong issue tracking methodology, then please let me know. I'll then reopen it.) Change By: Markus (23/Apr/15 6:14 AM) Status: Open Closed Resolution: Cannot Reproduce This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Oleg Nenashev commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive The issue has been caused by a binary stream corruption in Tar archiving procedures. https://github.com/jenkinsci/jenkins/pull/1667 has been created to revert the change This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Jan Vansteenkiste updated JENKINS-25666 Wrong view for build pipeline plugin dashboard view ui failure Change By: Jan Vansteenkiste (23/Apr/15 6:05 AM) Attachment: jenkins_layout_fail.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] [rebuild-plugin] (JENKINS-28054) Rebuild Plugin doesn't work with Repository Connector Plugin
Sandra Parsick
updated JENKINS-28054
Rebuild Plugin doesn't work with Repository Connector Plugin
Change By:
Sandra Parsick
(23/Apr/15 6:04 AM)
Description:
If the job contains Maven Repository Artifact parameters (see attachment Build.with.parameter.screen.png), rebuild plugin can't show them on its rebuild page (see attachment rebuild.last.screen.png). If, nonetheless, you try triggering a rebuild, a {{NullPointerException}} is thrown.
{code}
avax
javax
.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489) at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:960) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1021) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865) at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240) at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
[JIRA] [rebuild-plugin] (JENKINS-28054) Rebuild Plugin doesn't work with Repository Connector Plugin
Sandra Parsick created JENKINS-28054 Rebuild Plugin doesn't work with Repository Connector Plugin Issue Type: Bug Assignee: ragesh_nair Attachments: Build.with.parameter.screen.png, rebuild.last.screen.png Components: rebuild-plugin, repository-connector-plugin Created: 23/Apr/15 6:03 AM Description: If the job contains Maven Repository Artifact parameters (see attachment Build.with.parameter.screen.png), rebuild plugin can't show them on its rebuild page (see attachment rebuild.last.screen.png). If, nonetheless, you try triggering a rebuild, a NullPointerException is thrown. avax.servlet.ServletException: java.lang.NullPointerException at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$13.dispatch(MetaClass.java:411) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.util.CharacterEncodingFilter.doFilter(CharacterEncodingFilter.java:81) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.DiagnosticThreadNameFilter.doFilter(DiagnosticThreadNameFilter.java:30) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1474) at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:499) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:533) at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231) at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086) at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:428) at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193) at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020) at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116) at org.eclipse.jetty.server.Server.handle(Server.java:370) at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:489
[JIRA] [build-pipeline-plugin] (JENKINS-25666) Wrong view for build pipeline plugin
Jan Vansteenkiste reopened JENKINS-25666 Wrong view for build pipeline plugin With Jenkins v1.596.2, layout is broken again. Change By: Jan Vansteenkiste (23/Apr/15 6:01 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/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Andrey Regentov commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Oleg, positive. SLES 11, java 1.7.0_45-b18 - the problem appears. Not on every job though. But if the job is "cursed" then "Truncated TAR archive" on every its build. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [metadata-plugin] (JENKINS-26957) Metadata tag names containing underscores or dots break metadata searching
Bruno P. Kinoshita commented on JENKINS-26957 Metadata tag names containing underscores or dots break metadata searching Using spaces in the query doesn't break searching, but returns no results. For instance, any metadata string value element, with value equals "Sao Paulo" cannot be retrieved because of the space between Sao and Paulo. Looking at the Antlr tree, the query is parsed to something like = / \ /\ LOCATION Sao This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [metadata-plugin] (JENKINS-28053) Query parse errors are hidden from the user
Bruno P. Kinoshita created JENKINS-28053 Query parse errors are hidden from the user Issue Type: Improvement Assignee: rsandell Components: metadata-plugin Created: 23/Apr/15 2:08 AM Description: Using the plug-in with some metadata fields, and looking for something like LOCATION= Will raise an exception in Jenkins log similar to this one: line 0:-1 mismatched input '' expecting NAME com/sonyericsson/hudson/plugins/metadata/search/antlr/QueryWalker.g: node from line 0:0 no viable alternative at input 'LOCATION=' But in the user interface, all that the user gets is a "No jobs found" search result. It would be better if users received a feedback that their query is not valid. Project: Jenkins Priority: Major Reporter: Bruno P. Kinoshita This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [metadata-plugin] (JENKINS-28052) Support regular expressions in search
Bruno P. Kinoshita created JENKINS-28052 Support regular expressions in search Issue Type: Improvement Assignee: rsandell Components: metadata-plugin Created: 23/Apr/15 2:05 AM Description: It would be great if the plug-in supported regular expressions in the search metadata. For instance, instead of searching for LOCATION=Sao Paulo, I could look for LOCATION=*Paulo. Project: Jenkins Priority: Minor Reporter: Bruno P. Kinoshita This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [metadata-plugin] (JENKINS-28051) Creating a preset metadata value needs the job to be saved again to be applied
Bruno P. Kinoshita created JENKINS-28051 Creating a preset metadata value needs the job to be saved again to be applied Issue Type: Improvement Assignee: rsandell Components: metadata-plugin Created: 23/Apr/15 1:50 AM Description: If you have configured a job MY_JOB with some metadata, and then defined a preset metadata that must be applied to all jobs, your MY_JOB builds won't automatically include this new preset metadata, unless you save the job again. Project: Jenkins Priority: Minor Reporter: Bruno P. Kinoshita This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [configure-job-column-plugin] (JENKINS-28050) Getting Error while Trying to save anything from any of the Jenkins jobs Configuration
viral shah created JENKINS-28050 Getting Error while Trying to save anything from any of the Jenkins jobs Configuration Issue Type: Bug Assignee: Unassigned Components: configure-job-column-plugin Created: 23/Apr/15 1:41 AM Description: As soon as i try to save anything into jenkins Job configuration it is giving below Error. As i am seeing that issue from version after 1.596 and its keeps coming up everytime i tried to save anything in job config. however it is updating the config but everytime Oops page. it is now really a long timed and big issue . Please check it ASAP . avax.servlet.ServletException: java.lang.NoClassDefFoundError: hudson/maven/MavenModule at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:796) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.MetaClass$6.doDispatch(MetaClass.java:249) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:53) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:746) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:876) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:848) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:686) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1494) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:123) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:46) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.plugins.audit_trail.AuditTrailFilter.doFilter(AuditTrailFilter.java:95) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.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 jenkins.security.BasicHeaderProcessor.doFilter(BasicHeaderProcessor.java:93) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.context.HttpSessionContextIntegrationFilter.doFilter(HttpSessionContextIntegrationFilter.java:249) at hudson.security.HttpSessionContextIntegrationFilter2.doFilter(HttpSessionContextIntegrationFilter2.java:67) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:168) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at org.kohsuke.stapler.compression.CompressionFilter.doFilter(CompressionFilter.java:49) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(
[JIRA] [junit-plugin] (JENKINS-26153) JUnit missing builds
Brantone commented on JENKINS-26153 JUnit missing builds This looks like straight up dupe of JENKINS-25340 (not just "related to") Wonder if it's worth updating the Project Job page to use the workaround URL? 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/d/optout.
[JIRA] [junit-plugin] (JENKINS-25340) lost trend history after skipping build
Brantone commented on JENKINS-25340 lost trend history after skipping build If a work around is to hit `//lastCompletedBuild/testReport/history/countGraph/png?start=0&end=100` ... why not just update the Project Job page to use that?? Also, now that JENKINS-24380 is done and out the door, worth revisiting this sucker? Even if matter of swapping in the workaround 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] [promoted-builds-plugin] (JENKINS-27863) Please mention on the wiki that the promoted-builds UI will be missing for builds run before promotion added
John Tatum resolved JENKINS-27863 as Fixed Please mention on the wiki that the promoted-builds UI will be missing for builds run before promotion added I do not know whether to mark this as fixed or not a defect. Since the issue is an edit to the wiki and an edit has been made, I have marked the issue fixed. Change By: John Tatum (23/Apr/15 1:13 AM) Status: Open Resolved Assignee: John Tatum Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [promoted-builds-plugin] (JENKINS-27863) Please mention on the wiki that the promoted-builds UI will be missing for builds run before promotion added
John Tatum commented on JENKINS-27863 Please mention on the wiki that the promoted-builds UI will be missing for builds run before promotion added Edited wiki entry to italicize "and another build is run" and embolden "Note that this means that builds run before this point cannot be promoted." under Usage section. Removed duplicate entry under Usage section. Added the following under Notes: Note that after installing this plugin and configuring a promotion process, the option to promote the build will not be available for builds run before the promotion process was configured. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28032) Included Regions do not work when monitoring all branches
Jacek Sniecikowski
updated JENKINS-28032
Included Regions do not work when monitoring all branches
Change By:
Jacek Sniecikowski
(23/Apr/15 12:56 AM)
Description:
Set up a job to monitor all branches ('\*\*' in 'Branches to build') but restrict it to one folder ('Project1/.*' in 'Included Regions').As long as you make submissions to one branch, the included regions works fine.However, when you make a change on a different branch, the first job that triggers will ignore included regions and pick up changes from any location. After that the next jobs on the same branch will follow the restrictions correctly until a change on another branch is made.Here's part of my config.xml: 2g...@github.com:SomeAccount/1.git ff33d8db-ec3a-48d2-83cd-6d5cbd8f51a4 **false Project1/.*
Here's a part of the 'GitHub Hook log':Seen 51 remote branches > /usr/bin/git log --full-history --no-abbrev --format=raw -M -m --raw [edited change A] ..[edited change B] # timeout=10Ignored commit [edited change B]: Found only excluded paths: Done. Took 1.2 secChanges found
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Ayako Baba commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Same problem. java version "1.8.0_05" Java(TM) SE Runtime Environment (build 1.8.0_05-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed 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/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-28019) Some jobs not pulling in revisions at all
Alex Duncan commented on JENKINS-28019 Some jobs not pulling in revisions at all So unfortunately, building that version of the plugin did not fix the issue. Hopefully your new release will fix it. Please let me know if you have trouble reproducing this bug and I will do what I can to help. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [plot-plugin] (JENKINS-28025) Additional line style without indicated data points
SCM/JIRA link daemon commented on JENKINS-28025 Additional line style without indicated data points Code changed in jenkins User: Eric Nielsen Path: src/main/java/hudson/plugins/plot/Plot.java src/main/resources/hudson/plugins/plot/AbstractPlotPublisher/config.jelly src/main/webapp/help-style.html http://jenkins-ci.org/commit/plot-plugin/f2daef96b21bac10be6106658d204695592881cc Log: Merge pull request #18 from hjhafner/master [FIXED JENKINS-28025] Compare: https://github.com/jenkinsci/plot-plugin/compare/61cf86bb60aa...f2daef96b21b This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [plot-plugin] (JENKINS-28025) Additional line style without indicated data points
SCM/JIRA link daemon commented on JENKINS-28025 Additional line style without indicated data points Code changed in jenkins User: hjhafner Path: src/main/java/hudson/plugins/plot/Plot.java src/main/resources/hudson/plugins/plot/AbstractPlotPublisher/config.jelly src/main/webapp/help-style.html http://jenkins-ci.org/commit/plot-plugin/0b9bf55ec68dfd139ddbad79e9cf23f53190f1f2 Log: [FIXED JENKINS-28025] Added graph style "lineSimple" which is line without indicated data points This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [plot-plugin] (JENKINS-28025) Additional line style without indicated data points
SCM/JIRA link daemon resolved JENKINS-28025 as Fixed Additional line style without indicated data points Change By: SCM/JIRA link daemon (22/Apr/15 10:52 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28049) Cannot save job config with copyartifact step
Raphael Castaneda updated JENKINS-28049 Cannot save job config with copyartifact step Change By: Raphael Castaneda (22/Apr/15 10:40 PM) Attachment: jenkins_copyartifact_trace.txt This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-28049) Cannot save job config with copyartifact step
Raphael Castaneda updated JENKINS-28049 Cannot save job config with copyartifact step It looks like this is independent of the conditional build steps plugin. Any job with "copy artifact" fails to save. Change By: Raphael Castaneda (22/Apr/15 10:38 PM) Summary: Cannot save job config with conditional build step and copyartifact step Component/s: conditional-buildstep-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-environment-plugin] (JENKINS-22088) Disk space leak with multiple copies of winstone-XXXX.jar in TEMP folder
Amanda Xu commented on JENKINS-22088 Disk space leak with multiple copies of winstone-.jar in TEMP folder Hello There. I am running into the same problem. Is there a workaround? My Jenkins version is 1.542. Thanks in advanced. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [conditional-buildstep-plugin] (JENKINS-28049) Cannot save job config with conditional build step and copyartifact
Raphael Castaneda updated JENKINS-28049 Cannot save job config with conditional build step and copyartifact Change By: Raphael Castaneda (22/Apr/15 9:34 PM) Summary: Cannot save job config with conditional build step and copyartifact Component/s: copyartifact-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [conditional-buildstep-plugin] (JENKINS-28049) Cannot save job config with conditional build step
Raphael Castaneda
created JENKINS-28049
Cannot save job config with conditional build step
Issue Type:
Bug
Assignee:
Dominik Bartholdi
Attachments:
jenkins_conditional_buildstep_stacktrace.txt
Components:
conditional-buildstep-plugin
Created:
22/Apr/15 9:14 PM
Description:
After upgrade to Jenkins 1.610, I cannot save any job configurations if the job uses the conditional build step plugin.
Here is an excerpt from the stacktrace (see attached full stacktrace):
javax.servlet.ServletException: java.lang.RuntimeException: Failed to instantiate class org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder from {"":["3","0","0"],"condition":{"buildCause":"UPSTREAM_CAUSE","exclusiveCause":false,"stapler-class":"org.jenkins_ci.plugins.run_condition.core.CauseCondition","$class":"org.jenkins_ci.plugins.run_condition.core.CauseCondition"},"runner":{"stapler-class":"org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail","$class":"org.jenkins_ci.plugins.run_condition.BuildStepRunner$Fail"},"buildStep":{"projectName":"models platform build watcher","":"2","selector":{"fallback":true,"upstreamFilterStrategy":"UseGlobalSetting","kind":""},"filter":"latest_build.txt","excludes":"","target":"","parameters":"","flatten":false,"optional":false,"fingerprintArtifacts":true,"stapler-class":"hudson.plugins.copyartifact.CopyArtifact","$class":"hudson.plugins.copyartifact.CopyArtifact"},"stapler-class":"org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder","$class":"org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder"}
Environment:
Jenkins 1.610 on Ubuntu 14.04.2 LTS x64
Plugin info:
Active Directory plugin
This plugin enables authentication through Active Directory on Windows environment.
1.39
Downgrade to 1.38
Ant Plugin
This plugin adds Apache Ant support to Jenkins.
1.2
Build Failure Analyzer
This plugin analyzes the causes of failed builds and presents the causes on the build page. It does this by using a knowledge base of build failure causes that is built up from scratch. Saving statistics about failure causes is also possible.
1.13.0
Downgrade to 1.12.1
Build Monitor View
Provides a highly visible view of the status of selected Jenkins jobs. It easily accommodates different computer screen sizes and is ideal as an Extreme Feedback Device to be displayed on a screen on your office wall.
1.6+build.142
Downgrade to 1.6+build.138
build timeout plugin
This plugin allows builds to be automatically terminated after the specified amount of time has elapsed.
1.14.1
Downgrade to 1.14
build-environment
This plugin is a sample to explain how to write a Jenkins plugin.
1.4
build-name-setter
This plug-in sets the display name of a build to something other than #1, #2, #3, ...
1.3
buildgraph-view
This plugin visualize builds relations as a graph.
1.1.1
built-on-column
Shows the actual node that a job was built on
1.1
CloudBees Build Flow plugin
Manage jobs orchestration as a dedicated "build flow" top level item
0.17
Downgrade to 0.15
conditional-buildstep
A buildstep wrapping any number of other buildsteps, controlling their execution based on a defined condition (e.g. BuildParameter).
1.3.3
Configuration Slicing plugin
Perform mass configuration of select project properties, including email, timer, discard old builds, and Maven configuration.
1.40
Downgrade to 1.38.3
Configure Job Column Plugin
The Configure Job Column Plugin provides a fast-path configure job link available for views.
1.0
Confluence Publisher
This plugin allows you to publish build artifacts into a Confluence wiki page. Currently limited to uploading an artifact as an attachment to a page id.
1.8
Console Column Plugin
The Console Column Plugin provides a fast-path console link available for views.
1.5
[JIRA] [core] (JENKINS-27218) Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy
dogfood commented on JENKINS-27218 Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy Integrated in jenkins_main_trunk #4099 [FIXED JENKINS-27218] (Revision 342dc735b0df9e0be0e7e436ccc016bc6515e8e7) Result = SUCCESS kohsuke : 342dc735b0df9e0be0e7e436ccc016bc6515e8e7 Files : changelog.html core/src/main/resources/hudson/TcpSlaveAgentListener/index.jelly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24040) Excessive network load during build
Marko Käning commented on JENKINS-24040 Excessive network load during build I am seeing something similar for an OSX builder here, but I am told that this is normal... There is a constant network base-load of about 100-150 kB/s up- and downstream. Wondering what Jenkins is actually transferring at this rate between master and builder all the time with only short interruptions in between. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-24040) Excessive network load during build
Marko Käning edited a comment on JENKINS-24040 Excessive network load during build I am seeing something similar - but not during building, but rather when the builder is actually idle - for an OSX builder here, but I am told that this is normal... There is a constant network base-load of about 100-150 kB/s up- and downstream. Wondering what Jenkins is actually transferring at this rate between master and builder all the time with only short interruptions in between. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27571) Workflow Job: "Back to Project" link not navigating
Jesse Glick started work on JENKINS-27571 Workflow Job: "Back to Project" link not navigating Change By: Jesse Glick (22/Apr/15 8:22 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27571) Workflow Job: "Back to Project" link not navigating
Matthew Harrison commented on JENKINS-27571 Workflow Job: "Back to Project" link not navigating I'm seeing the same thing, running Jenkins 1.609, with workflow 1.5 on a Windows 2012 R2 server. The link I'm seeing is: Back to Project So looks like no href at all. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27218) Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy
SCM/JIRA link daemon resolved JENKINS-27218 as Fixed Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy Change By: SCM/JIRA link daemon (22/Apr/15 7:45 PM) Status: Open Resolved Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27218) Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy
SCM/JIRA link daemon commented on JENKINS-27218 Can't rely on hudson.TcpSlaveAgentListener.hostName to run JNLP slave with a reverse proxy Code changed in jenkins User: Kohsuke Kawaguchi Path: changelog.html core/src/main/resources/hudson/TcpSlaveAgentListener/index.jelly http://jenkins-ci.org/commit/jenkins/342dc735b0df9e0be0e7e436ccc016bc6515e8e7 Log: [FIXED JENKINS-27218] Advertise X-JNLP-Host-Name correctly This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27965) Can't trigger workflow job as job from freestyle or multijob project
Jesse Glick commented on JENKINS-27965 Can't trigger workflow job as job from freestyle or multijob project I am not sure what the Monitor plugin is, but its problem is probably unrelated. Check the 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/d/optout.
[JIRA] [core] (JENKINS-28043) Reload configs of all jobs in folder
Jesse Glick updated JENKINS-28043 Reload configs of all jobs in folder Are you sure this is reproducible? In which Jenkins version? It certainly should be reloading all jobs, everywhere, in any version I know about. Change By: Jesse Glick (22/Apr/15 7:23 PM) Labels: folders Assignee: Jesse Glick Component/s: core Component/s: cloudbees-folder-plugin This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Anthony Robinson commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x Still on the version that's in the standard repo: ii dpkg 1.15.5.6ubuntu4.5 Unfortunately, I can't (due to various policies) point to the non-standard repo. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Oleg Nenashev commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive I was unable to reproduce the issue on Java 6/7 and remote Windows/Ubuntu/Mac slaves. Massive load experiments didn't help as well. Does anybody see the issue on these Java versions? Probably, it could be something specific to Java8 or to the remoting behavior. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [job-dsl-plugin] (JENKINS-28048) Allow DslScriptLoader classloading customisation for reuse in other plug-ins
Damien Coraboeuf created JENKINS-28048 Allow DslScriptLoader classloading customisation for reuse in other plug-ins Issue Type: Improvement Assignee: Daniel Spilker Components: job-dsl-plugin Created: 22/Apr/15 6:54 PM Description: The DslScriptLoader class can be used from other plug-ins in order to bring the benefits of using the Job DSL capabilities. However, in the current state (version 1.32), the DslScriptLoader does not allow further configuration about the class loader, making impossible to inject helpers and other classes in the DSL script being run. The DslScriptLoader.runDslEngineForParent could be refactored in order to allow for further configuration. I'll try to propose a pull request for this - but I'd like to have some additional opinion on this. The context remains the reuse of the Job DSL capabilities from within another plug-in. Best regards, Damien. Environment: job-dsl 1.32 Project: Jenkins Priority: Major Reporter: Damien Coraboeuf This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [svn-tag-plugin] (JENKINS-28047) Make delay between delete and tag for source repository is synced between several instances
Aleksey Zvolinsky created JENKINS-28047 Make delay between delete and tag for source repository is synced between several instances Issue Type: Improvement Assignee: k2nakamura Components: svn-tag-plugin Created: 22/Apr/15 6:05 PM Description: We need to make wait before creating the tag and after delete old tag. It is required for case when source repository is synced between several instances and access to it is determined by geographical location, like the SVN repository at the Apache Software Foundation. Note: the similar problem had maven-release-plugin. Their solution is new parameter waitBeforeTagging -> http://maven.apache.org/maven-release/maven-release-plugin/prepare-mojo.html#waitBeforeTagging Environment: Jenkins 1.601; Subversion Plugin 2.4.5; Subversion Tagging Plugin 1.17 Project: Jenkins Labels: plugin subversion svn-tag svn Priority: Critical Reporter: Aleksey Zvolinsky This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [extensible-choice-parameter-plugin] (JENKINS-28046) Error: No stapler-class is specified
Ivan Stankov updated JENKINS-28046 Error: No stapler-class is specified Change By: Ivan Stankov (22/Apr/15 6:01 PM) Environment: Jenkins 1.610, Extensible Choice Parameter plugin 1.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/d/optout.
[JIRA] [extensible-choice-parameter-plugin] (JENKINS-28046) Error: No stapler-class is specified
Ivan Stankov created JENKINS-28046 Error: No stapler-class is specified Issue Type: Bug Assignee: Unassigned Components: extensible-choice-parameter-plugin Created: 22/Apr/15 5:55 PM Description: I installed latest jenkins 1.610 I installed Extensible Choice Parameter plugin 1.2.2. I created "Global Choice Parameter". I tried to use it in job "test" but when I save the job I see this error "No stapler-class is specified" Project: Jenkins Priority: Major Reporter: Ivan Stankov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [extended-choice-parameter-plugin] (JENKINS-28045) Provide predefined lists of values in Manage Jenkins -> Configure System
Ivan Stankov created JENKINS-28045 Provide predefined lists of values in Manage Jenkins -> Configure System Issue Type: Improvement Assignee: vimil Components: extended-choice-parameter-plugin Created: 22/Apr/15 5:45 PM Description: would be great to have a predefined lists in Manage Jenkins -> Configure System. And when you create a Extended choice parameter to select predefined list as source. I found a work around to have one job which creates config1.properties, config2.properties and then use parameter "Property File:" = http:///job//lastSuccessfulBuild/artifact/config1.properties "Property Key:" = list Here is similar plugin with such functionality, but I could configure it (it is old code base last upadte Dec 08, 2013) https://wiki.jenkins-ci.org/display/JENKINS/Extensible+Choice+Parameter+plugin Feature "Global Choice Provider" Please, let me know if such feature request make sense. Here is a Use Case: We use it to provide a list with server names and we have a lot of jobs. If I want to add one new server then I need to edit all the jobs. If this feature is implemented I could change only the global configuration. Also is there a way to export the default value list so I can use it later in build phase of the job as environment variable? Project: Jenkins Priority: Major Reporter: Ivan Stankov This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [ivytrigger-plugin] (JENKINS-28044) IveTrigger plugin description indicates that it "has no impact on the Jenkins infrastructure", but it does download all dependencies to the local file system
Robert Clark created JENKINS-28044 IveTrigger plugin description indicates that it "has no impact on the Jenkins infrastructure", but it does download all dependencies to the local file system Issue Type: Bug Assignee: Unassigned Components: ivytrigger-plugin Created: 22/Apr/15 5:42 PM Description: According to https://wiki.jenkins-ci.org/display/JENKINS/IvyTrigger+Plugin Note: The plugin uses only persistence in memory. There is no impact on the Jenkins infrastructure (no new files created). However, we've seen in practice that all depended-upon artifacts are downloaded to a ivy-trigger-cache directory outside the workspace. I'd expect that there would have to be some XML files downloaded and persisted between checks, but downloading all the depended-upon artifacts is really putting a strain on build machines handling multiple, very large, builds. I'm not sure if this is a requirement of the Ivy library, or if is really is possible to do a resolve without an implicit download. If it is however, that would be ideal for both my poor aching disks and for the network. Project: Jenkins Priority: Minor Reporter: Robert Clark This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [gradle-jpi-plugin] (JENKINS-27994) The Manifest of the job-dsl JAR is empty, making it unuseable for tests
SCM/JIRA link daemon commented on JENKINS-27994 The Manifest of the job-dsl JAR is empty, making it unuseable for tests Code changed in jenkins User: Damien Coraboeuf Path: src/main/groovy/org/jenkinsci/gradle/plugins/jpi/Jpi.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiManifest.groovy src/main/groovy/org/jenkinsci/gradle/plugins/jpi/JpiPlugin.groovy src/test/groovy/org/jenkinsci/gradle/plugins/jpi/JpiManifestSpec.groovy http://jenkins-ci.org/commit/gradle-jpi-plugin/ee38a8f14a7a1702c76a441fa9fc78c62deee8af Log: JENKINS-27994 Adding the manifest in the JAR This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloudbees-folder-plugin] (JENKINS-28043) Reload configs of all jobs in folder
Brantone created JENKINS-28043 Reload configs of all jobs in folder Issue Type: Bug Assignee: Jesse Glick Components: cloudbees-folder-plugin Created: 22/Apr/15 4:49 PM Description: If manual changes made to config.xml, hitting Jenkins > Manage > Reload Configuration from Disk does not seem to actually take jobs within the folder. Actually ... that may be a Jenkins core issue, worth checking though. Project: Jenkins Priority: Minor Reporter: Brantone This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [maven-plugin] (JENKINS-28042) Erro when commit using plugin maven scm
Rodrigo Macedo created JENKINS-28042 Erro when commit using plugin maven scm Issue Type: Bug Assignee: Rodrigo Macedo Components: maven-plugin Created: 22/Apr/15 3:40 PM Description: When the job runs and this job is no change files using the scm plugin maven, the following error occurs: [INFO] — maven-scm-plugin: 1.9.4: checkin (default-cli) @ sample-project — [INFO] Executing: / bin / sh -c cd / var / lib / jenkins / jobs / sample / workspace && svn --username redmine --password '*' --no-auth-cache --non -interactive commit --file /tmp/maven-scm-791942431.commit --targets / tmp / maven-scm-5538185210154714974-targets [INFO] Working directory: / var / lib / jenkins / jobs / sample / workspace [ERROR] Provider message: [ERROR] The svn command failed. [ERROR] Command output: [ERROR] svn: E215004: Authentication failed and interactive prompting is disabled; see the --force-interactive option svn: E215004: Commit failed (details follow): svn: E215004: Unable to connect to the repository at URL 'http: //svn.senfio.local/svn/senfio/software/sample/trunk/sample' svn: E215004: No more credentials or we tried too many times. Authentication failed I can guarantee that the problem is not of authentication because the checkout runs perfectly and is also not allowed to commit why I can do commit using IDE without problems. Environment: Jenkins 1.609 installed using apt-get ubuntu Project: Jenkins Labels: jenkins plugin maven3 Priority: Critical Reporter: Rodrigo Macedo This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-10385) FATAL: Could not checkout null with start point after a reset --hard to remove a commit
Loic Dachary commented on JENKINS-10385 FATAL: Could not checkout null with start point after a reset --hard to remove a commit I added a USD 500 bounty on this issue. https://freedomsponsors.org/issue/679/fatal-could-not-checkout-null-with-start-point-after-a-reset-hard-to-remove-a-commit This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cli] (JENKINS-28041) Allow delete-* CLI commands to operate on multiple arguments
Pavel Janoušek started work on JENKINS-28041 Allow delete-* CLI commands to operate on multiple arguments Change By: Pavel Janoušek (22/Apr/15 2:27 PM) Status: Open In Progress This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [cucumber-testresult-plugin] (JENKINS-27731) Exception while parsing result file
olivier destrebecq commented on JENKINS-27731 Exception while parsing result file I'm using calabash 0.14.0 for iOS And this is the command i use: cucumber test/cucumber -f junit -o ../../build/cucumberTests/ --tags @working -v This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cli] (JENKINS-28041) Allow delete-* CLI commands to operate on multiple arguments
Pavel Janoušek created JENKINS-28041 Allow delete-* CLI commands to operate on multiple arguments Issue Type: Improvement Assignee: Pavel Janoušek Components: cli, core Created: 22/Apr/15 2:18 PM Description: delete-job, delete-node and delete-view CLI commands accepts only one argument. Modify the commands in core to accept many. Project: Jenkins Priority: Major Reporter: Pavel Janoušek This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27965) Can't trigger workflow job as job from freestyle or multijob project
Thomas Dalton edited a comment on JENKINS-27965 Can't trigger workflow job as job from freestyle or multijob project Ok thanks for the explanation - it is a shame because I want to combine my workflow with build parameters Moreover the Monitor plugin (which I'd quite like to use) doesn't appear to recognise workflow jobs - could this be related too? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27677) SCM Polling does not run
Mark Waite resolved JENKINS-27677 as Won't Fix SCM Polling does not run Don't plan to fix this report. I can't duplicate it. Change By: Mark Waite (22/Apr/15 2:15 PM) Status: Open Resolved Resolution: Won't Fix This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27965) Can't trigger workflow job as job from freestyle or multijob project
Thomas Dalton commented on JENKINS-27965 Can't trigger workflow job as job from freestyle or multijob project That's odd because I wasn't trying a parameterized trigger directly - I thought I was trying a regular trigger! Though my setup does have the parameterized trigger plugin installed, could this be the cause? Moreover the Monitor plugin (which I'd quite like to use) doesn't appear to recognise workflow jobs - could this be related too? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Hi Mark, we currently prefer not to run via webhooks, because our tests (and deployments) take 20 minutes, and we get a few pushes per minute. In other words: we didn't want to overload our slaves (16 executors in total). We will re-evaluate a web-hook like system and also look into Gerrit and Zuul to limit the runtime. Thanks for your time. The ticket can be suspended. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27960) Snippet Generator for 'Bind Credentials to variables' blows up
Jesse Glick resolved JENKINS-27960 as Duplicate Snippet Generator for 'Bind Credentials to variables' blows up Change By: Jesse Glick (22/Apr/15 1:41 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27677) SCM Polling does not run
Mark Waite commented on JENKINS-27677 SCM Polling does not run Frank van Gemeren I don't know the code related to starvation threshold, so I can't help with that at all. If polling frequency is the concern, you may want to read the "polling must die" blog posting from Kohsuke Kawaguchi. He describes a technique which reduces polling dramatically and also reduces the time between a change being submitted and related jobs starting. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [config-file-provider-plugin] (JENKINS-26339) Workflow integration for Config File Provider
Jesse Glick commented on JENKINS-26339 Workflow integration for Config File Provider Requires a Jenkins LTS 1.599+ (so, the next one). The workaround is to use the Credentials Binding plugin with “secret file” credentials, as I guess you found. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-27965) Can't trigger workflow job as job from freestyle or multijob project
Jesse Glick resolved JENKINS-27965 as Duplicate Can't trigger workflow job as job from freestyle or multijob project Regular build triggers work, just not the ones from the Parameterized Trigger plugin, which is still calling old APIs. Change By: Jesse Glick (22/Apr/15 1:37 PM) Status: Open Resolved Resolution: Duplicate This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run Hi Mark, Thank you for your answer. I understand your position. I'll see if I can get approval for using the freedomsponsors option. We also have an in-house Java team so maybe I can use them to debug this further. In the meantime I have another, related, question: I just noticed that there's a hudson.triggers.SCMTrigger.starvationThreshold "hidden" feature with its default set to 1 hour (description is "Milliseconds waiting for polling executor before trigger reports it is clogged"). We do a lot of polling, so would extending it to 2 hours or more potentially fix this? If that's the case, maybe it makes sense to use a separate polling thread in the Jenkins core? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28034) SCM polling not using correct user credentials
Mark Waite commented on JENKINS-28034 SCM polling not using correct user credentials I don't understand that description. You say that you're using the credentials plugin, but also say that you're using a private key from $JENKINS_HOME/.ssh/. Are you using that private key by defining $JENKINS_HOME/.ssh/id_rsa as the source file for the private key in the credentials definition, or are you relying on the default behavior of command line git that it will find that private key if run on the master node? Another alternative you could test would be to see if the same behavior happens if you use JGit as the git implementation. You can enable JGit through the system configuration by adding a git implementation, then choose JGit. That will enable a drop down in the job which will let you change between "git" and "jgit" as the implementation. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [logstash-plugin] (JENKINS-28040) Allow logstash plugin to feed a syslog server
johmart created JENKINS-28040 Allow logstash plugin to feed a syslog server Issue Type: Improvement Assignee: Cyrille Le Clerc Components: logstash-plugin, syslog-logger-plugin Created: 22/Apr/15 1:05 PM Description: It would be nice to be able to send build logs to a syslog server. syslog-logger-plugin only sends Jenkins' own logs to the syslog server, logstash-plug will also send the console log, but not to a syslog server. Project: Jenkins Priority: Minor Reporter: johmart This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-14801) Node environment variable change not recognized
Aldrin Seychell commented on JENKINS-14801 Node environment variable change not recognized I encountered the same issue on version 1.608 - can you provide the link of the new bug? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27677) SCM Polling does not run
Mark Waite commented on JENKINS-27677 SCM Polling does not run Unfortunately, I don't think there is much you can do to change that (at least for me). Sorry about that. I think the investigation work will need to come from you. I can't duplicate your problem. I don't have a FreeBSD system in my git plugin / git client plugin test environment (only Windows 7 x86, Windows 7 x64, Windows 8.1 x64, Windows Home Server 2011 x64, Debian 6 x86, Debian 7 x64, Debian 8 x64, Ubuntu 14.04 x64, CentOS 6 x86, and CentOS 7 x64). I don't have a GitLab server in my test environment (only GitHub, gitweb, bitbucket, sourceforge, and a few others). I'm a volunteer who contributes to the plugins on my personal time, so you'd need to persuade me to use my personal time to work on a problem which I can't duplicate, and which has hints that it may be related to a local configuration problem. Some of the things I find most persuasive are things like: Expand the understanding of the platforms where the bug happens and does not happen, so that its impact to the larger community is more clear. If, for example, the problem also appears when using GitHub or bitbucket or a git protocol server on CentOS or Debian, that makes it more interesting to me Expand the understanding of the versions where the bug happens and does not happen, so that its impact to the larger community is more clear. If, for example, the problem also appears when using the most recent long term support release, that is more interesting to me, since I'm a user of the long term support release Expand the understanding of the conditions where the problem happens and does not happen, so that its impact to the larger community is more clear. If, for example, the problem does not appear when using git plugin 2.3.4 and does appear in 2.3.5, then that is very interesting, since it hints that there was a plugin version which behaved more the way you wanted If you'd rather have a more direct form of persuasion, you might be able to persuade others to investigate the problem by paying them to investigate. There is also freedomsponsors.org which provides a way to offer to fund a bug fix or investigation. I don't think my employer will allow me to take money for my personal development activities, so neither of those techniques will persuade me. It's not a personal thing, nor is it me saying that the problem you've found is not a bug. I hope that my description is not viewed as an attempt to offend or rebuff your concern. It is not. I'm trying to help you see which things might persuade others to help, and which will not. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [cloverphp-plugin] (JENKINS-28039) Clover PHP plugin does not provide data to the REST API
Dennis Claassen created JENKINS-28039 Clover PHP plugin does not provide data to the REST API Issue Type: Improvement Assignee: sogabe Components: cloverphp-plugin Created: 22/Apr/15 12:53 PM Description: Accessing data from the Clover PHP plugin is not possible via the REST API. The URL http://jenkins/job/test-job/1/cloverphp-report/api/xml returns a 404. Project: Jenkins Labels: plugin api rest php clover Priority: Major Reporter: Dennis Claassen This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
Jesse Glick updated JENKINS-26077 Multiple Test Reports Graphs and Links in Job Page Change By: Jesse Glick (22/Apr/15 12:50 PM) Labels: regression This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [junit-plugin] (JENKINS-26077) Multiple Test Reports Graphs and Links in Job Page
Jesse Glick assigned JENKINS-26077 to Jesse Glick Multiple Test Reports Graphs and Links in Job Page Change By: Jesse Glick (22/Apr/15 12:50 PM) Assignee: Gregory Boissinot 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/d/optout.
[JIRA] [git-plugin] (JENKINS-28034) SCM polling not using correct user credentials
Tobias Kremer commented on JENKINS-28034 SCM polling not using correct user credentials I am using Credential Plugin 1.22 The problem is the configured credentials are ignored when polling the repository. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28034) SCM polling not using correct user credentials
Mark Waite commented on JENKINS-28034 SCM polling not using correct user credentials Couldn't you instead use the Jenkins credentials plugin and let it manage the copying of the ssh information where it needs it, and when it needs it? The git plugin intentionally supports the credentials plugin so that users aren't required to manage ssh key files on the file systems of slaves. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [change-assembly-version-plugin] (JENKINS-25476) Encoding problem when writing file on windows.
Mattias Jiderhamn commented on JENKINS-25476 Encoding problem when writing file on windows. I'm seeing the same problem. I believe the reason is that Visual Studio not only uses UTF-8 encoding in the AssemblyInfo.cs/.vb files, but also adds a UTF-8 BOM (Byte Order Mark) at the beginning of the file. Seems that the change-assembly-version-plugin then fails to ignore the BOM and "converts" those bytes into "?" characters, which are written to the updated file. The workaround I found was to open the AssemblyInfo file in some text editor (TextPad in my case) and save as UTF-8 but without BOM. Then the plugin works. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [xshell-plugin] (JENKINS-28038) xshell should make itself available in "conditional build step" and "post-build actions" lists
Ed Randall created JENKINS-28038 xshell should make itself available in "conditional build step" and "post-build actions" lists Issue Type: Improvement Assignee: Unassigned Components: xshell-plugin Created: 22/Apr/15 12:13 PM Description: xshell-plugin appears only in the drop-down list of normal build steps. I want to run a script via xshell-plugin as a conditional build step but it doesn't register itself with conditional-buildstep so isn't available in the list there; Likewise I want to run an xshell script as a post-build action (so it doesn't affect the build status) but it isn't available in the list of available Post-Build Actions; Also I want to run it as a conditional post-build action (via flexible-publish-plugin) but it doesn't appear in the list of available actions there either. Environment: Jenkins-1.596.2 Xshell-0.10 Conditional-buildstep-1.3.3 Flexible-publish-plugin-0.14.1 Project: Jenkins Labels: xshell post-build flexible-publish conditional-buildstep Priority: Major Reporter: Ed Randall This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [packaging] (JENKINS-26240) Jenkins 1.595 cannot be installed on Ubuntu 10.04.x
Claus Westerkamp commented on JENKINS-26240 Jenkins 1.595 cannot be installed on Ubuntu 10.04.x @anthony what version of dpkg u got? I did the upgrade and could install 1.610 lsb_release -a Description: Ubuntu 10.04.4 LTS ii dpkg 1.16.1.2ubuntu Debian package management system ii jenkins1.610 continuous integration system This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-postbuild-plugin] (JENKINS-21924) Run groovy script for matrix parent builds
ikedam closed JENKINS-21924 as Fixed Run groovy script for matrix parent builds No. The feature should be still available. Create a new issue and report details and steps to reproduce the problem. Change By: ikedam (22/Apr/15 11:57 AM) Status: Reopened Closed Resolution: Fixed This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Fredrik Duprez commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive Same problem. Reverted to 1.609 solved it. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [warnings-plugin] (JENKINS-27377) Custom view does not display job warnings, displays '0'
Ulli Hafner commented on JENKINS-27377 Custom view does not display job warnings, displays '0' When you click on the 5 warnings link in image 36 do you then get to the build page in image 31? What is the warning count per axis in your build (image 31)? Did you change the number of axis in that build in the meantime? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [warnings-plugin] (JENKINS-28033) Warnings Plugin: The inconsistance between the totality warnings reported by Warnings Plugin and log files itself
Ulli Hafner commented on JENKINS-28033 Warnings Plugin: The inconsistance between the totality warnings reported by Warnings Plugin and log files itself Please attach one of your files that does not match. As already noted, duplicate warnings are skipped (same warning type, file and line number). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz commented on JENKINS-27948 Script timeout during start of configure a jenkins job Depending on the time, I configure as timeout value for the time a script may run, there are different _javascript_s active at the time the browser stops the script. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [groovy-plugin] (JENKINS-28037) Installing Groovy Plugin via CLI results in no Installs List
Kenneth Baltrinic updated JENKINS-28037 Installing Groovy Plugin via CLI results in no Installs List Change By: Kenneth Baltrinic (22/Apr/15 9:50 AM) Summary: Installing Groovy Plugin via CLI results in no Installs 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/d/optout.
[JIRA] [groovy-postbuild-plugin] (JENKINS-21924) Run groovy script for matrix parent builds
Martin Nonnenmacher reopened JENKINS-21924 Run groovy script for matrix parent builds I am using version 2.2 of the plugin and manager.addShortText does not add a label to the matrix parent job. Also the "Run also for matrix parent" checkbox as shown in the screenshot in the GitHub pull request is not there. Was the feature removed after release 1.9? Change By: Martin Nonnenmacher (22/Apr/15 9:50 AM) Resolution: Fixed Status: Closed Reopened This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [groovy-plugin] (JENKINS-28037) Groovy Plugin via CLI results in no Installs List
Kenneth Baltrinic created JENKINS-28037 Groovy Plugin via CLI results in no Installs List Issue Type: Bug Assignee: vjuranek Components: groovy-plugin Created: 22/Apr/15 9:49 AM Description: All of our deployments use Chef to manage the Jenkins instance. As a result all plugins get installed using the Jenkins CLI install-plugin command. When installed this way, the groovy plugin always ends up installed but with no hudson.plugins.groovy.GroovyInstaller file under /updates. This results in symptoms exactly like those reported in JENKINS-6085, including builds failing with the "Invalid tool ID" error. I have found that the solution is to go to the plugin-management/advanced tab and click the "Check Now" button to check for updates. This populates the needed file. I have never used the UI to install the groovy plug-in but I presume that this problem does not present itself in that situation or it would likely have been reported already. Environment: I've experienced this with versions as old as 1.585 through 1.609 with groovy plugin 1.23 and 1.24. Project: Jenkins Priority: Minor Reporter: Kenneth Baltrinic This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [envinject-plugin] (JENKINS-27895) Read a property from single value file
Florian Berger commented on JENKINS-27895 Read a property from single value file +1 for the original request. It would be extremly convenient to have that possibility. We currently invoke Python to creat a single-line temp file to be parsed by env-inject. One more failure point. We would love to skip that and use env-inject directly. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz commented on JENKINS-27948 Script timeout during start of configure a jenkins job Skript: http://sst-bld-master.sst.loca…/0da8a904/scripts/prototype.js:2188 It seems the script is calculating the size of the objects to display. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-27948) Script timeout during start of configure a jenkins job
Reiner Wirtz commented on JENKINS-27948 Script timeout during start of configure a jenkins job Excuse my late answer. I am glad that I can help. I started configuring the job I added in this call as example. The browser was about 3 minutes in the state loading data. At this time a call to the threadDump URL does not show a thread "Handling POST" or "configSubmit". The only Thread with Hanling was the threadDump itself. It look like jenkins generates _javascript_, which runs all the time in the browser. It seems it runs a lot longer, if there a more objects or lines to display. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-26440) svn: E200015: authentication cancelled (subversion plugin 2.5)
Laurent TOURREAU commented on JENKINS-26440 svn: E200015: authentication cancelled (subversion plugin 2.5) I confirm the issues with 1.609 subversion 2.5 too. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-27677) SCM Polling does not run
Frank van Gemeren commented on JENKINS-27677 SCM Polling does not run What can I do to change that? It's kinda annoying when we're moving to continuous integration and only a handful of our jobs that poll work (and even then not as often as they should). This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [extended-choice-parameter-plugin] (JENKINS-28035) Space delimiter is not supported
Noam Manos updated JENKINS-28035 Space delimiter is not supported Change By: Noam Manos (22/Apr/15 7:36 AM) Description: This plugin is very useful for multi-select parameters. However, when trying to pass the chosen parameters in a multi Configuration Matrix, using "Dynamic Axis plugin", the values must be separated by spaces. for example, setting optional values: file1.xml file2.xml,and having a default values choices, to get multiple parameters: file1.xml file2.xml.will pass a single parameter to the axis as: "file1.xml file2.xml". Please allow a space delimiter to be used.(by the way, I currently use Extensible Choice Parameter plugin, that can parse a multi-parameter with space delimiter, but your plugin has other advantages I preffer.) This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [testlink-plugin] (JENKINS-28036) Unable to mark Test execution using Jenkins TestLink plugin
Irfan Khaliq updated JENKINS-28036 Unable to mark Test execution using Jenkins TestLink plugin Change By: Irfan Khaliq (22/Apr/15 7:31 AM) Priority: Minor Critical This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [testlink-plugin] (JENKINS-28036) Unable to mark Test execution using Jenkins TestLink plugin
Irfan Khaliq created JENKINS-28036 Unable to mark Test execution using Jenkins TestLink plugin Issue Type: Bug Assignee: Bruno P. Kinoshita Components: testlink-plugin Created: 22/Apr/15 7:30 AM Description: I am trying to mark Test execution in TestLink. The list of test cases is retrieved correctly and it also looks like that the report generated by my testing tool is also identified correctly. But the execution is not marked and it is always Not Run. Console Log: Found 1 automated test cases in TestLink. Sorting automated test cases by TestLink test plan execution order. Executing single Build Steps. Merging build environment variables with data retrieved from TestLink. [TestJob_TestLink_Plugin_Integration] $ /bin/bash /tmp/hudson8712188314854337289.sh HelloWorld!!! TESTLINK_BUILD_NAME=b1 TESTLINK_TESTPLAN_NAME=Demo TESTLINK_TESTPROJECT_NAME=Dummy Project TESTLINK_TESTCASE_TOTAL=1 Executing iterative Build Steps. Looking for the test results of TestLink test cases. Looking for test results in JUnit suites by its name. Found 1 test result(s). Recording test results Notifying upstream projects of job completion Finished: SUCCESS TestLink Results Build ID: 1917 Build Name: b1 Passed: 0 Failed: 0 Blocked: 0 Not Run: 1 Total: 1 --- TestLink build ID: 1,917 TestLink build name: b1 Total of 1 tests. Where 0 passed, 0 failed, 0 were blocked and 1 were not executed. List of test cases and execution result status Test case ID Test case external ID Version Name Test project ID Execution status 174146 DUMMY-7 1 Verify that project can be built 171226 Not Run Environment: Jenkins ver. 1.554.1 TestLink Plugin v3.10 TestLink 1.9.9 Project: Jenkins Priority: Minor Reporter: Irfan Khaliq This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [gradle-jpi-plugin] (JENKINS-27826) Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test
Daniel Beck commented on JENKINS-27826 Getting java.lang.NoClassDefFoundError: hudson/matrix/MatrixRun error attempting to run a unit test java.lang.NoClassDefFoundError: hudson/tasks/test/AggregatedTestResultAction JUnit plugin was extracted from core in 1.577, so is not an explicit dependency of Matrix Project plugin, even though it's used by that. java.lang.InstantiationException: java.lang.NoClassDefFoundError: org/jenkinsci/plugins/scriptsecurity/sandbox/whitelists/ProxyWhitelist That's Script Security plugin, but I'm not sure how this gets involved. It only became a dependency of Matrix Project plugin in 1.2.1 and 1.4.1, and isn't in 1.4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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] [extended-choice-parameter-plugin] (JENKINS-28035) Space delimiter is not supported
Noam Manos created JENKINS-28035 Space delimiter is not supported Issue Type: Bug Assignee: vimil Components: extended-choice-parameter-plugin Created: 22/Apr/15 7:29 AM Description: This plugin is very useful for multi-select parameters. However, when trying to pass the chosen parameters in a multi Configuration Matrix, using "Dynamic Axis plugin", the values must be separated by spaces. Please allow a space delimiter to be used. (by the way, I currently use Extensible Choice Parameter plugin, that can parse a multi-parameter with space delimiter, but your plugin has other advantages I preffer.) Environment: Jenkins on Windows, with following plugins/versions: ant 1.2 antisamy-markup-formatter 1.3 any-buildstep 0.1 build-flow-plugin 0.17 build-name-setter 1.3 build-pipeline-plugin 1.4.7 build-timeout 1.14.1 conditional-buildstep 1.3.3 configure-job-column-plugin 1.0 copyartifact 1.35 credentials 1.22 cvs 2.12 dynamic-axis 1.0.3 dynamic_extended_choice_parameter 1.0.1 email-ext 2.39.3 envfile 1.2 envinject 1.91.2 extended-choice-parameter 0.36 extensible-choice-parameter 1.2.2 external-monitor-job 1.4 flexible-publish 0.15.1 git 2.3.5 git-client 1.16.1 groovyaxis 0.3 htmlpublisher 1.3 javadoc 1.3 jenkins-multijob-plugin 1.16 job-import-plugin 1.2 jobConfigHistory 2.11 jquery 1.7.2-1 junit 1.5 ldap 1.11 mailer 1.15 mapdb-api 1.0.6.0 matrix-auth 1.2 matrix-combinations-parameter 1.0.7 matrix-project 1.4.1 maven-plugin 2.9 nodelabelparameter 1.5.1 pam-auth 1.2 parameterized-trigger 2.26 robot 1.6.0 role-strategy 2.2.0 run-condition 1.0 scm-api 0.2 script-security 1.13 sidebar-link 1.6 ssh-credentials 1.11 ssh-slaves 1.9 subversion 2.5 test-results-analyzer 0.2.0 testng-plugin 1.10 timestamper 1.6 token-macro 1.10 translation 1.12 vncviewer 1.1 windows-slaves 1.0 ws-cleanup 0.25 Project: Jenkins Priority: Major Reporter: Noam Manos This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-28013) Archiving artifiacts fails with java.io.IOException: Truncated TAR archive
Frank Stiller commented on JENKINS-28013 Archiving artifiacts fails with java.io.IOException: Truncated TAR archive The problem is not coming up on every build. I started building 5 artifacts. 3 of them failed. Have now rolled back to 1.609 as they had the exact same 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 -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-plugin] (JENKINS-28034) SCM polling not using correct user credentials
Tobias Kremer created JENKINS-28034 SCM polling not using correct user credentials Issue Type: Bug Assignee: Nicolas De Loof Components: git-plugin Created: 22/Apr/15 7:14 AM Description: I deployed Jenkins as a docker container using a custom image. (I am using a custom image so my Jeknins server can build docker images.) I set up a Jenkins plan to build my git repo when it is changed. I set up repository polling as a trigger for the plan. The git repository is accessed via SSH. The plan itself works fine when triggered manually. But detecting changes in the repository fails. I checked the Poll-Log using the http://jenkinshost/job/jobname/scmPollLog endpoint and found a "permission denied" error. This was strange as the plan could checkout and build the repository when started manually. To authenticate with the git server I am using a key pair located in JENKINS_HOME/.ssh/. I do not use a key pair located in the user home (= default location) as I want to keep my keys when the docker container gets restarted. I was able to fixe my problem by logging in the container and creating a new key pair in the default location. When adding this pair to the allowed keys on the git server repository polling works. This makes me believe that the git plugin in is ignoring the key pair configured with the plan. Environment: Jenkins 1.596.2 Git Client Plugin 1.16.1 Git Plugin 1.16.1 Server running as a docker container (using custom image not "jenkins") Project: Jenkins Priority: Major Reporter: Tobias Kremer This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this 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.
