[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Liam Newman closed an issue as Fixed Bulk closing resolved issues. Jenkins / JENKINS-50833 NoSuchMethodError causing Pipeline editor to not see agent settings Change By: Liam Newman Status: Resolved Closed Add Comment This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- You received this message because you are subscribed to the Google 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.189947.1523918983000.16299.1571801050347%40Atlassian.JIRA.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title SCM/JIRA link daemon commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings Code changed in jenkins User: Andrew Bayer Path: pipeline-model-definition/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/generator/AgentDirective.java pipeline-model-extensions/src/main/java/org/jenkinsci/plugins/pipeline/modeldefinition/agent/DeclarativeAgentDescriptor.java http://jenkins-ci.org/commit/pipeline-model-definition-plugin/6b0e8f283437061169ae87dab25d44175e0afad0 Log: [FIXED JENKINS-50833] Revert DeclarativeAgentDescriptor.all() signature Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Andrew Bayer updated JENKINS-50833 Merged, releasing in Declarative 1.2.9 later today. Jenkins / JENKINS-50833 NoSuchMethodError causing Pipeline editor to not see agent settings Change By: Andrew Bayer Status: In Review Resolved Resolution: Fixed Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Andrew Bayer updated JENKINS-50833 Jenkins / JENKINS-50833 NoSuchMethodError causing Pipeline editor to not see agent settings Change By: Andrew Bayer Status: In Progress Review Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Andrew Bayer commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings PR up that should fix this at https://github.com/jenkinsci/pipeline-model-definition-plugin/pull/263 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Andrew Bayer started work on JENKINS-50833 Change By: Andrew Bayer Status: Open In Progress Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Alex White commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings I noticed this issue yesterday after using Pipeline and Blue Ocean for the first time and was very confused. I tried downgrading to Pipeline 2.4 from 2.5 but it still appears that `pipeline-model-definition 1.2.8` is the dependency there. I don't see a way to easily downgrade that specific dependency Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Vivek Pandey commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings Basically if users upgrade to pipeline-model-definition 1.2.8, this incompatibility will cause pipeline editor to be non-functional. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-50833
NoSuchMethodError causing Pipeline editor to not see agent settings
Change By:
Karl Shultz
*Summary*After taking the upgrade to Declarative 1. 28 2.8 , previously working Blue Ocean pipelines don't work correctly inside the editor. The editor still works, but the ability to change the agent type has gone missing. This was originally reported as Blue Ocean bug [JENKINS-50805|https://issues.jenkins-ci.org/browse/JENKINS-50805]. *Steps to recreate*1. Set up Blue Ocean to connect to a previously working Pipeline, or open a preexisting Pipeline.2. Launch the pipeline editor, and notice that there's no "Agent" settings available: !image-2018-04-16-18-40-00-833.png|thumbnail! 3. In the Jenkins log, you'll see the following {{InvocationTargetException}}, caused by a {{NoSuchMethodException}}: {code:none}Apr 16, 2018 10:29:19 PM org.eclipse.jetty.server.handler.ContextHandler$Context logWARNING: Error while serving http://172.18.40.95:8080/blue/rest/pipeline-metadata/agentMetadatajava.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.ForwardingFunction.invoke(ForwardingFunction.java:63) at io.jenkins.blueocean.commons.stapler.TreeResponse$Processor.invoke(TreeResponse.java:43) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Karl Shultz updated an issue Jenkins / JENKINS-50833 NoSuchMethodError causing Pipeline editor to not see agent settings Change By: Karl Shultz Environment: Jenkins:- Core 2.116- Blue Ocean 1.5.0- Declarative 1. 28 2.8 - Experimental update center everything elseClient:- Fedora workstation, updated and running the latest available version of Chrome Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Karl Shultz commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings Setting up a link relationship between the originally-reported issue and this one. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title
Karl Shultz updated an issue
Jenkins / JENKINS-50833
NoSuchMethodError causing Pipeline editor to not see agent settings
Change By:
Karl Shultz
*Summary*After taking the upgrade to Declarative 1.28, previously working Blue Ocean pipelines don't work correctly inside the editor. The editor still works, but the ability to change the agent type has gone missing. This was originally reported as Blue Ocean bug [JENKINS-50805|https://issues.jenkins-ci.org/browse/JENKINS-50805]. *Steps to recreate*1. Set up Blue Ocean to connect to a previously working Pipeline, or open a preexisting Pipeline.2. Launch the pipeline editor, and notice that there's no "Agent" settings available: !image-2018-04-16-18-40-00-833.png|thumbnail! 3. In the Jenkins log, you'll see the following {{InvocationTargetException}}, caused by a {{NoSuchMethodException}}: {code:none}Apr 16, 2018 10:29:19 PM org.eclipse.jetty.server.handler.ContextHandler$Context logWARNING: Error while serving http://172.18.40.95:8080/blue/rest/pipeline-metadata/agentMetadatajava.lang.reflect.InvocationTargetException at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:347) at org.kohsuke.stapler.ForwardingFunction.invoke(ForwardingFunction.java:63) at io.jenkins.blueocean.commons.stapler.TreeResponse$Processor.invoke(TreeResponse.java:43) at org.kohsuke.stapler.PreInvokeInterceptedFunction.invoke(PreInvokeInterceptedFunction.java:26) at org.kohsuke.stapler.Function.bindAndInvoke(Function.java:184) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:117) at org.kohsuke.stapler.MetaClass$1.doDispatch(MetaClass.java:129) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:686) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.MetaClass$10.dispatch(MetaClass.java:374) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:715) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:845) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:649) at org.kohsuke.stapler.Stapler.service(Stapler.java:238) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:225) at
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Karl Shultz commented on JENKINS-50833 Re: NoSuchMethodError causing Pipeline editor to not see agent settings Can also be recreated via: docker run \ --rm \ -u root \ -p 8080:8080 \ -v jenkins-data:/var/jenkins_home \ -v /var/run/docker.sock:/var/run/docker.sock \ -v "$HOME":/home \ jenkinsci/blueocean Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-50833) NoSuchMethodError causing Pipeline editor to not see agent settings
Title: Message Title Karl Shultz created an issue Jenkins / JENKINS-50833 NoSuchMethodError causing Pipeline editor to not see agent settings Issue Type: Bug Assignee: Andrew Bayer Attachments: image-2018-04-16-18-40-00-833.png Components: pipeline-model-definition-plugin Created: 2018-04-16 22:49 Environment: Jenkins: - Core 2.116 - Blue Ocean 1.5.0 - Declarative 1.28 - Experimental update center everything else Client: - Fedora workstation, updated and running the latest available version of Chrome Priority: Major Reporter: Karl Shultz Summary After taking the upgrade to Declarative 1.28, previously working Blue Ocean pipelines don't work correctly inside the editor. The editor still works, but the ability to change the agent type has gone missing. This was originally reported as Blue Ocean bug JENKINS-50805. Steps to recreate 1. Set up Blue Ocean to connect to a previously working Pipeline, or open a preexisting Pipeline. 2. Launch the pipeline editor, and notice that there's no "Agent" settings available: 3. In the Jenkins log, you'll see the following InvocationTargetException, caused by a NoSuchMethodException: Apr 16, 2018 10:29:19 PM org.eclipse.jetty.server.handler.ContextHandler$Context log WARNING: Error while serving http://172.18.40.95:8080/blue/rest/pipeline-metadata/agentMetadata java.lang.reflect.InvocationTargetException at
