Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-33032

Enabling Resolve artifacts from Artifactory results in stack trace

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Blocker
    • Resolution: Unresolved
    • Component/s: artifactory-plugin
    • Labels:
      None
    • Environment:
      Linux SLES11
      JDK 1.7
    • Similar Issues:

      Description

      When I enable the resolve artifacts from artifactory I get the following stack trace.

      [main] ERROR org.jfrog.build.extractor.maven.BuildInfoClientBuilder - Could not build the build-info object.
      org.apache.commons.logging.LogConfigurationException: User-specified log class 'org.apache.commons.logging.impl.LogKitLogger' cannot be found or is not useable.
      at org.apache.commons.logging.impl.LogFactoryImpl.discoverLogImplementation(LogFactoryImpl.java:874)
      at org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:604)
      at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:336)
      at org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:310)
      at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:685)
      at org.apache.http.impl.client.AbstractHttpClient.<init>(AbstractHttpClient.java:187)
      at org.apache.http.impl.client.DefaultHttpClient.<init>(DefaultHttpClient.java:141)
      at org.jfrog.build.client.PreemptiveHttpClient.createHttpClient(PreemptiveHttpClient.java:99)
      at org.jfrog.build.client.PreemptiveHttpClient.<init>(PreemptiveHttpClient.java:72)
      at org.jfrog.build.client.ArtifactoryHttpClient.getHttpClient(ArtifactoryHttpClient.java:121)
      at org.jfrog.build.client.ArtifactoryHttpClient.getVersion(ArtifactoryHttpClient.java:134)
      at org.jfrog.build.extractor.clientConfiguration.client.ArtifactoryBuildInfoClient.verifyCompatibleArtifactoryVersion(ArtifactoryBuildInfoClient.java:345)
      at org.jfrog.build.extractor.clientConfiguration.client.ArtifactoryBuildInfoClient.buildInfoToJsonString(ArtifactoryBuildInfoClient.java:562)
      at org.jfrog.build.extractor.clientConfiguration.client.ArtifactoryBuildInfoClient.sendBuildInfo(ArtifactoryBuildInfoClient.java:241)
      at org.jfrog.build.extractor.maven.BuildDeploymentHelper.deploy(BuildDeploymentHelper.java:111)
      at org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded(BuildInfoRecorder.java:170)
      at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:64)
      at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
      at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:129)
      at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
      at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
      at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
      at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
      at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:606)
      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
      at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
      at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
      [main] ERROR org.jfrog.build.extractor.maven.BuildInfoRecorder - org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded() listener has failed:
      java.lang.RuntimeException: Error occurred while publishing Build Info to Artifactory.
      at org.jfrog.build.extractor.maven.BuildDeploymentHelper.deploy(BuildDeploymentHelper.java:114)
      at org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded(BuildInfoRecorder.java:170)
      at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:64)
      at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
      at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:129)
      at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
      at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
      at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
      at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
      at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:606)
      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
      at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
      at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
      Caused by: java.io.IOException: Could not publish build-info: User-specified log class 'org.apache.commons.logging.impl.LogKitLogger' cannot be found or is not useable.
      at org.jfrog.build.extractor.clientConfiguration.client.ArtifactoryBuildInfoClient.sendBuildInfo(ArtifactoryBuildInfoClient.java:244)
      at org.jfrog.build.extractor.maven.BuildDeploymentHelper.deploy(BuildDeploymentHelper.java:111)
      ... 17 more
      [main] ERROR org.apache.maven.cli.MavenCli - Internal error: java.lang.RuntimeException: org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded() listener has failed: Error occurred while publishing Build Info to Artifactory. Could not publish build-info: User-specified log class 'org.apache.commons.logging.impl.LogKitLogger' cannot be found or is not useable. -> [Help 1]
      org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded() listener has failed:
      at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:166)
      at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
      at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
      at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
      at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
      at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
      at java.lang.reflect.Method.invoke(Method.java:606)
      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
      at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
      at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
      Caused by: java.lang.RuntimeException: org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded() listener has failed:
      at org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded(BuildInfoRecorder.java:179)
      at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:64)
      at org.apache.maven.lifecycle.internal.DefaultExecutionEventCatapult.fire(DefaultExecutionEventCatapult.java:42)
      at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:129)
      at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
      at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
      ... 11 more
      Caused by: java.lang.RuntimeException: Error occurred while publishing Build Info to Artifactory.
      at org.jfrog.build.extractor.maven.BuildDeploymentHelper.deploy(BuildDeploymentHelper.java:114)
      at org.jfrog.build.extractor.maven.BuildInfoRecorder.sessionEnded(BuildInfoRecorder.java:170)
      ... 16 more
      Caused by: java.io.IOException: Could not publish build-info: User-specified log class 'org.apache.commons.logging.impl.LogKitLogger' cannot be found or is not useable.
      at org.jfrog.build.extractor.clientConfiguration.client.ArtifactoryBuildInfoClient.sendBuildInfo(ArtifactoryBuildInfoClient.java:244)
      at org.jfrog.build.extractor.maven.BuildDeploymentHelper.deploy(BuildDeploymentHelper.java:111)
      ... 17 more

      Jenkins version is: 1.625.2
      Artifactory Plugin Version is: 2.4.6
      Artifactory Server version is: 4.2.2 rev 40049 - Professional

        Attachments

          Activity

          Hide
          praqmatim Timothy Harris added a comment - - edited

          Eyal Ben Moshe,Eyal Ben Moshe: Are you aware of this issue? It is very much related to JENKINS-24111. Seems you guys at jFrog have your own Jira instance. Should this issue be replicated to it by me or is that something you guys do yourselves?

          Show
          praqmatim Timothy Harris added a comment - - edited Eyal Ben Moshe , Eyal Ben Moshe : Are you aware of this issue? It is very much related to JENKINS-24111 . Seems you guys at jFrog have your own Jira instance. Should this issue be replicated to it by me or is that something you guys do yourselves?
          Hide
          praqmatim Timothy Harris added a comment -

          The problem seems to appear on Maven Projects with multimodules. We have worked around this by making sure our slaves have a maven settings file which will resolve to our Artifactory instance.

          But every time someone tries to use the plugin we end up getting a new issue about it. This is quite painful.

          Show
          praqmatim Timothy Harris added a comment - The problem seems to appear on Maven Projects with multimodules. We have worked around this by making sure our slaves have a maven settings file which will resolve to our Artifactory instance. But every time someone tries to use the plugin we end up getting a new issue about it. This is quite painful.

            People

            • Assignee:
              eyalbe Eyal Ben Moshe
              Reporter:
              praqmatim Timothy Harris
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated: