[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Oliver Gondža updated JENKINS-59145 Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Oliver Gondža Status: Fixed but Unreleased Resolved Released As: 0.6 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.201579.156710687.8433.1580320803736%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Oliver Gondža updated JENKINS-59145 Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Oliver Gondža Status: Open Fixed but Unreleased Resolution: Fixed 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.201579.156710687.8420.1580320803323%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Oliver Gondža commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Sorry, I failed to report back on the progress here. The rendering issue was addressed in 0.6: https://github.com/jenkinsci/permissive-script-security-plugin/pull/4 Adam Koch, if you believe there are some other outstanding issues, please report them separately. 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.201579.156710687.8407.1580320803122%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title
Adam Koch edited a comment on JENKINS-59145
Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Adding my 2¢... I don't have Prometheus but was seeing the issue. I downgraded permissive-script-security plugin from 0.5 to 0.4 and I'm no longer having the issue.I downloaded the plugin here: [https://updates.jenkins-ci.org/download/plugins/permissive-script-security/] Update 2020-01-29: After trying with 0.4 I was having issues when approving scripts: the approval would not be saved and I was asked again for approval. So I am on 0.6. I am trying with no_security but get an error running my jobs. {code:java}org.jenkinsci.plugins.scriptsecurity.scripts.UnapprovedUsageException: script not yet approved for use at org.jenkinsci.plugins.scriptsecurity.scripts.ScriptApproval.using(ScriptApproval.java:474) at org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition.create(CpsFlowDefinition.java:120) at org.jenkinsci.plugins.workflow.cps.CpsFlowDefinition.create(CpsFlowDefinition.java:67) at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:299) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:427){code}I'm still looking into this. I've got to understand ScriptApproval.using()
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
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Adam Koch commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Adding my 2¢... I don't have Prometheus but was seeing the issue. I downgraded permissive-script-security plugin from 0.5 to 0.4 and I'm no longer having the issue. I downloaded the plugin here: https://updates.jenkins-ci.org/download/plugins/permissive-script-security/ 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.201579.156710687.7435.1580227200627%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title László Kovács commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI It seems like a recurring problem with security plugins no matter what Jenkins versions we are using. With 2.138.3 Jenkins version after updating script-security plugin to version to 1.68 and permissive-script-security plugin is 0.5. We don't use Prometheus plugin, but the issue is still the same. As I see new permissive-script-security plugin version (0.5) has complications with several other plugin and there is no fix for it currently. So you have to downgrade plugins to solve the issue. 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.201579.156710687.6493.1578667740670%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Peter Wiseman commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Config.xml and org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml attached. config.xml org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml 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.201579.156710687.15303.1577160960309%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Peter Wiseman updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Peter Wiseman Attachment: org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml 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.201579.156710687.15301.1577160901779%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Peter Wiseman updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Peter Wiseman Attachment: config.xml 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.201579.156710687.15290.1577160901280%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Michal Kovarik commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Prometheus plugin 2.0.6 without permissive-security-plugin works. Prometheus plugin 2.0.0 and permissive-security-plugin 0.5 works. Prometheus plugin 2.0.6 and permissive-security-plugin 0.5 does not work regardless permissive-script-security.enabled setting. During startup of Jenkins there are issues with prometheus - https://issues.jenkins-ci.org/browse/JENKINS-59675?focusedCommentId=377073 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.201579.156710687.9738.1576589580555%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Oliver Gondža commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI permissive-script-security maintainer here, I failed to reproduce this with version 0.5 installed and enabled so I suspect there must be something else involved. Please share the config.xml of the affected job and org.jenkinsci.plugins.workflow.libs.GlobalLibraries.xml, where there is reported the stored config (of one or the other) is not rendered in UI. 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.201579.156710687.8897.1576507082768%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Peter Wiseman commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI I tried Permissive Script Security 0.4. It does not have the issue. 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.201579.156710687.3342.1575961860725%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Peter Wiseman updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Peter Wiseman Labels: NPE jenkins script-security security 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.201579.156710687.3310.1575959220595%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Peter Wiseman commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI With Permissive Script Security at 0.5, the Global Pipeline Library SCM configuration information is no longer visible. If that were all it might be ok, but upon saving, the configuration, is removed. 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.201579.156710687.3274.1575957720360%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI daniel zhang Your suggestion fixed our issue ! Thank you so very much, this issue was very annoying to us. 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.201579.156710687.5268.1574356620394%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title daniel zhang commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Mohamed ELHOSSARY This issue may be related with the Permissive Script Security Plugin. Although I don't know how it leads to this issue. We configured "-Dpermissive-script-security.enabled=no_security" in our Jenkins with Permissive Script Security Plugin 0.3 and every thing works fine. But after I upgrade the plugin to 0.5, issue happened and downgrade to 0.3 Jenkins is back to normal. Hope this information could help you. 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.201579.156710687.4827.1574319900520%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI so how can I tackle this ? We are quite affected by this issue and it is causing a lot of stress in the daily tasks. 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.201579.156710687.1938.1568991840469%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Jacek Kowalski commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI The problem occurs when Jenkins switches from rendering configuration fields directly (in the source of /job/.../configure) to requesting them via AJAX (/$stapler/bound/.../render). I do not know what conditions must be met in order for this to happen (>160 plugins?). 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.201579.156710687.1373.1568918820278%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI here is the list of our plugins bouncycastle API Plugin (bouncycastle-api): 2.17 Pipeline: Input Step (pipeline-input-step): 2.11 Folders Plugin (cloudbees-folder): 6.9 Branch API Plugin (branch-api): 2.5.4 Structs Plugin (structs): 1.20 Docker Commons Plugin (docker-commons): 1.15 JUnit Plugin (junit): 1.28 OWASP Markup Formatter Plugin (antisamy-markup-formatter): 1.6 PAM Authentication plugin (pam-auth): 1.5.1 WMI Windows Agents Plugin (windows-slaves): 1.4 Pipeline: Build Step (pipeline-build-step): 2.9 Display URL API (display-url-api): 2.3.2 Docker Pipeline (docker-workflow): 1.19 Mailer Plugin (mailer): 1.27 LDAP Plugin (ldap): 1.20 Token Macro Plugin (token-macro): 2.8 External Monitor Job Type Plugin (external-monitor-job): 1.7 Icon Shim Plugin (icon-shim): 2.0.3 Matrix Authorization Strategy Plugin (matrix-auth): 2.4.2 Pipeline: Model API (pipeline-model-api): 1.3.9 Script Security Plugin (script-security): 1.62 Matrix Project Plugin (matrix-project): 1.14 Build Timeout (build-timeout): 1.19 Credentials Plugin (credentials): 2.3.0 SSH Credentials Plugin (ssh-credentials): 1.17.2 Pipeline: Step API (workflow-step-api): 2.20 Plain Credentials Plugin (plain-credentials): 1.5 Git client plugin (git-client): 2.8.4 Credentials Binding Plugin (credentials-binding): 1.20 Timestamper (timestamper): 1.10 Jackson 2 API Plugin (jackson2-api): 2.9.9.1 SCM API Plugin (scm-api): 2.6.3 Pipeline: API (workflow-api): 2.37 Pipeline: Supporting APIs (workflow-support): 3.3 GitHub API Plugin (github-api): 1.95 Durable Task Plugin (durable-task): 1.30 Pipeline: Nodes and Processes (workflow-durable-task-step): 2.34 GIT server Plugin (git-server): 1.8 Resource Disposer Plugin (resource-disposer): 0.13 Workspace Cleanup Plugin (ws-cleanup): 0.37 Ant Plugin (ant): 1.10 Git plugin (git): 3.12.1 Gradle Plugin (gradle): 1.34 Pipeline: Groovy (workflow-cps): 2.74 Pipeline: Milestone Step (pipeline-milestone-step): 1.3.1 Pipeline: Shared Groovy Libraries (workflow-cps-global-lib): 2.15 _javascript_ GUI Lib: jQuery bundles (jQuery and jQuery UI) plugin (jquery-detached): 1.2.1 _javascript_ GUI Lib: ACE Editor bundle plugin (ace-editor): 1.1 Pipeline: SCM Step (workflow-scm-step): 2.9 Pipeline: Stage Step (pipeline-stage-step): 2.3 GitHub plugin (github): 1.29.4 Pipeline: Job (workflow-job): 2.35 Pipeline: Stage View Plugin (pipeline-stage-view): 2.12 Pipeline Graph Analysis Plugin (pipeline-graph-analysis): 1.10 Pipeline: REST API Plugin (pipeline-rest-api): 2.12 _javascript_ GUI Lib: Handlebars bundle plugin (handlebars): 1.1.1 _javascript_ GUI Lib: Moment.js bundle plugin (momentjs): 1.1.1 NodeJS Plugin (nodejs): 1.3.3 Pipeline: Declarative Extension Points API (pipeline-model-extensions): 1.3.9 Variant Plugin (variant): 1.3 Pipeline: Multibranch (workflow-multibranch): 2.21 Authentication Tokens API Plugin (authentication-tokens): 1.3 Pipeline: Stage Tags Metadata (pipeline-stage-tags-metadata): 1.3.9 Pipeline: Declarative Agent API (pipeline-model-declarative-agent): 1.1.1 Pipeline: Basic Steps (workflow-basic-steps): 2.18 Safe Restart Plugin (saferestart): 0.3 Pipeline: Declarative (pipeline-model-definition): 1.3.9 Metrics Plugin (metrics): 4.0.2.6 Pipeline (workflow-aggregator): 2.6 GitHub Branch Source Plugin (github-branch-source): 2.5.7 Web for Blue Ocean (blueocean-web): 1.19.0 Pub-Sub "lig
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI the issue is covering any GUI configuration related to pipeline, for example today there was an error on the Global Pipeline Libraries, after I enter the scm configuration, it disappears! There is a big NPE when I saved the configuration and this is how the conf look right now, the libraries are connected but the scm part is empty! Sep 18, 2019 10:58:19 AM hudson.ExpressionFactory2$JexlExpression evaluate WARNING: Caught exception evaluating: h.filterDescriptors(it,attrs.descriptors) in /configure. Reason: java.lang.NullPointerException: Descriptor list is null for context 'class hudson.model.Hudson' in thread 'Handling GET /configure from 10.129.16.109 : qtp1717159510-15 Jenkins/configure.jelly GlobalLibraries/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly' java.lang.NullPointerException: Descriptor list is null for context 'class hudson.model.Hudson' in thread 'Handling GET /configure from 10.129.16.109 : qtp1717159510-15 Jenkins/configure.jelly GlobalLibraries/config.jelly LibraryConfiguration/config.jelly SCMRetriever/DescriptorImpl/config.jelly MultiSCM/DescriptorImpl/config.jelly' at hudson.model.DescriptorVisibilityFilter.apply(DescriptorVisibilityFilter.java:73) at hudson.Functions.filterDescriptors(Functions.java:1876) at sun.reflect.GeneratedMethodAccessor884.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:258) at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:104) at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:83) at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:57) at org.apache.commons.jexl.parser.ASTReferenceExpression.value(ASTReferenceExpression.java:51) at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:80) at hudson.ExpressionFactory2$JexlExpression.evaluate(ExpressionFactory2.java:74) at org.apache.commons.jelly.tags.core.CoreTagLibrary$3.run(CoreTagLibrary.java:134) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.commons.jelly.tags.core.CoreTagLibrary$2.run(CoreTagLibrary.java:105) at org.kohsuke.stapler.jelly.CallTagLibScript.run(CallTagLibScript.java:120) at org.kohsuke.stapler.jelly.CallTagLibScript$1.run(CallTagLibScript.java:99) at org.apache.commons.jelly.tags.define.InvokeBodyTag.doTag(InvokeBodyTag.java:91) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:269) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTagLibrary.java:99) at org.kohsuke.stapler.jelly.ReallyStaticTagLibrary$1.run(ReallyStaticTag
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Mohamed ELHOSSARY Attachment: image-2019-09-18-11-11-40-308.png 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.201579.156710687.514.1568819520439%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title
Daniel Beck commented on JENKINS-59145
Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
No useful output in that part of the log. As a next step, reproduce the reported problem and look for errors in your browser's web developer console, or related messages in the Jenkins log. Also, make sure you have configured a Jenkins URL ("Jenkins Location") in the global configuration, and that you access Jenkins using that URL. Go to /manage and check whether there are admin monitors showing. The one about having no Jenkins URL configured, or the one about a broken reverse proxy would be interesting.
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.201579.156710687.4820.1568706421947%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Daniel Beck commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Please also provide a list of installed and enabled plugins and their versions. 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.201579.156710687.4822.1568706422015%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Mohamed ELHOSSARY Attachment: Jenkins_Restart.txt 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.201579.156710687.4691.1568667660898%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY edited a comment on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI here is the log for the jenkins restart, there an issue to list the plugins [^Jenkins_Restart] 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.201579.156710687.4701.1568667661809%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Mohamed ELHOSSARY Attachment: Jenkins_Restart 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.201579.156710687.4702.1568667661839%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Jenkins_Restart.txt 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.201579.156710687.4692.1568667661047%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY edited a comment on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI here is the log for the jenkins restart, there an issue to list the plugins[^Jenkins_Restart] 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.201579.156710687.4686.1568667600405%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI here is the log for the jenkins restart, there an issue to list the plugins Jenkins_Restart 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.201579.156710687.4677.1568667540570%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Mohamed ELHOSSARY Attachment: Jenkins_Restart 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.201579.156710687.4676.1568667540558%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Daniel Beck commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Please provide a complete Jenkins log from (and including) startup sequence to when you hit this issue. 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.201579.156710687.3275.1568394480469%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI We don't have this prometheus plugin and we are still stuck with dangerous issues, what's annoying is there is nothing in the logs that can point us to what might be the problem! 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.201579.156710687.205.1568042520400%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY edited a comment on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI We don't have this prometheus plugin and we are still stuck with this dangerous issues issue , what's annoying is there is nothing in the logs that can point us to what might be the problem! 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.201579.156710687.209.1568042520462%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Michael F. edited a comment on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI We did a downgrade of the plugin "Prometheus metrics" from 2.0.6 to 2.0 .0 and then restarted Jenkins.Luckily, it works again after the restart! The UI shows again the pipeline scripts/configurations!We're not 100% sure if the downgrade or the Jenkins restart was the solution, but we're happy for the hint, 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.201579.156710687.8936.1568026260240%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Michael F. commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI We did a downgrade of the plugin "Prometheus metrics" from 2.0.6 to 2.0 and then restarted Jenkins. Luckily, it works again after the restart! The UI shows again the pipeline scripts/configurations! We're not 100% sure if the downgrade or the Jenkins restart was the solution, but we're happy for the hint, 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.201579.156710687.8930.1568026200363%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title
Michael F. edited a comment on JENKINS-59145
Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
We did exactly the same: just upgrade to latest LTS and all plugins to latest versions and have the exact same problem!All jobs still have their inline- or scm-pipeline configuration in the background (visible via \{.../config.xml}}) but if they are " saved " in the UI (e.g. changing parameters or any job configuration at all) then their the pipeline configuration will be lost! This is a major risk and problem for us ! We have a lot of jobs with pipelines .Do you have any timeline when this bug might get fixed? Or any workaround?
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.201579.156710687.8900.1568020800178%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Michael F. commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI We did exactly the same: just upgrade to latest LTS and all plugins to latest versions and have the exact same problem! All jobs still have their inline- or scm-pipeline configuration but if they are "saved" then their configuration will be lost! This is a major risk and problem for us. Do you have any timeline when this bug might get fixed? Or any workaround? 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.201579.156710687.8896.1568020740267%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI No we don't have this plugin, this is issue is becoming way too critical for us, we have now way to launch the job from the GUI, I have raised the issue to blocker. 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.201579.156710687.8318.1567786260148%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Mohamed ELHOSSARY Priority: Critical Blocker 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.201579.156710687.8315.1567786140294%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Paulius Bulotas commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Do you have Prometheus plugin? Downgrading from 2.0.6 to 2.0.0 solved GUI issue for us. And random NPEs when saving user etc. As per JENKINS-58940 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.201579.156710687.6775.1567622400145%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Paulius Bulotas commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Small update... While it's little inconvenience with configuring pipeline text or pipeline scm source, I just noticed that configuring Folder (which has shared pipeline, vault info configured), shared pipeline and vault info is also not displayed and if you save folder config, those things are lost from config. I was a bit surprised that after modifying folder description, shared pipeline and vault info disappeared (config-history plugin is great) and all jobs in folder started failing. 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.201579.156710687.5899.1567523220752%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title
Paulius Bulotas edited a comment on JENKINS-59145
Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
We also have this on 2.176.3 with bunch of updated plugins.This is stacktrace seen in log:{code:java}WARNING: Error while serving https://jenkins/job/_playground/job/.../job/test/descriptorByName/org.jenkinsci.plugins.blockbuildfinalproject.BlockBuildJobProperty/checkUseBlockBuildDownstreamProjectjava.lang.reflect.InvocationTargetExceptionat org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:400)at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:408)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:535)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280)at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58)at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878)at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676)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:873)at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154)at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246)at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151)at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134)...Caused by: java.lang.NullPointerExceptionat org.jenkinsci.plugins.blockbuildfinalproject.BlockBuildJobProperty$DescriptorImpl.doCheckUseBlockBuildDownstreamProject(BlockBuildJobProperty.java:390)at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627)at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396){code}Maybe relevant plugin updates (where - is old version, + is new version, from diff -u :) : aws-codepipeline:0.38-blueocean:1.16.0+blueocean:1.18.1 blueocean-autofavorite:1.2.4-blueocean-bitbucket-pipeline:1.16.0-blueocean-commons:1.16.0-blueocean-config:1.16.0-blueocean-core-js:1.16.0-bl
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Paulius Bulotas updated an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Change By: Paulius Bulotas Labels: NPE 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.201579.156710687.4148.1567413000467%40Atlassian.JIRA.
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Paulius Bulotas commented on JENKINS-59145 Re: After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI We also have this on 2.176.3 with bunch of updated plugins. This is stacktrace seen in log: WARNING: Error while serving https://jenkins/job/_playground/job/.../job/test/descriptorByName/org.jenkinsci.plugins.blockbuildfinalproject.BlockBuildJobProperty/checkUseBlockBuildDownstreamProject 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.Function.bindAndInvoke(Function.java:212) at org.kohsuke.stapler.Function.bindAndInvokeAndServeResponse(Function.java:145) at org.kohsuke.stapler.MetaClass$11.doDispatch(MetaClass.java:535) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.MetaClass$4.doDispatch(MetaClass.java:280) at org.kohsuke.stapler.NameBasedDispatcher.dispatch(NameBasedDispatcher.java:58) at org.kohsuke.stapler.Stapler.tryInvoke(Stapler.java:747) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:878) at org.kohsuke.stapler.Stapler.invoke(Stapler.java:676) 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:873) at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1623) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:154) at org.jenkinsci.plugins.ssegateway.Endpoint$SSEListenChannelFilter.doFilter(Endpoint.java:246) at hudson.util.PluginServletFilter$1.doFilter(PluginServletFilter.java:151) at io.jenkins.blueocean.ResourceCacheControl.doFilter(ResourceCacheControl.java:134) ... Caused by: java.lang.NullPointerException at org.jenkinsci.plugins.blockbuildfinalproject.BlockBuildJobProperty$DescriptorImpl.doCheckUseBlockBuildDownstreamProject(BlockBuildJobProperty.java:390) at java.lang.invoke.MethodHandle.invokeWithArguments(MethodHandle.java:627) at org.kohsuke.stapler.Function$MethodFunction.invoke(Function.java:396)
[JIRA] (JENKINS-59145) After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI
Title: Message Title Mohamed ELHOSSARY created an issue Jenkins / JENKINS-59145 After Jenkins upgrade pipeline script from SCM configuration is no longer visible on the GUI Issue Type: Bug Assignee: Unassigned Attachments: image-2019-08-29-15-26-25-996.png Components: core Created: 2019-08-29 19:27 Environment: on prem linux server Priority: Critical Reporter: Mohamed ELHOSSARY After upgrade of the jenkins server to Jenkins ver. 2.176.2 and all plugins to the latest version, all of our pipeline jobs are showing this (see screenshot) and we try to modify it to Pipeline script from SCM and save the configuration, and reopen the configuration of the job it reverts back the screenshot! what is weird that in the jenkins home directory, the configuration in the job is there in the xml files, it is just not parsed on the GUI! Even when we create new jobs and save it as pipeline script from SCM, the display always revert to Pipeline script! And there is nothing in the logs that can point us to what might be the issue
