[JIRA] [nodelabelparameter-plugin] (JENKINS-27880) Expose NodeLabelParameter value in API
Title: Message Title SCM/JIRA link daemon commented on JENKINS-27880 Re: Expose NodeLabelParameter value in API Code changed in jenkins User: Charles Stephens Path: src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/LabelParameterValue.java http://jenkins-ci.org/commit/nodelabelparameter-plugin/9c137b8c6e1bbb60556870937f82ce318f29c38d Log: [FIXED JENKINS-27880] Expose value field for NodeLabelParameters Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-28374) NodeLabel vs Rebuild plugin - (pending—Waiting for next available executor)
Title: Message Title SCM/JIRA link daemon commented on JENKINS-28374 Re: NodeLabel vs Rebuild plugin - (pending—Waiting for next available executor) Code changed in jenkins User: imod Path: src/main/java/org/jvnet/jenkins/plugins/nodelabelparameter/NodeParameterDefinition.java http://jenkins-ci.org/commit/nodelabelparameter-plugin/2f943a16d1f55f1f6eb328a34ef348c69db3b800 Log: JENKINS-28374 add comment about issue Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31662) Check out of project wth svn:externals to files fails
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-31662 Check out of project wth svn:externals to files fails Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31662) Check out of project wth svn:externals to files fails
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31662 Re: Check out of project wth svn:externals to files fails M P, Could you provide the job configuration? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31455 Re: Build instability with "ISVNAuthentication provider did not provide credentials" Thomas Keller, I recommend you to upgrade to 2.5.4. Could you provide the job configuration? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31455) Build instability with "ISVNAuthentication provider did not provide credentials"
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-31455 Build instability with "ISVNAuthentication provider did not provide credentials" Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-22158) Wrong parsing of revision for externals causes infinite builds
Title: Message Title Manuel Jesús Recena Soto assigned an issue to Manuel Jesús Recena Soto Jenkins / JENKINS-22158 Wrong parsing of revision for externals causes infinite builds Change By: Manuel Jesús Recena Soto Assignee: Manuel Jesús Recena Soto Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-27726) git fetch fails when repository is checked out into a subdirectory
Title: Message Title armin novak commented on JENKINS-27726 Re: git fetch fails when repository is checked out into a subdirectory Couldn't this and the necessity for a checked out revision be solved by using the git ls-remote command? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mailer-plugin] (JENKINS-31700) Charset is ignored
Title: Message Title Sergey Shelomentsev created an issue Jenkins / JENKINS-31700 Charset is ignored Issue Type: Bug Assignee: Unassigned Components: mailer-plugin Created: 23/Nov/15 9:10 AM Environment: Linux ubuntussh 4.2.0-16-generic #19-Ubuntu SMP, openjdk version "1.8.0_66-internal", Jenkins v1.609.1, Mailer plugin v1.16 Priority: Minor Reporter: Sergey Shelomentsev If the MimeMessageBuilder is user to create MIME messages in from a third-party plugin, charset in ignored. Example: Charset: UTF-8 Set header "Build folder » job2 #11 is complete" In the source code looks like Subject: =?ANSI_X3.4-1968?Q?Build_folder_=3F_job2_#11_is_complete?= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii So, it's incorrectly displayed in mail clients.
[JIRA] [mailer-plugin] (JENKINS-31700) Charset is ignored
Title: Message Title
Sergey Shelomentsev updated an issue
Jenkins / JENKINS-31700
Charset is ignored
Change By:
Sergey Shelomentsev
If the MimeMessageBuilder is user to create MIME messages in from a third-party plugin, charset in ignored.Example:Charset: UTF-8Set header "Build folder » job2 #11 is complete"In the source code of the message it looks like {noformat}Subject: =?ANSI_X3.4-1968?Q?Build_folder_=3F_job2_#11_is_complete?=MIME-Version: 1.0Content-Type: text/plain; charset=us-ascii{noformat}So, it's incorrectly displayed in mail clients.
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-25622) NodeLabelParameter plugin is missing value parameter for queue jobs
Title: Message Title Dominik Bartholdi resolved as Fixed implemented with 1.6 Jenkins / JENKINS-25622 NodeLabelParameter plugin is missing value parameter for queue jobs Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-26905) NodeLabelParameter plugin is missing VALUE for parameter in API
Title: Message Title Dominik Bartholdi resolved as Fixed implemented with 1.6 Jenkins / JENKINS-26905 NodeLabelParameter plugin is missing VALUE for parameter in API Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [nodelabelparameter-plugin] (JENKINS-28374) NodeLabel vs Rebuild plugin - (pending—Waiting for next available executor)
Title: Message Title Dominik Bartholdi resolved as Fixed implemented with 1.6 Jenkins / JENKINS-28374 NodeLabel vs Rebuild plugin - (pending—Waiting for next available executor) Change By: Dominik Bartholdi Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [blamesubversion-plugin] (JENKINS-21154) UpDownStreamNumberSychronizedNotify no longer works in 1.532.1
Title: Message Title Sven S. commented on JENKINS-21154 Re: UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 Teh problem still exists within 1.638. Once a pipeline has been created and if the UpDownStreamNumberSychronizedNotify was set once the error can not be removed by removing UpDownStreamNumberSychronizedNotify. This is a really blocker for us, because for the moment we have a build-server with many such jobs which are now broken. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [blamesubversion-plugin] (JENKINS-21154) UpDownStreamNumberSychronizedNotify no longer works in 1.532.1
Title: Message Title Sven S. updated an issue Jenkins / JENKINS-21154 UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 Change By: Sven S. Component/s: parameterized-trigger-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [blamesubversion-plugin] (JENKINS-21154) UpDownStreamNumberSychronizedNotify no longer works in 1.532.1
Title: Message Title Sven S. edited a comment on JENKINS-21154 Re: UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 Teh The problem still exists within 1.638. Once a pipeline has been created and if the UpDownStreamNumberSychronizedNotify was set once the error can not be removed by removing UpDownStreamNumberSychronizedNotify. This is a really blocker for us, because for the moment we have a build-server with many such jobs which are now broken. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31701) workflow-multibranch Jenkinsfile: "Sleep 60" causes "RejectedAccessException: Scripts not permitted to use"
Title: Message Title Cyrille Le Clerc created an issue Jenkins / JENKINS-31701 workflow-multibranch Jenkinsfile: "Sleep 60" causes "RejectedAccessException: Scripts not permitted to use" Issue Type: Bug Assignee: Jesse Glick Attachments: about.md, config-workflow-multibranch.xml Components: workflow-plugin Created: 23/Nov/15 9:50 AM Environment: Jenkins ver. 1.609.14.1 (CloudBees Jenkins Enterprise 15.05) Labels: plugin Priority: Minor Reporter: Cyrille Le Clerc org.jenkinsci.plugins.scriptsecurity.sandbox.RejectedAccessException: Scripts not permitted to use method groovy.lang.GroovyObject invokeMethod java.lang.String java.lang.O
[JIRA] [gitlab-plugin] (JENKINS-28090) gitlab plugin causing configure job option to fail
Title: Message Title
Predrag Pramenko commented on JENKINS-28090
Re: gitlab plugin causing configure job option to fail
Similar problem with WindowsServer
{{ javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Jenkins/plugins/gitlab-plugin/WEB-INF/lib/gitlab-plugin-1.1.24.jar!/com/dabsquared/gitlabjenkins/GitLabPushTrigger/config.jelly:28:87: method getProjectBranches threw exception: java.io.IOException: {"message":"401 Unauthorized"}
at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) 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.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) 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.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection
[JIRA] [gitlab-plugin] (JENKINS-28090) gitlab plugin causing configure job option to fail
Title: Message Title
Predrag Pramenko edited a comment on JENKINS-28090
Re: gitlab plugin causing configure job option to fail
Similar problem with WindowsServer{{ javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Jenkins/plugins/gitlab-plugin/WEB-INF/lib/gitlab-plugin-1.1.24.jar!/com/dabsquared/gitlabjenkins/GitLabPushTrigger/config.jelly:28:87: method getProjectBranches threw exception: java.io.IOException: {"message":"401 Unauthorized"} at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) 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.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) 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.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:64
[JIRA] [gitlab-plugin] (JENKINS-28090) gitlab plugin causing configure job option to fail
Title: Message Title
Predrag Pramenko edited a comment on JENKINS-28090
Re: gitlab plugin causing configure job option to fail
Similar problem with WindowsServer : --- javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Jenkins/plugins/gitlab-plugin/WEB-INF/lib/gitlab-plugin-1.1.24.jar!/com/dabsquared/gitlabjenkins/GitLabPushTrigger/config.jelly:28:87: method getProjectBranches threw exception: java.io.IOException: {"message":"401 Unauthorized"} at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) 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.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) 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.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.jav
[JIRA] [gitlab-plugin] (JENKINS-28090) gitlab plugin causing configure job option to fail
Title: Message Title
Predrag Pramenko edited a comment on JENKINS-28090
Re: gitlab plugin causing configure job option to fail
Similar problem with WindowsServer {{ javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/C:/Jenkins/plugins/gitlab-plugin/WEB-INF/lib/gitlab-plugin-1.1.24.jar!/com/dabsquared/gitlabjenkins/GitLabPushTrigger/config.jelly:28:87: method getProjectBranches threw exception: java.io.IOException: {"message":"401 Unauthorized"} at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) 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.plugins.greenballs.GreenBallFilter.doFilter(GreenBallFilter.java:58) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:120) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:114) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:48) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1482) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.ChainedServletFilter.doFilter(ChainedServletFilter.java:76) at hudson.security.HudsonFilter.doFilter(HudsonFilter.java:171) 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.headerComplete(AbstractHttpConnection.java:949) at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:1011) at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:64
[JIRA] [release-plugin] (JENKINS-31702) Post successful build steps are executed when build fails
Title: Message Title Marcus Klein created an issue Jenkins / JENKINS-31702 Post successful build steps are executed when build fails Issue Type: Bug Assignee: Peter Hayes Components: release-plugin Created: 23/Nov/15 9:56 AM Environment: Standalone Jenkins 1.638 with release plugin 2.5.4 Labels: plugin Priority: Critical Reporter: Marcus Klein First build step was to copy artifacts from another job. This build step failed. Configured post successful build steps of the release plugin are executed anyway. But they should not be executed in my eyes when some build step fails. Do you have any hints how to debug this?
[JIRA] [release-plugin] (JENKINS-31702) Post successful build steps are executed when build fails
Title: Message Title Marcus Klein commented on JENKINS-31702 Re: Post successful build steps are executed when build fails I use the Git Publisher plugin as post successful build step. This plugin offers as first option to push only if build succeeds. But this option is broken, too. It fails with a NullPointerException: https://issues.jenkins-ci.org/browse/JENKINS-31678 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [release-plugin] (JENKINS-31702) Post successful build steps are executed when build fails
Title: Message Title Marcus Klein edited a comment on JENKINS-31702 Re: Post successful build steps are executed when build fails I use the Git Publisher plugin as post successful build step. This plugin offers as first option to push only if build succeeds. But this option is broken, too. It fails with a NullPointerException: https://issues.jenkins-ci.org/browse/JENKINS-31678 So there is currently no possibility to push to Git only when the build succeeds. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [mercurial-plugin] (JENKINS-14996) Jenkins does not find Mercurial that is on the PATH
Title: Message Title Artem Alexandrov commented on JENKINS-14996 Re: Jenkins does not find Mercurial that is on the PATH Affected too, I was making a workaround to make hg work by creating a symlink in /usr/bin from /usr/local/bin, but since mac 10.11 it's not possible. It's SIP doesn't allow to write into /usr/bin. And I'm not able to turn off SIP. Please fix ASAP. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-31686) Jenkins injects the old git commit as GIT_COMMIT env variable
Title: Message Title Kowal Cj0 commented on JENKINS-31686 Re: Jenkins injects the old git commit as GIT_COMMIT env variable I'm running the latest available versions of all of those plugins: GIT client plugin=1.19.0 GIT plugin=2.4.0 GitHub API Plugin=1.69 Github Authentication plugin=0.22.2 GitHub plugin=1.14.0 GitHub Pull Request Builder=1.29.4 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-28945) Lightbox view mode of console output won't show
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-28945 Re: Lightbox view mode of console output won't show Dan Alvizu, Did you try this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-stability-plugin] (JENKINS-31660) StackOverflowError when maximum number of builds archived
Title: Message Title Dave Hunt updated an issue Jenkins / JENKINS-31660 StackOverflowError when maximum number of builds archived Full console text attached. Change By: Dave Hunt Attachment: consoleText Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-stability-plugin] (JENKINS-31660) StackOverflowError when maximum number of builds archived
Title: Message Title Dave Hunt commented on JENKINS-31660 Re: StackOverflowError when maximum number of builds archived which versions do you have in use (Jenkins and especially junit-plugin) Jenkins: 1.625.2 JUnit Plugin: 1.9 Test Stability History: 1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-name-setter-plugin] (JENKINS-10613) The build name setter does not work for multi-configuration jobs
Title: Message Title Marek Martyniak commented on JENKINS-10613 Re: The build name setter does not work for multi-configuration jobs I have the issue. Jenkins ver. 1.624. Plugin ver. 1.5.1. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-name-setter-plugin] (JENKINS-10613) The build name setter does not work for multi-configuration jobs
Title: Message Title Marek Martyniak edited a comment on JENKINS-10613 Re: The build name setter does not work for multi-configuration jobs I have the same issue. Jenkins ver. 1.624. Plugin ver. 1.5.1. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ecutest-plugin] (JENKINS-31703) Incorrect form validation for some ATX settings
Title: Message Title TraceTronic GmbH created an issue Jenkins / JENKINS-31703 Incorrect form validation for some ATX settings Issue Type: Bug Assignee: TraceTronic GmbH Attachments: form_validation.png Components: ecutest-plugin Created: 23/Nov/15 11:06 AM Priority: Minor Reporter: TraceTronic GmbH The form validation for the ATX settings "Archive Misc Files" and "Covered Attributes" is incorrect in case of using single wildcards (*) or custom package attributes (see screenshot). Add Comment
[JIRA] [acceptance-test-harness] (JENKINS-31648) ATH Tests for Folder Plugin: Folder creation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31648 Re: ATH Tests for Folder Plugin: Folder creation Code changed in jenkins User: Andres Rodriguez Path: src/main/java/org/jenkinsci/test/acceptance/po/FolderJob.java src/test/java/plugins/FolderPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/f09d012f17269e42964d2be14340a9b27a8ee28e Log: JENKINS-31648 First acceptance test for Folder plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-31648) ATH Tests for Folder Plugin: Folder creation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31648 Re: ATH Tests for Folder Plugin: Folder creation Code changed in jenkins User: Andres Rodriguez Path: src/main/java/org/jenkinsci/test/acceptance/po/FolderJob.java src/test/java/plugins/FolderPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/629e778f62c907553237cdea2013a97a1b930ad4 Log: JENKINS-31648 Fix license comments, indentation and review javadoc. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-31648) ATH Tests for Folder Plugin: Folder creation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31648 Re: ATH Tests for Folder Plugin: Folder creation Code changed in jenkins User: Oliver Gondža Path: src/main/java/org/jenkinsci/test/acceptance/po/FolderItem.java src/main/java/org/jenkinsci/test/acceptance/po/Job.java src/main/java/org/jenkinsci/test/acceptance/po/JobsMixIn.java src/main/java/org/jenkinsci/test/acceptance/po/TopLevelItem.java src/test/java/plugins/FolderPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/95ca6f1161ca6d53b2f46da0719c689a494e213f Log: Merge pull request #58 from andresrc/JENKINS-31648 JENKINS-31648 First acceptance test for Folder plugin. Compare: https://github.com/jenkinsci/acceptance-test-harness/compare/92f50950fb83...95ca6f1161ca Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-31648) ATH Tests for Folder Plugin: Folder creation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31648 Re: ATH Tests for Folder Plugin: Folder creation Code changed in jenkins User: Andres Rodriguez Path: src/main/java/org/jenkinsci/test/acceptance/po/FolderItem.java src/main/java/org/jenkinsci/test/acceptance/po/FolderJob.java src/main/java/org/jenkinsci/test/acceptance/po/Job.java src/main/java/org/jenkinsci/test/acceptance/po/JobsMixIn.java src/main/java/org/jenkinsci/test/acceptance/po/TopLevelItem.java src/test/java/plugins/FolderPluginTest.java http://jenkins-ci.org/commit/acceptance-test-harness/e2c9d9a087762a7a44d51cf44c856bd020ffcd33 Log: JENKINS-31648 Introduce TopLevelItem abstraction. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [deploy-plugin] (JENKINS-21187) Change context path of manager app to deploy war file to.
Title: Message Title Nacho Nogueira commented on JENKINS-21187 Re: Change context path of manager app to deploy war file to. More than a year old. Is there an alternative way of doing this? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [test-results-analyzer-plugin] (JENKINS-30992) Generate Build Report button does not include all past builds
Title: Message Title Tomasz Kosiński commented on JENKINS-30992 Re: Generate Build Report button does not include all past builds In version 0.2.3 of the plugin this problem appears to be resolved. I see my results rendered for all builds. Still not sure if it is correctly picking junit test or it started picking testNG results as support for this has been added in this new version of plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-31648) ATH Tests for Folder Plugin: Folder creation
Title: Message Title Andres Rodriguez resolved as Fixed Jenkins / JENKINS-31648 ATH Tests for Folder Plugin: Folder creation Change By: Andres Rodriguez Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-1304) Add a "Use Export" option to the Subversion config section of a job
Title: Message Title Alex Vesely commented on JENKINS-1304 Re: Add a "Use Export" option to the Subversion config section of a job This would be perfect for my use-case as well. I always use a clean checkout, so "export" would save time, space and network bandwidth compared to "checkout". Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ecutest-plugin] (JENKINS-31703) Incorrect form validation for some ATX settings
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31703 Re: Incorrect form validation for some ATX settings Code changed in jenkins User: Christian Pönisch Path: src/main/java/de/tracetronic/jenkins/plugins/ecutest/util/validation/ATXValidator.java src/main/resources/de/tracetronic/jenkins/plugins/ecutest/report/atx/Messages.properties src/main/resources/de/tracetronic/jenkins/plugins/ecutest/report/atx/Messages_de.properties src/test/java/de/tracetronic/jenkins/plugins/ecutest/util/validation/ATXValidatorTest.java http://jenkins-ci.org/commit/ecutest-plugin/8ea43015567967ec2a1bc653b1a2bafb5063986d Log: JENKINS-31703 fixed ATX form validation Compare: https://github.com/jenkinsci/ecutest-plugin/compare/33bac910cd44...8ea430155679 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [copyartifact-plugin] (JENKINS-14999) Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter
Title: Message Title Shane Gannon commented on JENKINS-14999 Re: Copy Artifact plugin: Unable to find project for artifact copy when using a build parameter In Jenkins ver. 1.609.3 with Copy Artifact Plugin 1.36.1 I hit this issue. As a workaround if I set Permission to Copy Artifact - Projects to allow copy artifacts to * the problem is resolved. But this is still a bug. It should not behave differently depending on whether the job name is hard coded or comes from a parameter. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [blamesubversion-plugin] (JENKINS-21154) UpDownStreamNumberSychronizedNotify no longer works in 1.532.1
Title: Message Title Sven S. edited a comment on JENKINS-21154 Re: UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 The problem still exists within 1.638. Once a pipeline has been created and if the UpDownStreamNumberSychronizedNotify was set once the error can not be removed by removing UpDownStreamNumberSychronizedNotify. This is a really blocker for us, because for the moment we have a build-server with many such jobs which are now broken. After further investigations, I found out, this problem can be temporary fixed by removing the UpDownStreamNumberSychronizedNotify and then restarting the jenkins itself. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [blamesubversion-plugin] (JENKINS-21154) Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized build will lead to a non working pipeline
Title: Message Title Sven S. updated an issue Jenkins / JENKINS-21154 Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized build will lead to a non working pipeline Change By: Sven S. Summary: Usage of UpDownStreamNumberSychronizedNotify no longer works in 1.532.1 conjunction with parameterized build will lead to a non working pipeline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [blamesubversion-plugin] (JENKINS-21154) Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized-trigger-plugin will lead to a non working pipeline
Title: Message Title Sven S. updated an issue Jenkins / JENKINS-21154 Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized-trigger-plugin will lead to a non working pipeline Change By: Sven S. Summary: Usage of UpDownStreamNumberSychronizedNotify in conjunction with parameterized build -trigger-plugin will lead to a non working pipeline Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ecutest-plugin] (JENKINS-31703) Incorrect form validation for some ATX settings
Title: Message Title TraceTronic GmbH started work on JENKINS-31703 Change By: TraceTronic GmbH Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ecutest-plugin] (JENKINS-31703) Incorrect form validation for some ATX settings
Title: Message Title TraceTronic GmbH resolved as Fixed Jenkins / JENKINS-31703 Incorrect form validation for some ATX settings Change By: TraceTronic GmbH Status: In Progress Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [remoting] (JENKINS-23271) Intermittent Invalid Object ID in remoting module
Title: Message Title Hans-Juergen Hafner commented on JENKINS-23271 Re: Intermittent Invalid Object ID in remoting module I got this exception after update of Jenkins from 1.620 to 1.634 and Java on master from jdk1.7.0_45 to jdk1.8.0_66. Slaves still use Java SE RE 1.7.0_03-b04. ClearCase plug-in is not installed. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-22853) SEVERE: Trying to unexport an object that's already unexported
Title: Message Title Hans-Juergen Hafner commented on JENKINS-22853 Re: SEVERE: Trying to unexport an object that's already unexported I got this exception after update of Jenkins from 1.620 to 1.634 and Java on master from jdk1.7.0_45 to jdk1.8.0_66. Slaves still use Java SE RE 1.7.0_03-b04. Slave.jar version: 2.52 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31661) Jenkins.rootUrl too often unset or incorrect
Title: Message Title Antonio Muñiz commented on JENKINS-31661 Re: Jenkins.rootUrl too often unset or incorrect https://github.com/jenkinsci/jenkins/pull/1921 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31661) Jenkins.rootUrl too often unset or incorrect
Title: Message Title Manuel Jesús Recena Soto started work on JENKINS-31661 Change By: Manuel Jesús Recena Soto Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-31698) Add support for folder hierarchies in ATH
Title: Message Title Andres Rodriguez updated an issue Jenkins / JENKINS-31698 Add support for folder hierarchies in ATH Change By: Andres Rodriguez ATM, the JobsMixIn always creates Jobs at the "root" level. When the folder plugin is available, jobs may be created in any of the existing folders. Thus, the task scope includes: * Providing a mechanism to create jobs inside folders (including other folders). * Review TopLevelItem equality contract in the presence of hierarchy.* Create a simple test scenario involving a folder hierarchy. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Title: Message Title Daniel Beck commented on JENKINS-26545 Re: Persist build(s) log(s) in MySQL (or similar) More learned through experience by a number of community members. I doubt it's explicitly documented somewhere. From my limited experience with Maven I'd also consider 200 modules in a single build to be rather unusual, so the performance issues you experience likely aren't experienced by most users. When loading a single build involves parsing hundreds of XML files (compared to one in the case of freestyle), performance problems are to be expected. Note that there are other issues with the job type, which were written up by stephenconnolly, a contributor to Jenkins and Maven, here: http://javaadventure.blogspot.de/2013/11/jenkins-maven-job-type-considered-evil.html Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [acceptance-test-harness] (JENKINS-31698) Add support for folder hierarchies in ATH
Title: Message Title Andres Rodriguez updated an issue Jenkins / JENKINS-31698 Add support for folder hierarchies in ATH Change By: Andres Rodriguez ATM, the JobsMixIn always creates Jobs at the "root" level. When the folder plugin is available, jobs may be created in any of the existing folders. Thus, the task scope includes:* Providing a mechanism to create jobs inside folders (including other folders).* Review TopLevelItem equality contract in the presence of hierarchy.* Create a simple test scenario involving a folder hierarchy. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [reviewboard-plugin] (JENKINS-31704) Regarding stack trace
Title: Message Title vamsi juturu created an issue Jenkins / JENKINS-31704 Regarding stack trace Issue Type: Bug Assignee: vamsi juturu Components: reviewboard-plugin Created: 23/Nov/15 12:57 PM Priority: Major Reporter: vamsi juturu Hi, I am getting below error so, please help me how to resolve. NOTE: Below issue is appearing in manage jenkins>configure system. Oops! A problem occurred while processing the request. Please check our bug tracker to see if a similar problem has already been reported. If it is already reported, please vote and put a comment on it to let us gauge the impact of the problem. If you think this is a new issue, please file a new issue. When you file an issue, make sure to add the entire stack trace, along with the version of Jenkins and relevant plugins. The users list might be also useful in understanding what has happened. Stack trace javax.servlet.ServletException: org.apache.commons.jelly.JellyTagException: jar:file:/var/lib/jenkins/war/WEB-INF/lib/jenkins-core-1.610.jar!/lib/form/section.jelly:48:21: (class: hudson/plugins/reviewboard/ReviewboardPublisher, method: submitChangeToReviewBoard signature: (Ljava/lang/Long;Ljava/lang/String;Ljava/lang/Long;Ljava/lang/String;Ljava/lang/String;Ljava/util/Collection;Lhudson/model/AbstractBuild;Lhudson/Launcher;Lhudson/model/BuildListener;)Lhudson/plugins/reviewboard/ReviewInfoAction Incompatible argument to function at org.kohsuke.stapler.jelly.JellyFacet$1.dispatch(JellyFacet.java:103) at org.kohsuke.stapler.Stapler
[JIRA] [aws-beanstalk-publisher-plugin] (JENKINS-31705) Unable to hide the secret key of AWS in AWS elastic beanstalk plugin
Title: Message Title R. Tyler Croy moved an issue Jenkins / JENKINS-31705 Unable to hide the secret key of AWS in AWS elastic beanstalk plugin Change By: R. Tyler Croy Project: Infrastructure Jenkins Key: INFRA JENKINS - 494 31705 Issue Type: Bug Improvement Workflow: classic default workflow JNJira Component/s: aws-beanstalk-publisher-plugin Component/s: artifactory Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
[JIRA] [aws-beanstalk-publisher-plugin] (JENKINS-31705) Unable to hide the secret key of AWS in AWS elastic beanstalk plugin
Title: Message Title R. Tyler Croy assigned an issue to Unassigned I've moved this from the INFRA project which is largely focused on our project infrastructure. Jenkins / JENKINS-31705 Unable to hide the secret key of AWS in AWS elastic beanstalk plugin Change By: R. Tyler Croy Assignee: R. Tyler Croy Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-31462) GitHub Enterprise Servers validation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31462 Re: GitHub Enterprise Servers validation Code changed in jenkins User: Manuel Recena Path: src/main/java/org/jenkinsci/plugins/github_branch_source/Endpoint.java http://jenkins-ci.org/commit/github-branch-source-plugin/7bf7ae007abf7e22bca8f52060192e9880bd2dcb Log: JENKINS-31462 @oleg-nenashev's comments were addresed Compare: https://github.com/jenkinsci/github-branch-source-plugin/compare/8aefbc7ff314...7bf7ae007abf Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [github-branch-source-plugin] (JENKINS-31462) GitHub Enterprise Servers validation
Title: Message Title SCM/JIRA link daemon commented on JENKINS-31462 Re: GitHub Enterprise Servers validation Code changed in jenkins User: Manuel Recena Path: pom.xml src/main/java/org/jenkinsci/plugins/github_branch_source/Endpoint.java http://jenkins-ci.org/commit/github-branch-source-plugin/b05cadb17e87952955d25c7e91e1e03fa82758c9 Log: JENKINS-31462 GitHub Enterprise Servers validation Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clang-scanbuild-plugin] (JENKINS-24498) Promoted builds plugin fails to execute automatic (end of build) promotions
Title: Message Title Arnaud Héritier commented on JENKINS-24498 Re: Promoted builds plugin fails to execute automatic (end of build) promotions To be fixed by https://github.com/jenkinsci/clang-scanbuild-plugin/pull/11/commits ?? cc Emilio Escobar Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31706) ProcessTreeKiller broken for Windows when node went offline/online
Title: Message Title Stephane Gallès created an issue Jenkins / JENKINS-31706 ProcessTreeKiller broken for Windows when node went offline/online Issue Type: Bug Assignee: Unassigned Components: core Created: 23/Nov/15 1:50 PM Environment: Jenkins 1.625.1 LTS Window7,Window8,Window10 node JDK 1.7 Priority: Critical Reporter: Stephane Gallès 1) Choose a Windows7/8/10 node and mark it offline in its configuration page 2) then mark it online 3) Create a job attached to this node with the Windows command: notepad.exe 4) Start your job, check that Notepad is started (dont close). 5) Cancel the build of the job and see that Notepad is still open. On the windows node, if you manually restart the agent, this fixes the "kill behavior". the problem also happens for an accidental deconnection/reconnection (that how we've notificed that, because randomly it seems that the ProcessTreeKiller did not work anymore and it seemed that it happened after networks issues between the server and the node)
[JIRA] [github-pullrequest-plugin] (JENKINS-31707) manually trigger builds using ghprb don't add comments to the pull request
Title: Message Title Trevor Baker created an issue Jenkins / JENKINS-31707 manually trigger builds using ghprb don't add comments to the pull request Issue Type: Bug Assignee: Kanstantsin Shautsou Components: github-pullrequest-plugin Created: 23/Nov/15 1:59 PM Environment: jenkins 1.620 ghprb 1.29.4 Priority: Trivial Reporter: Trevor Baker When builds using the github pull request plugin are triggered manually by specifying the sha1 as a parameter, build results are not added to the pull request as comments. Is this expected for manually triggered builds? Add Comment
[JIRA] [ghprb-plugin] (JENKINS-31707) manually trigger builds using ghprb don't add comments to the pull request
Title: Message Title Kanstantsin Shautsou updated an issue Jenkins / JENKINS-31707 manually trigger builds using ghprb don't add comments to the pull request Change By: Kanstantsin Shautsou Component/s: ghprb-plugin Component/s: github-pullrequest-plugin Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [ghprb-plugin] (JENKINS-31707) manually trigger builds using ghprb don't add comments to the pull request
Title: Message Title Kanstantsin Shautsou assigned an issue to Honza Brázdil Jenkins / JENKINS-31707 manually trigger builds using ghprb don't add comments to the pull request Change By: Kanstantsin Shautsou Assignee: Kanstantsin Shautsou Honza Brázdil Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31706) ProcessTreeKiller broken for Windows when node went offline/online
Title: Message Title Stephane Gallès updated an issue Jenkins / JENKINS-31706 ProcessTreeKiller broken for Windows when node went offline/online Change By: Stephane Gallès 1) Choose a Windows7/8/10 node and mark it offline in its configuration page2) then mark it online3) Create a job attached to this node with the Windows command: notepad.exe4) Start your job, check that Notepad is started (dont close).5) Cancel the build of the job and see that Notepad is still open.On the windows node, if you manually restart the agent, this fixes the "kill behavior".the problem also happens for an accidental deconnection/reconnection (that how we 've notificed that, because randomly it seems that the ProcessTreeKiller did not work anymore and it seemed that it happened after networks issues between the server and the node) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-31708) pin plugin
Title: Message Title Zlatko Mozanic created an issue Jenkins / JENKINS-31708 pin plugin Issue Type: Improvement Assignee: Unassigned Components: core Created: 23/Nov/15 2:10 PM Environment: Jenkins ver. 1.609.3 Labels: pinned Priority: Minor Reporter: Zlatko Mozanic Hi, Wouldn't it be better to have possibility to pin plugin version via gui as well? At the moment it is possible only to unpin, and once it is unpinned you can not pin it back. This can lead to accidental unpinning. Think it should be better if either of two is possible: pin and unpin via gui and manually (plugins in jenkins_home) or pin and unpin ONLY manually. BRs
[JIRA] [jobconfighistory-plugin] (JENKINS-30968) slave config history does not show changes after SYSTEM update
Title: Message Title Zlatko Mozanic updated an issue Jenkins / JENKINS-30968 slave config history does not show changes after SYSTEM update Hi, no need to look at this. seems that our local installation of Job Configuration History Plugin was updated manually which introduced fault. BRs Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [clang-scanbuild-plugin] (JENKINS-24498) Promoted builds plugin fails to execute automatic (end of build) promotions
Title: Message Title Arnaud Héritier updated an issue Jenkins / JENKINS-24498 Promoted builds plugin fails to execute automatic (end of build) promotions Change By: Arnaud Héritier Comment: To be fixed by https://github.com/jenkinsci/clang-scanbuild-plugin/pull/11/commits ?? cc [~escoem] Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [core] (JENKINS-26545) Persist build(s) log(s) in MySQL (or similar)
Title: Message Title stephenconnolly commented on JENKINS-26545 Re: Persist build(s) log(s) in MySQL (or similar) Part of the issue in start-up performance for the evil job type is the mutability of build results issue... You can see this in the other side-effect issues: JENKINS-20731 , JENKINS-25075 Basically, back from when this job type was truly completely and utterly evil, it would run each module as a separate "job" in parallel and basically re-implement the whole Maven Reactor with a bunch of hacks... You can still enable this mode of using the evil job type, but it is at least no longer the default. So what you have is that you can re-run a single module only... and the build result for an evil job is the aggregate build result of the most recent build of all the modules... Thus if you get a foo-project build #5 broken due to a flakey test in foo-manchu-module, you just re-trigger the failing module and presto! your foo-project build #5 is now overall fixed because the foo-manchu-module build #6 was a success (note that the original build of foo-project #5 resulted in foo-manchu-module build #5) So when Jenkins loads an evil job build record, not only does it have to parse all latest build child module descriptors, but it has to re-evaluate all the latest build results of all modules in the current build... And then the weather column wants to evaluate the build stability... so it goes asking for the build result of the previous 4 builds... So actually I would contend (and James Nord would agree) that the root cause of the performance issues is actually the mutability of the build result in the evil job type... fix that and a lot of the evil job's performance issues can be resolved... there are other performance issues with the evil job... and it will still be evil (FYI: I call it evil from my PoV as a committer to the Apache Maven project because it is a job type that expressly goes completely against the core principles of Maven... one of which being that the build can be completely reproducible using an identical environment variables, user permissions pom and command-line... the evil one doesn't do this because it modifies the effective pom in ways you cannot see or deterministically determine without injecting some additional inspection code into your Maven binaries) Add Comment
[JIRA] [git-parameter-plugin] (JENKINS-28597) GIT Parameter Plugin not using stored credentials
Title: Message Title Nikolas Falco commented on JENKINS-28597 Re: GIT Parameter Plugin not using stored credentials Yes Bruno, but it should not use any the SSH key on jenkins server. I expect it use the credential plugin to access repositories as the git plugin do to download source code. The goal have a working a job without setup any SSH key configuration on all jenkins nodes. The credential plugin is great for that. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-parameter-plugin] (JENKINS-28597) GIT Parameter Plugin not using stored credentials
Title: Message Title Nikolas Falco edited a comment on JENKINS-28597 Re: GIT Parameter Plugin not using stored credentials Yes Bruno, but it should not use any the SSH key on jenkins server. I expect it use the credential plugin to access repositories as the git plugin do to download source code.The goal have a working a job without setup any SSH key configuration on all jenkins nodes. The credential plugin is great for that. Jenkins version 1.596.2 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [git-client-plugin] (JENKINS-30371) Symlinks still not supported on unix with JGit 3.7.1
Title: Message Title Alexandre Feblot commented on JENKINS-30371 Re: Symlinks still not supported on unix with JGit 3.7.1 Thanks Mark! I cross my fingers now to see it merged soon. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-2299) Offer option to generate a jira release for hudson build
Title: Message Title Radek Antoniuk resolved as Won't Do This should be possible with "Create JIRA version" and "Move matching issues to specified version". Jenkins / JENKINS-2299 Offer option to generate a jira release for hudson build Change By: Radek Antoniuk Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-12605) Avoid cluttering up JIRA comments
Title: Message Title Radek Antoniuk resolved as Won't Do Won't Fix - as designed. The comments should be added when they happen. Jenkins / JENKINS-12605 Avoid cluttering up JIRA comments Change By: Radek Antoniuk Status: Open Resolved Resolution: Won't Do Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [jira-plugin] (JENKINS-13494) Comment not added if issue id is not on first line of commit message
Title: Message Title Radek Antoniuk resolved as Cannot Reproduce Jenkins / JENKINS-13494 Comment not added if issue id is not on first line of commit message Change By: Radek Antoniuk Status: Open Resolved Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31662) Check out of project wth svn:externals to files fails
Title: Message Title
M P commented on JENKINS-31662
Re: Check out of project wth svn:externals to files fails
Sure. Note that this one has a workaround configured: the svn plugin does not check out the externals, but an extra build step (shell script) pulls them in with the regular svn command.
When I comment that line and uncheck "ignore externals" in the svn plugin, the problem reappears.
Here is the config.xml; see below for the svn:externals in question.
{{ P2 Web Development -1 10 -1 -1 false P2WEB-tomcat http://svnhost.example.com/p2/trunk/DFS/p2 2d3117d2-89e6-428d-adc8-cbd4a04613e5 . infinity true ; p2 SVN Repository 2d3117d2-89e6-428d-adc8-cbd4a04613e5http://svnhost.example.com/viewvc/p2/ /trunk/DFS/p2/web-app/apidoc.* /trunk/DFS/p2/web-app/WEB-INF/.*\.yaml false false seq false false false false Java7 32 H/2 * * * * false false # pull in externals – apparently Jenkins is unable to do that svn update --non-interactive "test-app functional:" "test test-more integration: -coverage" "codenarc" 2.5.028722 false true false true false false false "war target/p2-latest.war" 2.5.0 grails.env=demo false true false true false false false Coverage Report target/test-reports/cobertura index.html false true true Coding Style Report target/codenarc index.html true true false target/test-reports/TEST-*.xml false 1.0 checkstyle checkstyle 10 999 999 false codenarc codenarc 10 999 999 false target/**/codenarc.xmlcpd cpd 10 999 999 false cpplint cpplint 10 999 999 false csslint csslint 10 999 999 false findbugs findbugs 10 999 999 false fxcop fxcop 10 999 999 false gendarme gendarme 10 999 999 false jcreport jcreport 10 999 999 false jslint jslint 10 999 999 false pep8 pep8 10 999 999 false perlcritic perlcritic 10 999 999 false pmd pmd 10 999 999 false pylint pylint 10 999 999 false simian simian 10 999 999 false stylecop stylecop 10 999 999 false 100 default jenkins XX http://tomcat.example.com /p2ci target/p2-latest.war true x...@example.com false false}}
svn:externals: {{$ svn proplist -v . Properties on '.': svn:externals ^/trunk/DFS/OHS/esoAuthenticator/src/main/java/org/eso/ohs/esoAuthenticator/BCrypt.java BCrypt.java ^/trunk/DFS/OHS/esoAuthenticator/src/main/java/org/eso/ohs/esoAuthenticator/EncryptionAlgorithm.java EncryptionAlgorithm.java }}
Add Comment
[JIRA] [subversion-plugin] (JENKINS-31662) Check out of project wth svn:externals to files fails
Title: Message Title
Manuel Jesús Recena Soto updated an issue
Jenkins / JENKINS-31662
Check out of project wth svn:externals to files fails
Change By:
Manuel Jesús Recena Soto
Checking out a project with two file externals fails with the following errors: { { noformat} [...]A web-app/WEB-INF/instruments/ESPRESSO-1.01/ESPRESSO_multiMR_obs.tsfA web-app/WEB-INF/instruments/ESPRESSO-1.01/test_ESPRESSO_TPL_sci.tsfA web-app/WEB-INF/instruments/ESPRESSO-1.01/ESPRESSERROR: Failed to check out http:///trunk/DFS/p2org.tmatesoft.svn.core.SVNCancelException: svn: E200015: authentication cancelled at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:37) at org.tmatesoft.svn.core.internal.wc.SVNErrorManager.cancel(SVNErrorManager.java:32) at org.tmatesoft.svn.core.internal.wc.DefaultSVNAuthenticationManager.getNextAuthentication(DefaultSVNAuthenticationManager.java:215) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:685) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:371) at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:359) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.performHttpRequest(DAVConnection.java:710) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.exchangeCapabilities(DAVConnection.java:627) at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.open(DAVConnection.java:102) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.openConnection(DAVRepository.java:1032) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.hasCapability(DAVRepository.java:860) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1278) at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:845) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.switchFileExternal(SvnNgAbstractUpdate.java:587) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.handleExternalItemChange(SvnNgAbstractUpdate.java:395) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.handleExternalsChange(SvnNgAbstractUpdate.java:310) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.handleExternals(SvnNgAbstractUpdate.java:246) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.updateInternal(SvnNgAbstractUpdate.java:224) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.update(SvnNgAbstractUpdate.java:72) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgAbstractUpdate.checkout(SvnNgAbstractUpdate.java:802) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:26) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgCheckout.run(SvnNgCheckout.java:11) at org.tmatesoft.svn.core.internal.wc2.ng.SvnNgOperationRunner.run(SvnNgOperationRunner.java:20) at org.tmatesoft.svn.core.internal.wc2.SvnOperationRunner.run(SvnOperationRunner.java:21) at org.tmatesoft.svn.core.wc2.SvnOperationFactory.run(SvnOperationFactory.java:1259) at org.tmatesoft.svn.core.wc2.SvnOperation.run(SvnOperation.java:294) at hudson.scm.subversion.CheckoutUpdater$1.perform(CheckoutUpdater.java:121) at hudson.scm.subversion.WorkspaceUpdater$UpdateTask.delegateTo(WorkspaceUpdater.java:162) at hudson.scm.Su
[JIRA] [subversion-plugin] (JENKINS-31662) Check out of project wth svn:externals to files fails
Title: Message Title Manuel Jesús Recena Soto updated an issue Jenkins / JENKINS-31662 Check out of project wth svn:externals to files fails Change By: Manuel Jesús Recena Soto Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31662) Check out of project wth svn:externals to files fails
Title: Message Title Manuel Jesús Recena Soto commented on JENKINS-31662 Re: Check out of project wth svn:externals to files fails M P, Please, apply format to your comment. You don't need a workaround to use svn:externals. I recommend you do not use SVN Client in CLI when your working copy was checked out with Subversion Plugin. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [multiple-scms-plugin] (JENKINS-26734) Subversion Plugin 2.5 is incompatible with Multiple SCM plugin
Title: Message Title Sven S. commented on JENKINS-26734 Re: Subversion Plugin 2.5 is incompatible with Multiple SCM plugin Same problem here with 1.638 reverted to 2.4.5 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-28945) Lightbox view mode of console output won't show
Title: Message Title Dan Alvizu resolved as Duplicate Jenkins / JENKINS-28945 Lightbox view mode of console output won't show Change By: Dan Alvizu Status: Open Resolved Assignee: Dan Alvizu Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-28945) Lightbox view mode of console output won't show
Title: Message Title Dan Alvizu commented on JENKINS-28945 Re: Lightbox view mode of console output won't show Yup duplicate of JENKINS-25430 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-14591) Add the ability to choose which parameters build will be displayed
Title: Message Title Dan Alvizu commented on JENKINS-14591 Re: Add the ability to choose which parameters build will be displayed Three scenarios are valid: Include all variables (today's behavior) Include a subset of all variables (JENKINS-14591) Include only parameters (PR #74's behavior) Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [integrity-plugin] (JENKINS-31588) "No space left on device" when there is near 100 GB available
Title: Message Title Cletus D'Souza commented on JENKINS-31588 Re: "No space left on device" when there is near 100 GB available Do you have an update? Were you able to identify the root cause for the disk space issue? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-26596) On restarting broken build in pipeline, dashboard should update accordingly
Title: Message Title Dan Alvizu commented on JENKINS-26596 Re: On restarting broken build in pipeline, dashboard should update accordingly I believe this is fixed - can you please re-test on master? This is very similar to JENKINS-30801 , the PR is very similar as well. JENKINS-30801 was fixed in master and it's likely it resolved this issue as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-26596) On restarting broken build in pipeline, dashboard should update accordingly
Title: Message Title Dan Alvizu resolved as Duplicate Jenkins / JENKINS-26596 On restarting broken build in pipeline, dashboard should update accordingly Change By: Dan Alvizu Status: Open Resolved Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-19870) Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds
Title: Message Title Dan Alvizu resolved as Fixed Jenkins / JENKINS-19870 Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds Change By: Dan Alvizu Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-19870) Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds
Title: Message Title Dan Alvizu commented on JENKINS-19870 Re: Status of the existing pipeline job is not updated after a failure or aborted build. Downstream job trigger is not enabled after the build succeeds Can you please re-test on master? This is very similar to JENKINS-30801 , the PR is very similar as well. JENKINS-30801 was fixed in master and it's likely it resolved this issue as well. Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31662) Check out of project wth svn:externals to files fails
Title: Message Title
M P edited a comment on JENKINS-31662
Re: Check out of project wth svn:externals to files fails
Sure. Note that this one has a workaround configured: the svn plugin does not check out the externals, but an extra build step (shell script) pulls them in with the regular svn command.When I comment that line and uncheck "ignore externals" in the svn plugin, the problem reappears.Here is the config.xml; see below for the svn:externals in question.{ { noformat} P2 Web Development -110-1-1falseP2WEB-tomcat http://svnhost.example.com/p2/trunk/DFS/p22d3117d2-89e6-428d-adc8-cbd4a04613e5.infinitytrue p2 SVN Repository2d3117d2-89e6-428d-adc8-cbd4a04613e5http://svnhost.example.com/viewvc/p2//trunk/DFS/p2/web-app/apidoc.*/trunk/DFS/p2/web-app/WEB-INF/.*\.yamlfalsefalseseq false false false false Java7 32H/2 * * * * falsefalse# pull in externals -- apparently Jenkins is unable to do that :-(svn update --non-interactive "test-app functional:" "test test-more integration: -coverage" "codenarc" 2.5.028722false true false true false false false "war target/p2-latest.war" 2.5.0 grails.env=demo false true false true false false falseCoverage Report target/test-reports/cobertura index.html false true true Coding Style Report target/codenarc index.html true true falsetarget/test-reports/TEST-*.xml false 1.0checkstyle checkstyle 10 999 999 false codenarc codenarc 10 999 999 false target/**/codenarc.xmlcpd cpd 10 999 999 false cpplint cpplint 10 999 999 false csslint csslint 10 999 999 false findbugs findbugs 10 999 999 false fxcop fxcop 10 999 999 false gendarme gendarme 10 999 999 false jcreport jcreport 10 999 999 false jslint jslint 10 999 999 false pep8 pep8 10 999 999 false perlcritic perlcritic 10 999
[JIRA] [google-play-android-publisher-plugin] (JENKINS-31684) timeout when trying to upload an apk to google play probably because of proxy
Title: Message Title
Alexander Fendt commented on JENKINS-31684
Re: timeout when trying to upload an apk to google play probably because of proxy
Hi Christopher, thanks for your answer - the proxy works now. So stupid simple. Now I get another exception.
Caused by: com.google.api.client.auth.oauth2.TokenResponseException: 400 Bad Request
{
"error" : "invalid_grant"
}
at com.google.api.client.auth.oauth2.TokenResponseException.from(TokenResponseException.java:105)
which I think is caused by the fact that I cannot grant access to the client ID in google Play. As you can see google automatically sets the numeric client id as e-mail-adress in google play's api access page. That client id I cannot grant access because its no valid mailadress. Am I totally crazy or is this a bug on google play?
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [workflow-plugin] (JENKINS-31701) workflow-multibranch Jenkinsfile: "Sleep 60" causes "RejectedAccessException: Scripts not permitted to use"
Title: Message Title Jesse Glick resolved as Incomplete Can you reproduce from scratch on a clean installation? Typically this kind of error means that you failed to update some of the relevant plugins, such as Script Security, to the versions required by some downstream plugins. (And Jenkins core does not yet enforce plugin dependencies consistently.) Jenkins / JENKINS-31701 workflow-multibranch Jenkinsfile: "Sleep 60" causes "RejectedAccessException: Scripts not permitted to use" Change By: Jesse Glick Status: Open Resolved Resolution: Incomplete Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-play-android-publisher-plugin] (JENKINS-31684) timeout when trying to upload an apk to google play probably because of proxy
Title: Message Title Alexander Fendt updated an issue Jenkins / JENKINS-31684 timeout when trying to upload an apk to google play probably because of proxy Change By: Alexander Fendt Attachment: google.developer.console.png Attachment: google.play.api.access.png Attachment: google.play.api.access.grant.png Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [google-play-android-publisher-plugin] (JENKINS-31684) timeout when trying to upload an apk to google play probably because of proxy
Title: Message Title
Alexander Fendt edited a comment on JENKINS-31684
Re: timeout when trying to upload an apk to google play probably because of proxy
Hi Christopher, thanks for your answer - the proxy works now. So stupid simple. Now I get another exception.{code:java}Caused by: com.google.api.client.auth.oauth2.TokenResponseException: 400 Bad Request{ "error" : "invalid_grant"} at com.google.api.client.auth.oauth2.TokenResponseException.from(TokenResponseException.java:105){code}which I think is caused by the fact that I cannot grant access to the client ID in google Play.As you can see google automatically sets the numeric (!) client id as e-mail-adress in google play's api access page. That client id I cannot grant access because its no valid mailadress.Am I totally crazy or is this a bug on google play? !google.developer.console.png|thumbnail! !google.play.api.access.grant.png|thumbnail! !google.play.api.access.png|thumbnail!
Add Comment
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] [subversion-plugin] (JENKINS-31662) Check out of project wth svn:externals to files fails
Title: Message Title M P commented on JENKINS-31662 Re: Check out of project wth svn:externals to files fails Re formatting: I was using the wrong "code", sorry for that. I fixed it. If I let the svn plugin check out the code, the job always fails because of the externals. So, what do you suggest? Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [matrix-auth-plugin] (JENKINS-21856) Authorization - Matrix-based security - Removing Cancel Right Has No Effect
Title: Message Title Jesse Glick resolved as Not A Defect Job/Cancel is implied by Job/Build. You cannot have the latter without the former. Jenkins / JENKINS-21856 Authorization - Matrix-based security - Removing Cancel Right Has No Effect Change By: Jesse Glick Status: Open Resolved Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [security] (JENKINS-7890) Hudson CI start-up with IBM JDK 6 reports java.lang.NoClassDefFoundError: sun.security.x509.CertAndKeyGen
Title: Message Title
Alberto Gallardo reopened an issue
Seen this issue in a recent jenkins running on IBM Java.
{{# java -jar /usr/lib/jenkins/jenkins.war --version Running from: /usr/lib/jenkins/jenkins.war webroot: $user.home/.jenkins 1.638
#java -version java version "1.7.0" Java(TM) SE Runtime Environment (build pxa6470_27sr3fp10-20150708_01(SR3 FP10)) IBM J9 VM (build 2.7, JRE 1.7.0 Linux amd64-64 Compressed References 20150630_255653 (JIT enabled, AOT enabled) J9VM - R27_Java727_SR3_20150630_2236_B255653 JIT - tr.r13.java_20150623_94888.01 GC - R27_Java727_SR3_20150630_2236_B255653_CMPRSS J9CL - 20150630_255653) JCL - 20150628_01 based on Oracle jdk7u85-b15
cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 4
tail -1 /etc/sysconfig/jenkins JENKINS_ARGS="--httpsPort=8443" }}
Notice that Java IBM comes with a com.ibm.security.x509.CertAndKeyGen (provided in lib/ibmpkcs.jar) in contrast to the requested sun.security.x509.CertAndKeyGen.
Logs: {{Running from: /usr/lib/jenkins/jenkins.war Nov 23, 2015 4:57:03 PM winstone.Logger logInternal INFO: Beginning extraction from war file Using one-time self-signed certificate Nov 23, 2015 4:57:03 PM winstone.Logger logInternal INFO: Winstone shutdown successfully Nov 23, 2015 4:57:03 PM winstone.Logger logInternal SEVERE: Container startup failed java.io.IOException: Failed to start a listener: winstone.HttpsConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.(Launcher.java:149) at winstone.Launcher.main(Launcher.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56) at java.lang.reflect.Method.invoke(Method.java:620) at Main._main(Main.java:293) at Main.main(Main.java:98) Caused by: java.lang.NoClassDefFoundError: sun.security.x509.CertAndKeyGen at winstone.HttpsConnectorFactory.start(HttpsConnectorFactory.java:100) at winstone.Launcher.spawnListener(Launcher.java:207) ... 8 more Caused by: java.lang.ClassNotFoundException: sun.security.x509.CertAndKeyGen at java.net.URLClassLoader.findClass(URLClassLoader.java:600) at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:786) at java.lang.ClassLoader.loadClass(ClassLoader.java:760) at java.lang.ClassLoader.loadClass(ClassLoader.java:741) ... 10 more }}
Jenkins / JENKINS-7890
Hudson CI start-up with IBM JDK 6 reports java.lang.NoClassDefFoundError: sun.security.x509.CertAndKeyGen
Change By:
Albert
[JIRA] [security] (JENKINS-7890) Hudson CI start-up with IBM JDK 6 reports java.lang.NoClassDefFoundError: sun.security.x509.CertAndKeyGen
Title: Message Title
Alberto Gallardo edited a comment on JENKINS-7890
Re: Hudson CI start-up with IBM JDK 6 reports java.lang.NoClassDefFoundError: sun.security.x509.CertAndKeyGen
Seen this issue in a recent jenkins running on IBM Java.{ { code} # java -jar /usr/lib/jenkins/jenkins.war --versionRunning from: /usr/lib/jenkins/jenkins.warwebroot: $user.home/.jenkins1.638#java -versionjava version "1.7.0"Java(TM) SE Runtime Environment (build pxa6470_27sr3fp10-20150708_01(SR3 FP10))IBM J9 VM (build 2.7, JRE 1.7.0 Linux amd64-64 Compressed References 20150630_255653 (JIT enabled, AOT enabled)J9VM - R27_Java727_SR3_20150630_2236_B255653JIT - tr.r13.java_20150623_94888.01GC - R27_Java727_SR3_20150630_2236_B255653_CMPRSSJ9CL - 20150630_255653)JCL - 20150628_01 based on Oracle jdk7u85-b15# cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64)VERSION = 11PATCHLEVEL = 4# tail -1 /etc/sysconfig/jenkinsJENKINS_ARGS="--httpsPort=8443" {code } } Notice that Java IBM comes with a {{com.ibm.security.x509.CertAndKeyGen}} (provided in {{lib/ibmpkcs.jar}}) in contrast to the requested {{sun.security.x509.CertAndKeyGen}}.Logs:{ { code} Running from: /usr/lib/jenkins/jenkins.warNov 23, 2015 4:57:03 PM winstone.Logger logInternalINFO: Beginning extraction from war fileUsing one-time self-signed certificateNov 23, 2015 4:57:03 PM winstone.Logger logInternalINFO: Winstone shutdown successfullyNov 23, 2015 4:57:03 PM winstone.Logger logInternalSEVERE: Container startup failedjava.io.IOException: Failed to start a listener: winstone.HttpsConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.(Launcher.java:149) at winstone.Launcher.main(Launcher.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56) at java.lang.reflect.Method.invoke(Method.java:620) at Main._main(Main.java:293) at Main.main(Main.java:98)Caused by: java.lang.NoClassDefFoundError: sun.security.x509.CertAndKeyGen at winstone.HttpsConnectorFactory.start(HttpsConnectorFactory.java:100) at winstone.Launcher.spawnListener(Launcher.java:207) ... 8 moreCaused by: java.lang.ClassNotFoundException: sun.security.x509.CertAndKeyGen at java.net.URLClassLoader.findClass(URLClassLoader.java:600) at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:786) at java.lang.ClassLoader.loadClass(ClassLoader.java:760) at java.lang.ClassLoader.loadClass(ClassLoader.java:741) ... 10 more {code } }
Add Comment
This message was sent by Atlassian JIRA
[JIRA] [security] (JENKINS-7890) Hudson CI start-up with IBM JDK 6 reports java.lang.NoClassDefFoundError: sun.security.x509.CertAndKeyGen
Title: Message Title
Alberto Gallardo edited a comment on JENKINS-7890
Re: Hudson CI start-up with IBM JDK 6 reports java.lang.NoClassDefFoundError: sun.security.x509.CertAndKeyGen
Seen this issue in a recent jenkins running on IBM Java.{ code noformat }# java -jar /usr/lib/jenkins/jenkins.war --versionRunning from: /usr/lib/jenkins/jenkins.warwebroot: $user.home/.jenkins1.638#java -versionjava version "1.7.0"Java(TM) SE Runtime Environment (build pxa6470_27sr3fp10-20150708_01(SR3 FP10))IBM J9 VM (build 2.7, JRE 1.7.0 Linux amd64-64 Compressed References 20150630_255653 (JIT enabled, AOT enabled)J9VM - R27_Java727_SR3_20150630_2236_B255653JIT - tr.r13.java_20150623_94888.01GC - R27_Java727_SR3_20150630_2236_B255653_CMPRSSJ9CL - 20150630_255653)JCL - 20150628_01 based on Oracle jdk7u85-b15# cat /etc/SuSE-release SUSE Linux Enterprise Server 11 (x86_64)VERSION = 11PATCHLEVEL = 4# tail -1 /etc/sysconfig/jenkinsJENKINS_ARGS="--httpsPort=8443"{ code noformat }Notice that Java IBM comes with a {{com.ibm.security.x509.CertAndKeyGen}} (provided in {{lib/ibmpkcs.jar}}) in contrast to the requested {{sun.security.x509.CertAndKeyGen}}.Logs:{ code noformat }Running from: /usr/lib/jenkins/jenkins.warNov 23, 2015 4:57:03 PM winstone.Logger logInternalINFO: Beginning extraction from war fileUsing one-time self-signed certificateNov 23, 2015 4:57:03 PM winstone.Logger logInternalINFO: Winstone shutdown successfullyNov 23, 2015 4:57:03 PM winstone.Logger logInternalSEVERE: Container startup failedjava.io.IOException: Failed to start a listener: winstone.HttpsConnectorFactory at winstone.Launcher.spawnListener(Launcher.java:209) at winstone.Launcher.(Launcher.java:149) at winstone.Launcher.main(Launcher.java:354) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:95) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:56) at java.lang.reflect.Method.invoke(Method.java:620) at Main._main(Main.java:293) at Main.main(Main.java:98)Caused by: java.lang.NoClassDefFoundError: sun.security.x509.CertAndKeyGen at winstone.HttpsConnectorFactory.start(HttpsConnectorFactory.java:100) at winstone.Launcher.spawnListener(Launcher.java:207) ... 8 moreCaused by: java.lang.ClassNotFoundException: sun.security.x509.CertAndKeyGen at java.net.URLClassLoader.findClass(URLClassLoader.java:600) at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:786) at java.lang.ClassLoader.loadClass(ClassLoader.java:760) at java.lang.ClassLoader.loadClass(ClassLoader.java:741) ... 10 more{ code noformat }
Add Comment
This message
[JIRA] [build-pipeline-plugin] (JENKINS-29477) View bad for Build Pipeline Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29477 Re: View bad for Build Pipeline Plugin Code changed in jenkins User: Fishermans Path: src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/d8eb803c054b30a7c423ad543f5433316ee6f81a Log: Fixed JENKINS-29477 Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] [build-pipeline-plugin] (JENKINS-29477) View bad for Build Pipeline Plugin
Title: Message Title SCM/JIRA link daemon commented on JENKINS-29477 Re: View bad for Build Pipeline Plugin Code changed in jenkins User: Dan Alvizu Path: src/main/webapp/css/main.css http://jenkins-ci.org/commit/build-pipeline-plugin/b5d8f5251bcf1c9c1711e1d9513bd0dc66911629 Log: Merge pull request #92 from fishermans/master [Fixed JENKINS-29477] Compare: https://github.com/jenkinsci/build-pipeline-plugin/compare/77a1a2ffa368...b5d8f5251bcf Add Comment This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
