Paulius Bulotas added a comment - 2019-09-02 08:28 - edited 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) 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 -blueocean-dashboard:1.16.0 -blueocean-display-url:2.2.0 -blueocean-events:1.16.0 -blueocean-executor-info:1.14.0 -blueocean-github-pipeline:1.16.0 -blueocean-git-pipeline:1.16.0 -blueocean-i18n:1.16.0 -blueocean-jira:1.16.0 -blueocean-jwt:1.16.0 -blueocean-personalization:1.16.0 -blueocean-pipeline-api-impl:1.16.0 -blueocean-pipeline-editor:1.16.0 -blueocean-pipeline-scm-api:1.16.0 -blueocean-rest:1.16.0 -blueocean-rest-impl:1.16.0 -blueocean-web:1.16.0 +blueocean-bitbucket-pipeline:1.18.1 +blueocean-commons:1.18.1 +blueocean-config:1.18.1 +blueocean-core-js:1.18.1 +blueocean-dashboard:1.18.1 +blueocean-display-url:2.3.0 +blueocean-events:1.18.1 +blueocean-executor-info:1.18.1 +blueocean-github-pipeline:1.18.1 +blueocean-git-pipeline:1.18.1 +blueocean-i18n:1.18.1 +blueocean-jira:1.18.1 +blueocean-jwt:1.18.1 +blueocean-personalization:1.18.1 +blueocean-pipeline-api-impl:1.18.1 +blueocean-pipeline-editor:1.18.1 +blueocean-pipeline-scm-api:1.18.1 +blueocean-rest:1.18.1 +blueocean-rest-impl:1.18.1 +blueocean-web:1.18.1 build-pipeline-plugin:1.5.8 hashicorp-vault-pipeline:1.2 -pipeline-aws:1.36 +pipeline-aws:1.38 pipeline-build-step:2.9 pipeline-github-lib:1.0 -pipeline-graph-analysis:1.9 -pipeline-input-step:2.10 +pipeline-graph-analysis:1.10 +pipeline-input-step:2.11 pipeline-milestone-step:1.3.1 -pipeline-model-api:1.3.8 +pipeline-model-api:1.3.9 pipeline-model-declarative-agent:1.1.1 -pipeline-model-definition:1.3.8 -pipeline-model-extensions:1.3.8 -pipeline-rest-api:2.11 +pipeline-model-definition:1.3.9 +pipeline-model-extensions:1.3.9 +pipeline-rest-api:2.12 pipeline-stage-step:2.3 -pipeline-stage-tags-metadata:1.3.8 -pipeline-stage-view:2.11 +pipeline-stage-tags-metadata:1.3.9 +pipeline-stage-view:2.12 pipeline-utility-steps:2.3.0 ... -docker-workflow:1.18 +docker-workflow:1.19 workflow-aggregator:2.6 workflow-api:2.36 -workflow-basic-steps:2.15 +workflow-basic-steps:2.18 workflow-cps:2.73 workflow-cps-global-lib:2.15 -workflow-durable-task-step:2.30 -workflow-job:2.32 +workflow-durable-task-step:2.33 +workflow-job:2.34 workflow-multibranch:2.21 -workflow-scm-step:2.7 +workflow-scm-step:2.9 workflow-step-api:2.20 workflow-support:3.3

Paulius Bulotas added a comment - 2019-09-03 15:06 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.

Paulius Bulotas added a comment - 2019-09-04 18:39 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

Mohamed ELHOSSARY added a comment - 2019-09-06 16:10 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.

Michael F. added a comment - 2019-09-09 09:18 - edited 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 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?

Michael F. added a comment - 2019-09-09 10:49 - edited 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!

Mohamed ELHOSSARY added a comment - 2019-09-09 15:21 - edited We don't have this prometheus plugin and we are still stuck with this dangerous issue, what's annoying is there is nothing in the logs that can point us to what might be the problem!