[JIRA] (JENKINS-45074) spot-fleet plugin deadlocks master when scaling up
Title: Message Title Artem Stasiuk resolved as Fixed Feel free to reopen if you still have problem with it. Jenkins / JENKINS-45074 spot-fleet plugin deadlocks master when scaling up Change By: Artem Stasiuk Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183167.1498143044000.2130.1557813061502%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-45074) spot-fleet plugin deadlocks master when scaling up
Title: Message Title Artem Stasiuk commented on JENKINS-45074 Re: spot-fleet plugin deadlocks master when scaling up Was released under version 1.1.7 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.183167.1498143044000.2122.1557813061244%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54679) SSHLauncher doesn't continue retrying to connect to remote executor
Title: Message Title Artem Stasiuk commented on JENKINS-54679 Re: SSHLauncher doesn't continue retrying to connect to remote executor Thx for info, Bert JW Regeer did you fix it in the same way? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195470.1542400069000.2118.1557812880200%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47396) ArrayIndexOutOfBoundsException on some fast searches
Title: Message Title runze xia edited a comment on JENKINS-47396 Re: ArrayIndexOutOfBoundsException on some fast searches Seem like ORO's error . As of 2010-09-01, the ORO project is retired. This is an archived site. :( Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185834.1507789181000.2114.1557812400103%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47396) ArrayIndexOutOfBoundsException on some fast searches
Title: Message Title runze xia commented on JENKINS-47396 Re: ArrayIndexOutOfBoundsException on some fast searches As of 2010-09-01, the ORO project is retired. This is an archived site. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185834.1507789181000.2112.1557812340149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47396) ArrayIndexOutOfBoundsException on some fast searches
Title: Message Title runze xia commented on JENKINS-47396 Re: ArrayIndexOutOfBoundsException on some fast searches May 14, 2019 5:04:01 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: Error while serving http://ks-jenkins.kubesphere-devops-system.svc/blue/rest/search/ java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.ForwardingFunction.invoke(ForwardingFunction.java:83) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor.invoke(PagedResponse.java:42) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:709) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at
[JIRA] (JENKINS-47396) ArrayIndexOutOfBoundsException on some fast searches
Title: Message Title runze xia commented on JENKINS-47396 Re: ArrayIndexOutOfBoundsException on some fast searches May 14, 2019 5:03:59 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: Error while serving http://ks-jenkins.kubesphere-devops-system.svc/blue/rest/search/ java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.ForwardingFunction.invoke(ForwardingFunction.java:83) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor.invoke(PagedResponse.java:42) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:709) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at
[JIRA] (JENKINS-44138) Add options for node launching strategy
Title: Message Title Artem Stasiuk commented on JENKINS-44138 Re: Add options for node launching strategy Could you please provide a use case for such flexible configuration, this change could take some time, as current impl totally controlled by Jenkins. It defines when scale-up will be run and what amount of executors should be launched. The plugin just controls that no the max will be run. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.181764.1494315309000.2103.1557811560111%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47396) ArrayIndexOutOfBoundsException on some fast searches
Title: Message Title runze xia reopened an issue I can provide some error logs May 14, 2019 5:04:01 AM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: Error while serving http://ks-jenkins.kubesphere-devops-system.svc/blue/rest/search/ java.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400) at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408) at org.kohsuke.stapler.ForwardingFunction.invoke(ForwardingFunction.java:83) at io.jenkins.blueocean.rest.pageable.PagedResponse$Processor.invoke(PagedResponse.java:42) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:537) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:709) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.MetaClass$9.dispatch(MetaClass.java:458) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:739) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:870) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:668) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:865) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1655) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:243) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.auth.jwt.impl.JwtAuthenticationFilter.doFilter(JwtAuthenticationFilter.java:61) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at com.smartcodeltd.jenkinsci.plugin.assetbundler.filters.LessCSS.doFilter(LessCSS.java:47) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at hudson.util.PluginServletFilter.doFilter(PluginServletFilter.java:157) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.csrf.CrumbFilter.doFilter(CrumbFilter.java:105) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1642) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:84) at hudson.security.UnwrapSecurityExceptionFilter.doFilter(UnwrapSecurityExceptionFilter.java:51) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at jenkins.security.ExceptionTranslationFilter.doFilter(ExceptionTranslationFilter.java:117) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.providers.anonymous.AnonymousProcessingFilter.doFilter(AnonymousProcessingFilter.java:125) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.rememberme.RememberMeProcessingFilter.doFilter(RememberMeProcessingFilter.java:142) at hudson.security.ChainedServletFilter$1.doFilter(ChainedServletFilter.java:87) at org.acegisecurity.ui.AbstractProcessingFilter.doFilter(AbstractProcessingFilter.java:271) at
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk edited a comment on JENKINS-35435 Re: Test connection doesn't work Current The current version of the plugin is using configured credentials [ here code|[https://github.com/jenkinsci/ec2-fleet-plugin/blob/master/src/main/java/com/amazon/jenkins/ec2fleet/EC2FleetCloud.java#L611]] Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171232.146532240.2092.1557811380282%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35435) Test connection doesn't work
Title: Message Title Artem Stasiuk commented on JENKINS-35435 Re: Test connection doesn't work Current version of plugin is using configured credentials code Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171232.146532240.2089.1557811320357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37123) Support role based access
Title: Message Title Artem Stasiuk commented on JENKINS-37123 Re: Support role based access EC2 Spot Fleet supports IAM Roles: EC2 Fleet Plugin supports IAM Role. Manage Jenkins > System Configuration, find Spot Fleet Configuration, if you open AWS Credentials, at the bottom, it has IAM Role Support, which allows the specifying role to assume by the plugin. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173201.1470152923000.2076.1557811080316%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37123) Support role based access
Title: Message Title Artem Stasiuk resolved as Done Feel free to reopen if you have questions. Jenkins / JENKINS-37123 Support role based access Change By: Artem Stasiuk Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173201.1470152923000.2080.1557811080399%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37123) Support role based access
Title: Message Title Artem Stasiuk commented on JENKINS-37123 Re: Support role based access Similar https://issues.jenkins-ci.org/browse/JENKINS-55343 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173201.1470152923000.2068.1557811020279%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-37123) Support role based access
Title: Message Title Artem Stasiuk edited a comment on JENKINS-37123 Re: Support role based access Similar https://issues.jenkins-ci.org/browse/ JENKINS-55343 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.173201.1470152923000.2072.1557811020329%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57188) EC2 fleet machines fail to spin up.
Title: Message Title Artem Stasiuk resolved as Done Thx for update, closed. Jenkins / JENKINS-57188 EC2 fleet machines fail to spin up. Change By: Artem Stasiuk Status: Open Resolved Resolution: Done Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198941.1556212968000.2065.1557810900382%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-48696) When an offline node comes online, pending jobs don't get assigned to it
Title: Message Title Artem Stasiuk commented on JENKINS-48696 Re: When an offline node comes online, pending jobs don't get assigned to it Do you still have this issue? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.187380.1513974343000.2060.1557810780141%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55343) How to use IAM role for authentication with Amazon EC2 Fleet Plugin
Title: Message Title Artem Stasiuk edited a comment on JENKINS-55343 Re: How to use IAM role for authentication with Amazon EC2 Fleet Plugin Hi,EC2 Fleet Plugin supports IAM Role. Manage Jenkins > System Configuration, find Spot Fleet Configuration, if you open AWS Credentials, at the bottom, it has IAM Role Support, which allows the specifying role to assume by the plugin. Thx,Artem Is that feature which you are interesting? Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196437.1545899269000.2058.1557809220124%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55343) How to use IAM role for authentication with Amazon EC2 Fleet Plugin
Title: Message Title Artem Stasiuk commented on JENKINS-55343 Re: How to use IAM role for authentication with Amazon EC2 Fleet Plugin Hi, EC2 Fleet Plugin supports IAM Role. Manage Jenkins > System Configuration, find Spot Fleet Configuration, if you open AWS Credentials, at the bottom, it has IAM Role Support, which allows the specifying role to assume by the plugin. Thx, Artem Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196437.1545899269000.2053.1557809160209%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55343) How to use IAM role for authentication with Amazon EC2 Fleet Plugin
Title: Message Title Artem Stasiuk assigned an issue to Artem Stasiuk Jenkins / JENKINS-55343 How to use IAM role for authentication with Amazon EC2 Fleet Plugin Change By: Artem Stasiuk Assignee: Chad Schmutzer Artem Stasiuk Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196437.1545899269000.2056.1557809160260%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35438) Fleet always keeps at least one instance
Title: Message Title Artem Stasiuk commented on JENKINS-35438 Re: Fleet always keeps at least one instance Released under version ec2-fleet-1.1.9 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171235.1465324703000.2043.1557808200220%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-35438) Fleet always keeps at least one instance
Title: Message Title Artem Stasiuk resolved as Fixed Fix already merged, close ticket. Feel free to reopen it if any problem or questions. Jenkins / JENKINS-35438 Fleet always keeps at least one instance Change By: Artem Stasiuk Status: Open Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.171235.1465324703000.2033.1557808140573%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49763) Duration time is incorrect in a parallel pipeline step.
Title: Message Title Ben Walding commented on JENKINS-49763 Re: Duration time is incorrect in a parallel pipeline step. Note: my example doesn't show negatives, but does show the blueocean endpoint returning invalid timings for parallel stages, and not accumulating the time for the overall stage correctly. I suspect they're all issues in a similar section of code, so will leave my notes here. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188710.1519731897000.2014.1557805440129%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49763) Duration time is incorrect in a parallel pipeline step.
Title: Message Title
Ben Walding commented on JENKINS-49763
Re: Duration time is incorrect in a parallel pipeline step.
I've reproduced this using a similar pipeline in declarative format. Classic Stages ViewBlueOcean ViewPipeline
Jenkinsfile
pipeline {
agent {
label "docker"
}
stages {
stage('Step Serial') {
steps {
sh "sleep 5"
}
}
stage('Step Parallel') {
parallel {
stage("Primary Branch") {
steps {
sh "sleep 4"
}
}
stage("Secondary Branch") {
steps {
sh "sleep 6"
}
}
}
}
}
}
REST Response /blue/rest/organizations/jenkins/pipelines/test-timings/runs/3/nodes/?limit=1
REST Response
[
{
"_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl",
"_links": {
"self": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/test-timings/runs/3/nodes/6/"
},
"actions": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/test-timings/runs/3/nodes/6/actions/"
},
"steps": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/test-timings/runs/3/nodes/6/steps/"
}
},
"actions": [],
"displayDescription": null,
"displayName": "Step Serial",
"durationInMillis": 5573,
"id": "6",
"input": null,
"result": "SUCCESS",
"startTime": "2019-05-14T03:31:27.174+",
"state": "FINISHED",
"type": "STAGE",
"causeOfBlockage": null,
"edges": [
{
"_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl$EdgeImpl",
"id": "11",
"type": "STAGE"
}
],
"firstParent": null,
"restartable": true
},
{
"_class": "io.jenkins.blueocean.rest.impl.pipeline.PipelineNodeImpl",
"_links": {
"self": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/test-timings/runs/3/nodes/11/"
},
"actions": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/test-timings/runs/3/nodes/11/actions/"
},
"steps": {
"_class": "io.jenkins.blueocean.rest.hal.Link",
"href": "/blue/rest/organizations/jenkins/pipelines/test-timings/runs/3/nodes/11/steps/"
}
},
"actions": [],
"displayDescription": null,
"displayName": "Step Parallel",
"durationInMillis": 31,
"id":
[JIRA] (JENKINS-49763) Duration time is incorrect in a parallel pipeline step.
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-49763 Duration time is incorrect in a parallel pipeline step. Change By: Ben Walding Attachment: screenshot-1.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188710.1519731897000.2008.1557805200228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49763) Duration time is incorrect in a parallel pipeline step.
Title: Message Title Ben Walding updated an issue Jenkins / JENKINS-49763 Duration time is incorrect in a parallel pipeline step. Change By: Ben Walding Attachment: Screen Shot 2019-05-14 at 1.37.24 pm.png Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188710.1519731897000.2005.1557805080171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-23857) Coverage Breakdown by Maven Module
Title: Message Title Joey SUN commented on JENKINS-23857 Re: Coverage Breakdown by Maven Module Echo this request. Is there any way that, we can get coverage report per maven sub module? In our project, it has different packages for one submodule, so we can't get the coverage rate for each module from the report currently. Hope one workaround can be provided. Thanks. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.156321.1405608567000.2001.1557804900165%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-17614) Jenkins triggers builds on git SCM changes, but nothing changed
Title: Message Title Ryan Kenney commented on JENKINS-17614 Re: Jenkins triggers builds on git SCM changes, but nothing changed Is it possible to inspect whatever the git plugin uses to track which git hashes it hass built so far? I can't seem to find this anywhere on my jenkins master. Presumably it has to be persisted to disk on the master.. somewhere. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.148793.1366035236000.1930.1557800641217%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.
Title: Message Title anand acharya commented on JENKINS-54363 Re: ERROR: Could not send email as a part of the post-build publishers. Hi Alex, Can you please confirm when this issue will be resolved? Is there any current workaround in Jenkins to trigger emails post build? Thanks & Regards, Anand Acharya Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195113.1540977422000.1928.1557797700162%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57440) reduceLog checkbox not available in Process xUnit test result report
Title: Message Title Steven Wadsworth commented on JENKINS-57440 Re: reduceLog checkbox not available in Process xUnit test result report It would have been helpful to better announce the change in default behavior and the deprecation of Builder. The jobs I have set up all use the xUnit plugin as a build step, not a post-build step, and information necessary to debug failed tests was unexpectedly missing. Set up this way, there is no way to return to previous behavior. I have not written this into any pipelines, so had no direct visibility of Builder vs. Publisher, and I try to look at all changelogs before updating plugins. We were not experiencing the OOM. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199253.1557789679000.1925.1557795600297%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-47496) No automatic builds for tags
Title: Message Title Jay Ache edited a comment on JENKINS-47496 Re: No automatic builds for tags I found that adding a Basic Branch Build Strategy to automatically build tags interfered with the rest of the multibranch pipeline builds automatically triggered by GitHub. They were working fine, then I added a Basic Branch Build Strategy to automatically build a tag, added a new tag, the new tag was automatically discovered and it attempted to build it (but failed with a NullPtrException; I had to manually schedule the tag build again before it successfully built, but that's an unrelated issue , probably because of this: https://issues.jenkins-ci.org/browse/JENKINS-50715 ). However, subsequent pushes to branches didn't re-trigger builds as expected. Simply removing the Basic Branch Build Strategy fixed it, and builds/pull-requests were again automatically built whenever pushes happened. I'll try Mark F's JobDSL workaround next. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185952.1508325472000.1917.1557794400289%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57442) Parameterized Trigger Plugin should print link to running job
Title: Message Title Tim Armstrong created an issue Jenkins / JENKINS-57442 Parameterized Trigger Plugin should print link to running job Issue Type: Improvement Assignee: Tim Armstrong Components: parameterized-trigger-plugin Created: 2019-05-14 00:35 Labels: user-experience Priority: Minor Reporter: Tim Armstrong He have some jobs that use this plugin to launch a child job execution. A major usability headache is that you can't directly find the child execution from the parent. A link is printed to the parent job at the start, and to the specific execution once it completes, but if you look at a life job, you have to go scrounging through lists of running jobs to find the child job. 18:58:00 Waiting for the completion of parallel-all-tests 00:12:05 parallel-all-tests #5574 completed. Result was SUCCESS I started working on a potential patch for this - https://github.com/timarmstrong/parameterized-trigger-plugin I haven't worked on Jenkins code at all so would welcome feedback on whether this makes any sense and whether I'm heading in an appropriate direction.
[JIRA] (JENKINS-57442) Parameterized Trigger Plugin should print link to running job
Title: Message Title
Tim Armstrong updated an issue
Jenkins / JENKINS-57442
Parameterized Trigger Plugin should print link to running job
Change By:
Tim Armstrong
He We have some jobs that use this plugin to launch a child job execution. A major usability headache is that you can't directly find the child execution from the parent. A link is printed to the parent job at the start, and to the specific execution once it completes, but if you look at a life job, you have to go scrounging through lists of running jobs to find the child job. E.g. if you look at this log output, the job ID is only printed several hours after the job actual starts. {noformat}18:58:00 Waiting for the completion of parallel-all-tests00:12:05 parallel-all-tests #5574 completed. Result was SUCCESS {noformat} I started working on a potential patch for this - https://github.com/timarmstrong/parameterized-trigger-pluginI haven't worked on Jenkins code at all so would welcome feedback on whether this makes any sense and whether I'm heading in an appropriate direction.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Oleg Nenashev assigned an issue to Oleg Nenashev Jenkins / JENKINS-57441 Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Change By: Oleg Nenashev Assignee: Oleg Nenashev Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199254.1557791602000.1912.1557792360139%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Oleg Nenashev commented on JENKINS-57441 Re: Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 I am reverting Jetty as a temporary workaround: https://github.com/jenkinsci/jenkinsfile-runner/pull/125 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199254.1557791602000.1911.1557792360075%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title
Oleg Nenashev updated an issue
Jenkins / JENKINS-57441
Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Change By:
Oleg Nenashev
When using a Jetty version from the core (9.4.12.v20180830) on the current JFR master branch, I get the following error during the startup:{ noformat code:java }2019-05-13 23:45:58.737+ [id=1] WARNING o.e.jetty.webapp.WebAppContext#doStart: Failed startup of context o.e.j.w.WebAppContext@7ef27d7f{Jenkins v2.164.2,/jenkins,file:///app/jenkins/,UNAVAILABLE}{/app/jenkins} java.lang.IllegalStateException: No config path set at org.eclipse.jetty.security.PropertyUserStore.loadUsers(PropertyUserStore.java:246) at org.eclipse.jetty.security.PropertyUserStore.doStart(PropertyUserStore.java:329) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.security.HashLoginService.doStart(HashLoginService.java:192) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.security.SecurityHandler.doStart(SecurityHandler.java:361) at org.eclipse.jetty.security.ConstraintSecurityHandler.doStart(ConstraintSecurityHandler.java:448) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:108) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:123) at org.eclipse.jetty.server.session.SessionHandler.doStart(SessionHandler.java:503) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:108) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:123) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:908) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:370) at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:847) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:287) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545)
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Oleg Nenashev commented on JENKINS-57441 Re: Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Jetty update is the root cause. It works well after reverting the JFR Jetty version to 9.4.5.v20170502 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199254.1557791602000.1909.1557792120042%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title
Oleg Nenashev updated an issue
Jenkins / JENKINS-57441
Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Change By:
Oleg Nenashev
When using a Jetty version from the core (9.4.12.v20180830) on the current JFR master branch , I get the following error during the startup:{noformat}2019-05-13 23:45:58.737+ [id=1] WARNING o.e.jetty.webapp.WebAppContext#doStart: Failed startup of context o.e.j.w.WebAppContext@7ef27d7f{Jenkins v2.164.2,/jenkins,file:///app/jenkins/,UNAVAILABLE}{/app/jenkins} java.lang.IllegalStateException: No config path set at org.eclipse.jetty.security.PropertyUserStore.loadUsers(PropertyUserStore.java:246) at org.eclipse.jetty.security.PropertyUserStore.doStart(PropertyUserStore.java:329) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.security.HashLoginService.doStart(HashLoginService.java:192) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.security.SecurityHandler.doStart(SecurityHandler.java:361) at org.eclipse.jetty.security.ConstraintSecurityHandler.doStart(ConstraintSecurityHandler.java:448) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:108) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:123) at org.eclipse.jetty.server.session.SessionHandler.doStart(SessionHandler.java:503) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:108) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.server.handler.ScopedHandler.doStart(ScopedHandler.java:123) at org.eclipse.jetty.server.handler.ContextHandler.startContext(ContextHandler.java:908) at org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:370) at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1497) at org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1459) at org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:847) at org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:287) at org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:545) at
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2
Title: Message Title
Oleg Nenashev created an issue
Jenkins / JENKINS-57441
Warning on JFR initialization when running with Jenkins 2.164.2
Issue Type:
Bug
Assignee:
Unassigned
Components:
jenkinsfile-runner
Created:
2019-05-13 23:53
Priority:
Minor
Reporter:
Oleg Nenashev
When using a Jetty version from the core (9.4.12.v20180830), I get the following error during the startup:
2019-05-13 23:45:58.737+ [id=1] WARNING o.e.jetty.webapp.WebAppContext#doStart: Failed startup of context o.e.j.w.WebAppContext@7ef27d7f{Jenkins v2.164.2,/jenkins,file:///app/jenkins/,UNAVAILABLE}{/app/jenkins} java.lang.IllegalStateException: No config path set at org.eclipse.jetty.security.PropertyUserStore.loadUsers(PropertyUserStore.java:246) at org.eclipse.jetty.security.PropertyUserStore.doStart(PropertyUserStore.java:329) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.security.HashLoginService.doStart(HashLoginService.java:192) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117) at org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:113) at org.eclipse.jetty.security.SecurityHandler.doStart(SecurityHandler.java:361) at org.eclipse.jetty.security.ConstraintSecurityHandler.doStart(ConstraintSecurityHandler.java:448) at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) at org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:138) at org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:108) at
[JIRA] (JENKINS-57441) Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-57441 Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Change By: Oleg Nenashev Summary: Warning on JFR initialization when running with Jenkins 2.164.2 and Jetty 9.4.12.v20180830 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199254.1557791602000.1907.1557791640299%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57440) reduceLog checkbox not available in Process xUnit test result report
Title: Message Title Nikolas Falco closed an issue as Won't Fix Jenkins / JENKINS-57440 reduceLog checkbox not available in Process xUnit test result report Change By: Nikolas Falco Status: Open Closed Resolution: Won't Fix Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199253.1557789679000.1905.1557790860211%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57440) reduceLog checkbox not available in Process xUnit test result report
Title: Message Title Nikolas Falco commented on JENKINS-57440 Re: reduceLog checkbox not available in Process xUnit test result report The reason is because the builder is deprecated. I left just to be back compatible for people that had written pipeline using step($class: XUnitBuilder,...) It can use only default configuration that prevents OOM in jenkins (the same of JUnit plugins) Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199253.1557789679000.1903.1557790440141%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57440) reduceLog checkbox not available in Process xUnit test result report
Title: Message Title Steven Wadsworth created an issue Jenkins / JENKINS-57440 reduceLog checkbox not available in Process xUnit test result report Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2019-05-13 23:21 Environment: xunit-plugin 2.3.3 Priority: Minor Reporter: Steven Wadsworth New reduceLog setting changes default behavior, and if plugin is being used as a Build Step there is no way to restore the old behavior through the GUI. If the plugin is used as Post-build Action, the GUI does show the new checkbox under Advanced. Looking at the source, the setting was added to src/main/resources/org/jenkinsci/plugins/xunit/XUnitPublisher but not to src/main/resources/org/jenkinsci/plugins/xunit/XUnitBuilder The two sets of settings look to like they should be the same. Adding the new checkbox and properties to the XUnitBuilder resources gives the desired result, but if the settings are intended to be identical, combining these to a single point of maintenance would be preferable. As it is, the title and description for the report time margin are also out of sync between the two.
[JIRA] (JENKINS-52737) Using a docker agent from a private registry does pass the proxy configuration to the docker container
Title: Message Title Oleg Nenashev updated JENKINS-52737 Jenkins / JENKINS-52737 Using a docker agent from a private registry does pass the proxy configuration to the docker container Change By: Oleg Nenashev Status: Open Fixed but Unreleased Assignee: Andrew Bayer Resolution: Fixed Released As: Docker Commons Plugin 1.15 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192630.1532520749000.1891.1557784381003%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57439) Add Declarative Credentials handler for Docker
Title: Message Title Oleg Nenashev updated JENKINS-57439 Jenkins / JENKINS-57439 Add Declarative Credentials handler for Docker Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Docker Commons Plugin 1.15 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199252.155778171.1875.1557784320511%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52737) Using a docker agent from a private registry does pass the proxy configuration to the docker container
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52737 Using a docker agent from a private registry does pass the proxy configuration to the docker container Change By: Oleg Nenashev Component/s: docker-commons-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192630.1532520749000.1888.1557784380884%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57420) Use the new multiline secret field in docker-commons
Title: Message Title Oleg Nenashev updated JENKINS-57420 Jenkins / JENKINS-57420 Use the new multiline secret field in docker-commons Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199231.1557733016000.1899.1557784381143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52737) Using a docker agent from a private registry does pass the proxy configuration to the docker container
Title: Message Title Oleg Nenashev updated JENKINS-52737 Jenkins / JENKINS-52737 Using a docker agent from a private registry does pass the proxy configuration to the docker container Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192630.1532520749000.1893.1557784381045%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57420) Use the new multiline secret field in docker-commons
Title: Message Title Oleg Nenashev updated JENKINS-57420 Jenkins / JENKINS-57420 Use the new multiline secret field in docker-commons Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Docker Commons Plugin 1.15 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199231.1557733016000.1896.1557784381104%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52724) Building an image with a custom registry overwrites environment variables
Title: Message Title Oleg Nenashev updated JENKINS-52724 Jenkins / JENKINS-52724 Building an image with a custom registry overwrites environment variables Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192615.1532442915000.1881.1557784320647%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57439) Add Declarative Credentials handler for Docker
Title: Message Title Oleg Nenashev updated JENKINS-57439 Jenkins / JENKINS-57439 Add Declarative Credentials handler for Docker Change By: Oleg Nenashev Status: Fixed but Unreleased Resolved Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199252.155778171.1876.1557784320565%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52724) Building an image with a custom registry overwrites environment variables
Title: Message Title Oleg Nenashev updated an issue Jenkins / JENKINS-52724 Building an image with a custom registry overwrites environment variables Change By: Oleg Nenashev Component/s: docker-commons-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192615.1532442915000.1884.1557784320696%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-52724) Building an image with a custom registry overwrites environment variables
Title: Message Title Oleg Nenashev updated JENKINS-52724 Jenkins / JENKINS-52724 Building an image with a custom registry overwrites environment variables Change By: Oleg Nenashev Status: Open Fixed but Unreleased Resolution: Fixed Released As: Docker Commons Plugin 1.15 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.192615.1532442915000.1879.1557784320608%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-54363) ERROR: Could not send email as a part of the post-build publishers.
Title: Message Title Alex Earl commented on JENKINS-54363 Re: ERROR: Could not send email as a part of the post-build publishers. That corresponds to this line of code: https://github.com/jenkinsci/email-ext-plugin/blob/email-ext-2.66/src/main/java/hudson/plugins/emailext/ExtendedEmailPublisherDescriptor.java#L244 I can add some checking in there to make sure things aren't null. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.195113.1540977422000.1873.1557783180224%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57320) Fix a possible regression introduced on JENKINS-56312
Title: Message Title Oleg Nenashev updated JENKINS-57320 Jenkins / JENKINS-57320 Fix a possible regression introduced on JENKINS-56312 Change By: Oleg Nenashev Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199090.1556886713000.1871.1557782040251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55287) Pipeline: Failure to load flow node: FlowNode was not found in storage for head
Title: Message Title Jason MCDev commented on JENKINS-55287 Re: Pipeline: Failure to load flow node: FlowNode was not found in storage for head Craig Rodrigues We are always running full clean builds, so I concur that the suggestion does not fit our use case. It has really been causing us headaches for sure - random failures in release pipelines. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196374.1545361815000.1857.1557781800282%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57439) Add Declarative Credentials handler for Docker
Title: Message Title Oleg Nenashev created an issue Jenkins / JENKINS-57439 Add Declarative Credentials handler for Docker Issue Type: New Feature Assignee: Unassigned Components: docker-commons-plugin Created: 2019-05-13 21:08 Priority: Minor Reporter: Oleg Nenashev Placeholder for https://github.com/jenkinsci/docker-commons-plugin/pull/77/ Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title Ulli Hafner closed an issue as Cannot Reproduce Ok, I'm closing it. If you see it a again please reopen and provide a pointer to the wrong message. Jenkins / JENKINS-57378 warnings-ng commands show up as General Build Step in pipeline views Change By: Ulli Hafner Status: Open Closed Resolution: Cannot Reproduce Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199159.155735243.1854.1557781260219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57428) Duplicate warnings when using error-prone and java scan
Title: Message Title Ulli Hafner updated an issue Jenkins / JENKINS-57428 Duplicate warnings when using error-prone and java scan Change By: Ulli Hafner Issue Type: Bug Improvement Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199240.1557749846000.1852.1557781140228%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57428) Duplicate warnings when using error-prone and java scan
Title: Message Title Ulli Hafner commented on JENKINS-57428 Re: Duplicate warnings when using error-prone and java scan Yes, both parsers match the same warning line. Just error prone has some additional entries. I'm not sure what a good approach would be to eliminate these duplicates. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199240.1557749846000.1850.1557781140202%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Jon Starbird assigned an issue to Unassigned Jenkins / JENKINS-57438 Blue Ocean multibranch scan queuing should not add to queue if job already queued Change By: Jon Starbird Component/s: bitbucket-branch-source-plugin Component/s: bitbucket-plugin Component/s: blueocean-plugin Component/s: multibranch-scan-webhook-trigger-plugin Assignee: Jon Starbird Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Igal Gluh assigned an issue to Jon Starbird Jenkins / JENKINS-57438 Blue Ocean multibranch scan queuing should not add to queue if job already queued Change By: Igal Gluh Assignee: Igal Gluh Jon Starbird Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199251.1557771219000.1844.1557780720246%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Jon Starbird commented on JENKINS-57438 Re: Blue Ocean multibranch scan queuing should not add to queue if job already queued Igal Gluh thanks, I wasn't sure which part was controlling this. Thanks for your time and changing the component. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199251.1557771219000.1845.1557780720265%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title Ulli Hafner commented on JENKINS-57312 Re: Provide tokens for new and fixed warnings Matthew Dews I have no idea on how to consume tokens in a declarative pipeline. Maybe here you should better ask on the mailing list or Gitter channel (or IRC). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.1841.1557780660113%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Igal Gluh commented on JENKINS-57438 Re: Blue Ocean multibranch scan queuing should not add to queue if job already queued It's look like the plugin is not installed on your jenkins instance Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199251.1557771219000.1839.1557780600100%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Igal Gluh commented on JENKINS-57438 Re: Blue Ocean multibranch scan queuing should not add to queue if job already queued Jon hi , It's not connected to " multibranch-scan-webhook-trigger-plugin" , It's something else. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199251.1557771219000.1837.1557780540146%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title
Ulli Hafner edited a comment on JENKINS-57312
Re: Provide tokens for new and fixed warnings
[~christiantreczoks] The {{action}} from above has a {{getDisplayName()}} method that shows the link name in the side panel. Or you can call {{getLabelProvider()}} to obtain an instance of the `LabelProvider` that handles all of the labels.If you have a working example it would be quite helpful for others if we can put it into [Documentation.md|https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md] file.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.1830.1557780480247%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Igal Gluh updated an issue Jenkins / JENKINS-57438 Blue Ocean multibranch scan queuing should not add to queue if job already queued Change By: Igal Gluh Component/s: multibranch-scan-webhook-trigger-plugin Component/s: bitbucket-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199251.1557771219000.1835.1557780480362%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title
Ulli Hafner edited a comment on JENKINS-57312
Re: Provide tokens for new and fixed warnings
[~christiantreczoks] The {{action}} from above has a {{getDisplayName()}} method that shows the link name in the side panel. Or you can call {{getLabelProvider()}} to obtain an instance of the `LabelProvider` that handles all of the labels. If you have a working example it would be quite helpful for others if we can put it into the [Documentation.md|https://github.com/jenkinsci/warnings-ng-plugin/blob/master/doc/Documentation.md] file.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.1833.1557780480311%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57411) Upgrade github-branch-source-plugin to use okhttp3
Title: Message Title Liam Newman commented on JENKINS-57411 Re: Upgrade github-branch-source-plugin to use okhttp3 Josh Soref Cool thanks. I'm really not sure what would the periodic scans to not run. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199216.1557540525000.1826.1557780360357%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title
Ulli Hafner edited a comment on JENKINS-57312
Re: Provide tokens for new and fixed warnings
[~christiantreczoks] The {{action}} from above has a {{getDisplayName()}} method that shows the link name in the side panel. Or you can call {{ getLabelProvider()}} to obtain an instance of the `LabelProvider` that handles all of the labels.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.1825.1557780360327%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title
Ulli Hafner edited a comment on JENKINS-57312
Re: Provide tokens for new and fixed warnings
[~christiantreczoks] The ` {{ action ` }} from above has a ` {{ getDisplayName() ` }} method that show shows the link name in the side panel. Or you can call ` {{ getLabelProvider() ` }} to obtain an instance of the `LabelProvider` that handles all of the labels.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.1822.1557780360275%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57312) Provide tokens for new and fixed warnings
Title: Message Title Ulli Hafner commented on JENKINS-57312 Re: Provide tokens for new and fixed warnings Christian Treczoks The `action` from above has a `getDisplayName()` method that show the link name in the side panel. Or you can call `getLabelProvider()` to obtain an instance of the `LabelProvider` that handles all of the labels. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199081.1556811582000.1818.1557780240149%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Igal Gluh updated an issue Jenkins / JENKINS-57438 Blue Ocean multibranch scan queuing should not add to queue if job already queued Change By: Igal Gluh Component/s: bitbucket-plugin Component/s: multibranch-scan-webhook-trigger-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199251.1557771219000.1816.1557780120134%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57371) error message when building PR
Title: Message Title Liam Newman commented on JENKINS-57371 Re: error message when building PR Niklas Claesson Excellent! Brandon Le Sann Yes, the only changes in 2.5.x were ones that changed the way PRs were handled. So, branches not being effected makes sense. The behavior you're seeing is truly odd. But if it is all clear now, that is the important part. I'm going to leave this open in case there are other who see upgrade issues to v2.5.2. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199152.155732120.1814.1557779760135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57378) warnings-ng commands show up as General Build Step in pipeline views
Title: Message Title Jason Faust commented on JENKINS-57378 Re: warnings-ng commands show up as General Build Step in pipeline views Fell free to close this as a bogus report. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199159.155735243.1811.1557779700251%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Jon Starbird updated an issue Jenkins / JENKINS-57438 Blue Ocean multibranch scan queuing should not add to queue if job already queued Change By: Jon Starbird Attachment: j1.PNG Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199251.1557771219000.1805.1557779160219%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Jon Starbird commented on JENKINS-57438 Re: Blue Ocean multibranch scan queuing should not add to queue if job already queued Not sure how much you want but gave the setting for polling. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199251.1557771219000.1807.1557779160257%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49787) Jenkins.createProjectFromXml() formats xml differently than AbstractItem.save()
Title: Message Title Reto Hoehener commented on JENKINS-49787 Re: Jenkins.createProjectFromXml() formats xml differently than AbstractItem.save() Would be nice if at least the empty element strategy could be consistent within the file: Either expand or collapse all empty tags. We also backup (and version) our hundreds of job confix.xml files, and sometimes modify them programmatically. Currently it is impossible to modify just a single element with an XML processing library like JDOM, without getting a ton of changes because of the inconsistent empty tags. The whitespace differences are not a problem, as for example the eclipse diff editor can be configured to ignore those. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.188737.1519803395000.1800.1557778220280%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Igal Gluh commented on JENKINS-57438 Re: Blue Ocean multibranch scan queuing should not add to queue if job already queued Please attach a job configuration screenshot Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199251.1557771219000.1797.155900254%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-55214) NullPointerException when starting a pipeline in a multibranch project
Title: Message Title kyle ian commented on JENKINS-55214 Re: NullPointerException when starting a pipeline in a multibranch project Ran into this today on 1.9.7 - it appeared to me the cause was a poorly formed parameter block passed to the (node) pipeline on one of my branches. Added new description to parameter on one branch, missing comma after description (groovy linter would've picked it up) All builds under multi pipeline failed with error noted in OP when solely one of the multipipeline branches had bad parameter configuration fixed comma on bad branch parameter configuration (single branch), rescanned multipipeline reran pipeline build for each branch, confirmed fixing that parameter block to be well formed resulted in all successful pipeline builds for each branch I have not been able to reproduce it after fixing this parameter block // have not tried breaking it again. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.196286.1544938736000.1794.1557776520156%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Mario Jauvin commented on JENKINS-57324 Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch From what I understand the code, the method setupMaven which defines and overrides the MAVEN_CONFIG environment variable is not Windows specific so that making the change in that method would require knowing the platform. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.1790.1557776160175%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title
Mario Jauvin edited a comment on JENKINS-57324
Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch
I did and the problem is that when the with maven wrapper script is created, the pathnames contain %2F which when invoked inside the wrapper scripts get evaluated as arguments. Here is the log output from WithMavenStepExecution2: {noformat}Generated Maven wrapper script: @echo offecho - withMaven Wrapper script -"C:\APPS\apache-maven-3.6.0\bin\mvn.cmd" --batch-mode --show-version --settings "e:\cc-build\checkout\abc\citest\branches%2Ftest\workspace@tmp\withMaven94865076\settings.xml" --global-settings "e:\cc-build\checkout\abc\citest\branches%2Ftest\workspace@tmp\withMaven94865076\globalSettings.xml" %*{noformat}when calling maven in that manner, it will not work. The generated wrapper script should double the % signs in each path argument. For example: {noformat}@echo offecho - withMaven Wrapper script -"C:\APPS\apache-maven-3.6.0\bin\mvn.cmd" --batch-mode --show-version --settings "e:\cc-build\checkout\aws\citest\branches%%2Ftest\workspace@tmp\withMaven94865076\settings.xml" --global-settings "e:\cc-build\checkout\aws\citest\branches%%2Ftest\workspace@tmp\withMaven94865076\globalSettings.xml" %*{noformat} I tested modifying the withMaven wrapper script manually and it works.
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.1787.1557774720147%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Mario Jauvin commented on JENKINS-57324 Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch I did and the problem is that when the with maven wrapper script is created, the pathnames contain %2F which when invoked inside the wrapper scripts get evaluated as arguments. Here is the log output from WithMavenStepExecution2: Generated Maven wrapper script: @echo off echo - withMaven Wrapper script - "C:\APPS\apache-maven-3.6.0\bin\mvn.cmd" --batch-mode --show-version --settings "e:\cc-build\checkout\abc\citest\branches%2Ftest\workspace@tmp\withMaven94865076\settings.xml" --global-settings "e:\cc-build\checkout\abc\citest\branches%2Ftest\workspace@tmp\withMaven94865076\globalSettings.xml" %* when calling maven in that manner, it will not work. The generated wrapper script should double the % signs in each path argument. For example: @echo off echo - withMaven Wrapper script - "C:\APPS\apache-maven-3.6.0\bin\mvn.cmd" --batch-mode --show-version --settings "e:\cc-build\checkout\aws\citest\branches%%2Ftest\workspace@tmp\withMaven94865076\settings.xml" --global-settings "e:\cc-build\checkout\aws\citest\branches%%2Ftest\workspace@tmp\withMaven94865076\globalSettings.xml" %* Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the
[JIRA] (JENKINS-57396) Pods Terminate before container image can download
Title: Message Title Carlos Sanchez commented on JENKINS-57396 Re: Pods Terminate before container image can download just set slaveConnectTimeout in the template Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199178.1557479229000.1781.1557771660171%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57438) Blue Ocean multibranch scan queuing should not add to queue if job already queued
Title: Message Title Jon Starbird created an issue Jenkins / JENKINS-57438 Blue Ocean multibranch scan queuing should not add to queue if job already queued Issue Type: Bug Assignee: Igal Gluh Components: multibranch-scan-webhook-trigger-plugin Created: 2019-05-13 18:13 Environment: Jenkins - 2.164.2 - blueocean multibranch builds Bitbucket Cloud Priority: Major Reporter: Jon Starbird Apologies if I did not pick the correct component for this, please change to the correct one if needed. When using Polling instead of build requests from Bitbucket, business environment requirement, Jenkins will add repeated multibranch scans to the job queue even when one is already queued. This occurs because Bitbucket cloud has limitations on API use so if enough requests come in the queue gets back logged. Jenkins should not be adding requests for multibranch scans to the queue if one already exists for that job. Since the scan only uses one executor on the main server this causes the queue to fill up and slow builds down dramatically.
[JIRA] (JENKINS-53950) Support configuration as code
Title: Message Title René Scheibe assigned an issue to Aleksi Simell Jenkins / JENKINS-53950 Support configuration as code Change By: René Scheibe Assignee: René Scheibe Aleksi Simell Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.194552.1539028394000.1774.1557769500329%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57396) Pods Terminate before container image can download
Title: Message Title
Daniel Watrous updated an issue
Jenkins / JENKINS-57396
Pods Terminate before container image can download
Change By:
Daniel Watrous
I have a build that uses 9 containers, but the Pod never gets to start because it can't finish downloading in the amount of time (100 seconds) that the kubernetes plugin allows.{code:java}io.fabric8.kubernetes.client.KubernetesClientTimeoutException: Timed out waiting for [10] milliseconds for [Pod] with name:[api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191] in namespace [jenkins]. at org.csanchez.jenkins.plugins.kubernetes.AllContainersRunningPodWatcher.await(AllContainersRunningPodWatcher.java:134) at org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:128) at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46) at jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748)May 10, 2019 8:57:17 AM FINER org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncherRemoving Jenkins node: api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191May 10, 2019 8:57:17 AM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminateTerminating Kubernetes instance for agent api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191May 10, 2019 8:57:17 AM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesCloudBuilding connection to Kubernetes k8s-houston URL https://api.eng. houston company . trinet-k8s. com: 7443 6443 / namespace jenkinsMay 10, 2019 8:57:17 AM FINE org.csanchez.jenkins.plugins.kubernetes.KubernetesCloudConnected to Kubernetes k8s-houston URL https://api.eng. houston company . trinet-k8s. com: 7443 6443 /May 10, 2019 8:57:17 AM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave deleteSlavePodTerminated Kubernetes instance for agent jenkins/api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191May 10, 2019 8:57:17 AM INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminateDisconnected computer api-build-4f60479c-c124-4d8b-a7e6-3f27f05e163d-570px-5n191{code}I would like to be able to set this in the settings, or at least as an argument when I start Jenkins.
[JIRA] (JENKINS-57417) configFileProvider / withCredentials not working in declarative pipeline
Title: Message Title Richard Davis updated JENKINS-57417 Jenkins / JENKINS-57417 configFileProvider / withCredentials not working in declarative pipeline Change By: Richard Davis Resolution: Not A Defect Status: Resolved In Review Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199223.1557587492000.1769.1557769080231%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Cyrille Le Clerc edited a comment on JENKINS-57324 Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch [~marioja] could you please enable the Jenkins logs on the logger "org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution2" to "FINER" and re run the build please?Troubleshooting message will be added in the console of your build.Reference: https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.6.12/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution2.java#L684 [~domi] I'm assigning the ticket to me Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.1767.1557769020125%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Cyrille Le Clerc assigned an issue to Cyrille Le Clerc Jenkins / JENKINS-57324 Error running maven with settings file when running multibranch pipeline with a slash in the branch Change By: Cyrille Le Clerc Assignee: Dominik Bartholdi Cyrille Le Clerc Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.1763.1557768960591%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Cyrille Le Clerc updated an issue Jenkins / JENKINS-57324 Error running maven with settings file when running multibranch pipeline with a slash in the branch Change By: Cyrille Le Clerc Component/s: pipeline-maven-plugin Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.1759.1557768960486%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57324) Error running maven with settings file when running multibranch pipeline with a slash in the branch
Title: Message Title Cyrille Le Clerc commented on JENKINS-57324 Re: Error running maven with settings file when running multibranch pipeline with a slash in the branch Mario Jauvin could you please enable the Jenkins logs on the logger "org.jenkinsci.plugins.pipeline.maven.WithMavenStepExecution2" to "FINER" and re run the build please? Troubleshooting message will be added in the console of your build. Reference: https://github.com/jenkinsci/pipeline-maven-plugin/blob/pipeline-maven-3.6.12/jenkins-plugin/src/main/java/org/jenkinsci/plugins/pipeline/maven/WithMavenStepExecution2.java#L684 Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199095.1556895401000.1755.1557768960388%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56071) Pipeline (workflow job) support
Title: Message Title Pavel Roskin updated an issue Jenkins / JENKINS-56071 Pipeline (workflow job) support Change By: Pavel Roskin Summary: Workflow Pipeline (workflow job ) support Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197496.1549797931000.1752.1557768840143%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56071) Workflow job support
Title: Message Title Pavel Roskin commented on JENKINS-56071 Re: Workflow job support PR #69 will add pipeline support. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.197496.1549797931000.1750.1557768660135%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title
edburns edited a comment on JENKINS-56890
Re: IOException: "cannot find current thread"
Jenkins version : h1. 2.164.2 Pipeline: Basic Steps 2.15 Pipeline: Build Step 2.9 Pipeline: Groovy 2.67 Pipeline: Nodes and Processes 2.30 I am seeing this also:{quote}java.io.IOException: cannot find current thread at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:300) at org.jenkinsci.plugins.workflow.cps.CpsBodySubContext.doGet(CpsBodySubContext.java:88) at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:67) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Callback.finished(BindingStep.java:254) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2$Callback2.finished(BindingStep.java:162) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:140) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){quote}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198561.1554419267000.1727.1557767160477%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57437) Update jenkins.io page for the Role Strategy GSoC 2019 project
Title: Message Title Abhyudaya Sharma assigned an issue to Abhyudaya Sharma Jenkins / JENKINS-57437 Update jenkins.io page for the Role Strategy GSoC 2019 project Change By: Abhyudaya Sharma Assignee: Oleg Nenashev Abhyudaya Sharma Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199250.1557766913000.1700.1557766980507%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56890) IOException: "cannot find current thread"
Title: Message Title
edburns edited a comment on JENKINS-56890
Re: IOException: "cannot find current thread"
Jenkins version:h1. 2.164.2 I am seeing this also:{quote}java.io.IOException: cannot find current thread at org.jenkinsci.plugins.workflow.cps.CpsStepContext.doGet(CpsStepContext.java:300) at org.jenkinsci.plugins.workflow.cps.CpsBodySubContext.doGet(CpsBodySubContext.java:88) at org.jenkinsci.plugins.workflow.support.DefaultStepContext.get(DefaultStepContext.java:67) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Callback.finished(BindingStep.java:254) at org.jenkinsci.plugins.credentialsbinding.impl.BindingStep$Execution2$Callback2.finished(BindingStep.java:162) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution$TailCall.lambda$onSuccess$0(GeneralNonBlockingStepExecution.java:140) at org.jenkinsci.plugins.workflow.steps.GeneralNonBlockingStepExecution.lambda$run$0(GeneralNonBlockingStepExecution.java:77) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748){quote}
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.198561.1554419267000.1703.1557766980547%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-57437) Update jenkins.io page for the Role Strategy GSoC 2019 project
Title: Message Title Abhyudaya Sharma created an issue Jenkins / JENKINS-57437 Update jenkins.io page for the Role Strategy GSoC 2019 project Issue Type: Improvement Assignee: Oleg Nenashev Components: role-strategy-plugin Created: 2019-05-13 17:01 Priority: Minor Reporter: Abhyudaya Sharma Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199250.1557766913000.1697.1557766920245%40Atlassian.JIRA. For more options, visit
[JIRA] (JENKINS-57422) Verify and cleanup Docker performance test configuration
Title: Message Title Abhyudaya Sharma started work on JENKINS-57422 Change By: Abhyudaya Sharma Status: Open In Progress Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.199234.1557738945000.1693.1557766800327%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
