[JIRA] (JENKINS-47972) hudson.plugins.claim.ClaimConfig: circular dependency

2018-02-27 Thread andreas.sk...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Skoog commented on  JENKINS-47972  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: hudson.plugins.claim.ClaimConfig: circular dependency   
 

  
 
 
 
 

 
 I uninstalled the plugin completely and installed it again, then it worked fine...  
 

  
 
 
 
 

 
 
 

 
 
 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-47972) hudson.plugins.claim.ClaimConfig: circular dependency

2018-02-26 Thread andreas.sk...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Skoog commented on  JENKINS-47972  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: hudson.plugins.claim.ClaimConfig: circular dependency   
 

  
 
 
 
 

 
 Here's the error I got:   

 

Feb 25, 2018 8:27:59 PM hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1 error
WARNING: Failed to instantiate Key[type=hudson.plugins.claim.ClaimConfig, annotation=[none]]; skipping this component
com.google.inject.ProvisionException: Unable to provision, see the following errors:

1) Tried proxying hudson.plugins.claim.ClaimConfig to support a circular dependency, but it is not an interface.

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:424)
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:1103)
at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386)
at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377)
at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:482)
at hudson.ExtensionList.load(ExtensionList.java:366)
at hudson.ExtensionList.ensureLoaded(ExtensionList.java:304)
at hudson.ExtensionList.getComponents(ExtensionList.java:169)
at hudson.DescriptorExtensionList.load(DescriptorExtensionList.java:192)
at hudson.ExtensionList.ensureLoaded(ExtensionList.java:304)
at hudson.ExtensionList.iterator(ExtensionList.java:158)
at hudson.ExtensionList.get(ExtensionList.java:149)
at jenkins.plugins.slack.webhook.WebhookEndpoint.(WebhookEndpoint.java:46)
at jenkins.plugins.slack.webhook.WebhookEndpoint$$FastClassByGuice$$843c6231.newInstance()
at com.google.inject.internal.cglib.reflect.$FastConstructor.newInstance(FastConstructor.java:40)
at com.google.inject.internal.DefaultConstructionProxyFactory$1.newInstance(DefaultConstructionProxyFactory.java:61)
at com.google.inject.internal.ConstructorInjector.provision(ConstructorInjector.java:105)
at com.google.inject.internal.ConstructorInjector.construct(ConstructorInjector.java:85)
at com.google.inject.internal.ConstructorBindingImpl$Factory.get(ConstructorBindingImpl.java:267)
at com.google.inject.internal.ProviderToInternalFactoryAdapter$1.call(ProviderToInternalFactoryAdapter.java:46)
at com.google.inject.internal.InjectorImpl.callInContext(InjectorImpl.java:1103)
at com.google.inject.internal.ProviderToInternalFactoryAdapter.get(ProviderToInternalFactoryAdapter.java:40)
at com.google.inject.internal.SingletonScope$1.get(SingletonScope.java:145)
at hudson.ExtensionFinder$GuiceFinder$FaultTolerantScope$1.get(ExtensionFinder.java:424)
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:1103)
at com.google.inject.internal.InjectorImpl$2.get(InjectorImpl.java:1012)
at hudson.ExtensionFinder$GuiceFinder._find(ExtensionFinder.java:386)
at hudson.ExtensionFinder$GuiceFinder.find(ExtensionFinder.java:377)
at hudson.ClassicPluginStrategy.findComponents(ClassicPluginStrategy.java:482)
at

[JIRA] (JENKINS-47972) hudson.plugins.claim.ClaimConfig: circular dependency

2018-02-25 Thread andreas.sk...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andreas Skoog reopened an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 I got this exact error when upgrading from 2.13 to 2.14  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47972  
 
 
  hudson.plugins.claim.ClaimConfig: circular dependency   
 

  
 
 
 
 

 
Change By: 
 Andreas Skoog  
 
 
Resolution: 
 Fixed  
 
 
Status: 
 Resolved Reopened  
 

  
 
 
 
 

 
 
 

 
 
 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] [gitlab-plugin] (JENKINS-34396) Gitlab plugin does not work with jenkins pipeline plugin

2016-04-22 Thread andreas.sk...@gmail.com (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Andreas Skoog created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Jenkins /  JENKINS-34396 
 
 
 
  Gitlab plugin does not work with jenkins pipeline plugin  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 
 Robin Müller 
 
 
 

Components:
 

 gitlab-plugin 
 
 
 

Created:
 

 2016/Apr/22 12:34 PM 
 
 
 

Priority:
 
  Minor 
 
 
 

Reporter:
 
 Andreas Skoog 
 
 
 
 
 
 
 
 
 
 
It seems that the gitlab plugin does not work very well with the jenkins pipeline plugin in jenkins 2.0. If you create a new pipeline job in jenkins you are not able to trigger it from a gitlab web hook since the project has no SCM connection (the scm connection is defined in the pipeline dsl) 

 
WARNING: Error while serving http:///project/
java.lang.reflect.InvocationTargetException
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:497)
at org.kohsuke.stapler.Function$InstanceFunction.invoke(Function.java:320)
...
Caused by: java.lang.IllegalArgumentException: This project does not use git:
at com.dabsquared.gitlabjenkins.GitLabPushTrigger$DescriptorImpl.getSourceRepoNameDefault(GitLabPushTrigger.java:894)
at com.dabsquared.gitlabjenkins.GitLabPushTrigger.createActions(GitLabPushTrigger.java:289)
at com.dabsquared.gitlabjenkins.GitLabPushTrigger.onPost(GitLabPushTrigger.java:238)
at com.dabsquared.gitlabjenkins.GitLabWebHook.generatePushBuild(GitLabWebHook.java:378)
at