[JIRA] (JENKINS-60571) Prometheus Metrics Plugin installed failed

2019-12-22 Thread zhuxiaoyang1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zhu xiaoyang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60571  
 
 
  Prometheus Metrics Plugin installed failed   
 

  
 
 
 
 

 
Change By: 
 zhu xiaoyang  
 

  
 
 
 
 

 
 plugging installed failed.create jenkins as a deployment in namespace kubesphere.install  plugin   Prometheus Metrics Plugin with following error log ```WARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.prometheus.service.PrometheusAsyncWorker, annotation=[none]]; skipping this componentWARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.prometheus.service.PrometheusAsyncWorker, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Error injecting constructor, java.lang.IllegalArgumentException: Invalid metric name: kubesphere-devops-system_jenkins_builds_duration_milliseconds_summary  at org.jenkinsci.plugins.prometheus.service.DefaultPrometheusMetrics.(DefaultPrometheusMetrics.java:24)  while locating org.jenkinsci.plugins.prometheus.service.DefaultPrometheusMetrics  at org.jenkinsci.plugins.prometheus.context.Context.configure(Context.java:13)  while locating org.jenkinsci.plugins.prometheus.service.PrometheusMetrics    for parameter 0 at org.jenkinsci.plugins.prometheus.service.PrometheusAsyncWorker.setPrometheusMetrics(PrometheusAsyncWorker.java:26) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:439) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:401) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:392) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:339) at hudson.ExtensionList.load(ExtensionList.java:381) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.iterator(ExtensionList.java:172) at hudson.ExtensionList.get(ExtensionList.java:149) at jenkins.metrics.api.Metrics$HealthCheckMetricsProvider.getMetricSet(Metrics.java:359) at jenkins.metrics.api.MetricProviderListener.onChange(MetricProviderListener.java:91) at jenkins.metrics.api.MetricProviderListener.attach(MetricProviderListener.java:77) at jenkins.metrics.api.Metrics.afterExtensionsAugmented(Metrics.java:313) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFind

[JIRA] (JENKINS-60571) Prometheus Metrics Plugin installed failed

2019-12-22 Thread zhuxiaoyang1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zhu xiaoyang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60571  
 
 
  Prometheus Metrics Plugin installed failed   
 

  
 
 
 
 

 
Change By: 
 zhu xiaoyang  
 

  
 
 
 
 

 
 plugging installed failed .  create jenkins as a deployment in namespace kubesphere.install plugin  ```WARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.prometheus.service.PrometheusAsyncWorker, annotation=[none]]; skipping this componentWARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.prometheus.service.PrometheusAsyncWorker, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Unable to provision, see the following errors:1) Error injecting constructor, java.lang.IllegalArgumentException: Invalid metric name: kubesphere-devops-system_jenkins_builds_duration_milliseconds_summary  at org.jenkinsci.plugins.prometheus.service.DefaultPrometheusMetrics.(DefaultPrometheusMetrics.java:24)  while locating org.jenkinsci.plugins.prometheus.service.DefaultPrometheusMetrics  at org.jenkinsci.plugins.prometheus.context.Context.configure(Context.java:13)  while locating org.jenkinsci.plugins.prometheus.service.PrometheusMetrics    for parameter 0 at org.jenkinsci.plugins.prometheus.service.PrometheusAsyncWorker.setPrometheusMetrics(PrometheusAsyncWorker.java:26)1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:439) at com.google.inject.internal.InternalFactoryToProviderAdapter.get(InternalFactoryToProviderAdapter.java:41) at com.google.inject.internal.InjectorImpl$2$1.call(InjectorImpl.java:1016) at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1092) at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012) at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:401) at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:392) at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:339) at hudson.ExtensionList.load(ExtensionList.java:381) at hudson.ExtensionList.ensureLoaded(ExtensionList.java:317) at hudson.ExtensionList.iterator(ExtensionList.java:172) at hudson.ExtensionList.get(ExtensionList.java:149) at jenkins.metrics.api.Metrics$HealthCheckMetricsProvider.getMetricSet(Metrics.java:359) at jenkins.metrics.api.MetricProviderListener.onChange(MetricProviderListener.java:91) at jenkins.metrics.api.MetricProviderListener.attach(MetricProviderListener.java:77) at jenkins.metrics.api.Metrics.afterExtensionsAugmented(Metrics.java:313) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at hudson.init.TaskMethodFinder.invoke(TaskMethodFinder.java:104) at hudson.init.TaskMethodFinder$TaskImp

[JIRA] (JENKINS-60571) Prometheus Metrics Plugin installed failed

2019-12-22 Thread zhuxiaoyang1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zhu xiaoyang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60571  
 
 
  Prometheus Metrics Plugin installed failed   
 

  
 
 
 
 

 
Change By: 
 zhu xiaoyang  
 
 
Summary: 
 plugging Prometheus Metrics Plugin  installed failed  
 

  
 
 
 
 

 
 
 

 
 
 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.203684.1577078342000.14897.1577078460181%40Atlassian.JIRA.


[JIRA] (JENKINS-60571) plugging installed failed

2019-12-22 Thread zhuxiaoyang1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zhu xiaoyang created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-60571  
 
 
  plugging installed failed   
 

  
 
 
 
 

 
Issue Type: 
  Bug  
 
 
Assignee: 
 Marky Jackson  
 
 
Components: 
 prometheus-plugin  
 
 
Created: 
 2019-12-23 05:19  
 
 
Environment: 
 Jenkins 2.176.2  Prometheus metrics plugin 2.0.6  
 
 
Labels: 
 plugin  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 zhu xiaoyang  
 

  
 
 
 
 

 
 plugging installed failed ``` WARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.prometheus.service.PrometheusAsyncWorker, annotation=[none]]; skipping this componentWARNING: Failed to instantiate Key[type=org.jenkinsci.plugins.prometheus.service.PrometheusAsyncWorker, annotation=[none]]; skipping this componentcom.google.inject.ProvisionException: Unable to provision, see the following errors: 1) Error injecting constructor, java.lang.IllegalArgumentException: Invalid metric name: kubesphere-devops-system_jenkins_builds_duration_milliseconds_summary  at org.jenkinsci.plugins.prometheus.service.DefaultPrometheusMetrics.(DefaultPrometheusMetrics.java:24)  while locating org.jenkinsci.plugins.prometheus.service.DefaultPrometheusMetrics  at org.jenkinsci.plugins.prometheus.context.Context.configure(Context.java:13)  while locating org.jenkinsci.plugins.prometheus.service.PrometheusMetrics    for parameter 0 at org.jenkinsci.plugins.prometheus.service.PrometheusAsyncWorker.setPrometheusMetrics(PrometheusAsyncWorker.java:26) 1 error at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:52) at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145) at hudson.ExtensionFinder$GuiceFinde

[JIRA] (JENKINS-58406) A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.

2019-07-09 Thread zhuxiaoyang1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zhu xiaoyang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58406  
 
 
  A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.   
 

  
 
 
 
 

 
Change By: 
 zhu xiaoyang  
 

  
 
 
 
 

 
 A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check process, but it will be returned an error: "parameters is required".Now the request body like :{"id":"2", "parameters":[]}  it works well, but the field "parameters" is not used.I guess  If we  remove   "parameters" like \{"id":"2"} , The function can also work well.Perhaps support both different struct  is  more restful  a better choice .  
 

  
 
 
 
 

 
 
 

 
 
 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.200531.1562686643000.5651.1562687820061%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58406) A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.

2019-07-09 Thread zhuxiaoyang1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zhu xiaoyang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58406  
 
 
  A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.   
 

  
 
 
 
 

 
Change By: 
 zhu xiaoyang  
 

  
 
 
 
 

 
 A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check  proceed  process , but it will be returned an error: "parameters is required"Now the request body like :{"id":"2", "parameters":[]}it works well, but the field "parameters" is not used.I guess remove "parameters" like \{"id":"2"} is more restful.  
 

  
 
 
 
 

 
 
 

 
 
 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.200531.1562686643000.5649.1562686980098%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58406) A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.

2019-07-09 Thread zhuxiaoyang1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zhu xiaoyang updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58406  
 
 
  A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.   
 

  
 
 
 
 

 
Change By: 
 zhu xiaoyang  
 

  
 
 
 
 

 
 A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check process, but it will be returned an error: "parameters is required" . Now the request body like :{"id":"2", "parameters":[]}it works well, but the field "parameters" is not used.I guess remove "parameters" like \{"id":"2"} is more restful.  
 

  
 
 
 
 

 
 
 

 
 
 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.200531.1562686643000.5650.1562686980140%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58406) A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.

2019-07-09 Thread zhuxiaoyang1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zhu xiaoyang started work on  JENKINS-58406  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
Change By: 
 zhu xiaoyang  
 
 
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.200531.1562686643000.5648.1562686800088%40Atlassian.JIRA.
For more options, visit https://groups.google.com/d/optout.


[JIRA] (JENKINS-58406) A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.

2019-07-09 Thread zhuxiaoyang1...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 zhu xiaoyang created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-58406  
 
 
  A pipeline is pending, I just want to continue not required any parameters, so check proceed without field "parameters", is will be return error: parameters is required.   
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 zhu xiaoyang  
 
 
Components: 
 blueocean-plugin  
 
 
Created: 
 2019-07-09 15:37  
 
 
Labels: 
 blueocean improvement  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 zhu xiaoyang  
 

  
 
 
 
 

 
 A pipeline is pending, I just want to continue without any parameters, so I use pipeline API to check proceed, but it will be returned an error: "parameters is required" Now the request body like : {"id":"2", "parameters":[]} it works well, but the field "parameters" is not used. I guess remove "parameters" like {"id":"2"} is more restful.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment