• 1.18

      most builds get this error now:

      java.lang.NoSuchMethodError: 'java.lang.ClassLoader com.google.inject.internal.BytecodeGen.getClassLoader(java.lang.Class)'
      	at com.google.inject.assistedinject.FactoryProvider2.<init>(FactoryProvider2.java:322)
      	at com.google.inject.assistedinject.FactoryModuleBuilder$1.configure(FactoryModuleBuilder.java:334)
      	at com.google.inject.AbstractModule.configure(AbstractModule.java:64)
      	at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
      	at com.google.inject.AbstractModule.install(AbstractModule.java:106)
      	at org.jclouds.rest.config.RestModule.configure(RestModule.java:59)
      	at org.jclouds.rest.config.HttpApiModule.configure(HttpApiModule.java:53)
      	at org.jclouds.s3.config.S3HttpApiModule.configure(S3HttpApiModule.java:169)
      	at org.jclouds.aws.s3.config.AWSS3HttpApiModule.configure(AWSS3HttpApiModule.java:56)
      	at com.google.inject.AbstractModule.configure(AbstractModule.java:64)
      	at com.google.inject.spi.Elements$RecordingBinder.install(Elements.java:409)
      	at com.google.inject.spi.Elements.getElements(Elements.java:108)
      	at com.google.inject.internal.InjectorShell$Builder.build(InjectorShell.java:160)
      	at com.google.inject.internal.InternalInjectorCreator.build(InternalInjectorCreator.java:107)
      	at com.google.inject.Guice.createInjector(Guice.java:87)
      	at org.jclouds.ContextBuilder.buildInjector(ContextBuilder.java:405)
      	at org.jclouds.ContextBuilder.buildInjector(ContextBuilder.java:328)
      	at org.jclouds.ContextBuilder.buildView(ContextBuilder.java:615)
      	at org.jclouds.ContextBuilder.buildView(ContextBuilder.java:595)
      	at io.jenkins.plugins.artifact_manager_jclouds.s3.S3BlobStore.getContext(S3BlobStore.java:136)
      	at io.jenkins.plugins.artifact_manager_jclouds.JCloudsArtifactManager.getContext(JCloudsArtifactManager.java:377)
      	at io.jenkins.plugins.artifact_manager_jclouds.JCloudsArtifactManager.stash(JCloudsArtifactManager.java:216)
      	at org.jenkinsci.plugins.workflow.flow.StashManager.stash(StashManager.java:117)
      	at org.jenkinsci.plugins.workflow.support.steps.stash.StashStep$Execution.run(StashStep.java:116)
      	at org.jenkinsci.plugins.workflow.support.steps.stash.StashStep$Execution.run(StashStep.java:104)
      	at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
      	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
      	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
      	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
      	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
      	at java.base/java.lang.Thread.run(Thread.java:829) 

      downgrading to 2.230 fixes this

          [JENKINS-67174] Guice error from artifact-manager-s3 on 2.321

          Basil Crow added a comment -

          jglick Perhaps we should release your latest PRs to see if that fixes this problem?

          Basil Crow added a comment - jglick Perhaps we should release your latest PRs to see if that fixes this problem?

          Tim Jacomb added a comment - Please provide plugins and their versions. https://www.jenkins.io/participate/report-issue/#Howtoreportanissue-WhatinformationtoprovideforEnvironmentandDescription This may be fixed by https://github.com/jenkinsci/artifact-manager-s3-plugin/releases/tag/artifact-manager-s3-1.16.1

          Jesse Glick added a comment -

          1.16.1 solves other issues, only in tests I think.

          b_dean can you please check whether https://repo.jenkins-ci.org/incrementals/io/jenkins/plugins/artifact-manager-s3/1.18-rc598.5dbda854ed51/artifact-manager-s3-1.18-rc598.5dbda854ed51.hpi solves your issue? If so, I will release it.

          Jesse Glick added a comment - 1.16.1 solves other issues, only in tests I think. b_dean can you please check whether https://repo.jenkins-ci.org/incrementals/io/jenkins/plugins/artifact-manager-s3/1.18-rc598.5dbda854ed51/artifact-manager-s3-1.18-rc598.5dbda854ed51.hpi solves your issue? If so, I will release it.

          Jesse Glick added a comment -

          Reproduced via

          git checkout $(git log --reverse --ancestry-path --pretty=%H artifact-manager-s3-1.17..master | head -1)
          mvn clean test -Djenkins.version=2.321 -Dtest=MinioIntegrationTest\#artifactArchiveAndDelete
          

          I think it best to just release what I have in trunk which should be compatible with 2.321.

          Jesse Glick added a comment - Reproduced via git checkout $(git log --reverse --ancestry-path --pretty=%H artifact-manager-s3-1.17..master | head -1) mvn clean test -Djenkins.version=2.321 -Dtest=MinioIntegrationTest\ #artifactArchiveAndDelete I think it best to just release what I have in trunk which should be compatible with 2.321.

          Ben Dean added a comment -

          sorry jglick, been busy. We do use the s3 artifact manager so that's likely it. haven't had a chance to try it yet though

          Ben Dean added a comment - sorry jglick , been busy. We do use the s3 artifact manager so that's likely it. haven't had a chance to try it yet though

            jglick Jesse Glick
            b_dean Ben Dean
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: