Using globs with depths causes errors in archiveartifact

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Hello,

       

      Upgrading from 902 to 926 caused a weird issue on my end.

       

      On a pipeline I'm using archiveartifacts like this:

       archiveArtifacts artifacts: 'my-client-build-eu/**/*.*, my-client-build-us/**/*.*', onlyIfSuccessful: true

      After upgrading to 926, it started to return the following error out of the blue:

      Unable to load credentials from any of the providers in the chain AwsCredentialsProviderChain(credentialsProviders=[SystemPropertyCredentialsProvider(), EnvironmentVariableCredentialsProvider(), WebIdentityTokenCredentialsProvider(), ProfileCredentialsProvider(profileName=default, profileFile=ProfileFile(sections=[])), ContainerCredentialsProvider(), InstanceProfileCredentialsProvider()]) : [SystemPropertyCredentialsProvider(): Unable to load credentials from system settings. Access key must be specified either via environment variable (AWS_ACCESS_KEY_ID) or system property (aws.accessKeyId)., EnvironmentVariableCredentialsProvider(): Unable to load credentials from system settings. Access key must be specified either via environment variable (AWS_ACCESS_KEY_ID) or system property (aws.accessKeyId)., WebIdentityTokenCredentialsProvider(): Either the environment variable AWS_WEB_IDENTITY_TOKEN_FILE or the javaproperty aws.webIdentityTokenFile must be set., ProfileCredentialsProvider(profileName=default, profileFile=ProfileFile(sections=[])): Profile file contained no credentials for profile 'default': ProfileFile(sections=[]), ContainerCredentialsProvider(): Cannot fetch credentials from container - neither AWS_CONTAINER_CREDENTIALS_FULL_URI or AWS_CONTAINER_CREDENTIALS_RELATIVE_URI environment variables are set., InstanceProfileCredentialsProvider(): Failed to load credentials from IMDS.]

      For the context, I'm using instance profiles and that profile has s3 access already and just works. I also noticed that, if I specify a top level like (

      /*

      ) version 926 still works. But if I provide a pattern like 

      directory/**/*.*

      , it fails the error above.

      Downgrading to 906 back fixes the issue.

      Jenkins version: 2.504.1 (LTS, docker image)
       

            Assignee:
            Unassigned
            Reporter:
            Samed
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Archived: