Artifact Manager on S3 - issue with loading links to the S3 artifacts about configuration-as-code-plugin HOT 3 CLOSED

Can you raise this with the artifact manager with S3 plugin please, its unlikely to be an issue with configuration as code

from configuration-as-code-plugin.

@timja
I think I just figured out

Seems that prefix parameter is required even value is empty string. I don't have prefix, all artifacts are in the root of the bucket.

I compared io.jenkins.plugins.artifact_manager_jcloud.s3.S3BlobstorageConfig.xml before and after save, and after saving few lines are added to that .xml

<prefix></prefix>
<customEndpoint></customEndpoint>
<customSigningRegion></customSigningRegion>

I did not set it because when I checked "View Configuration", prefix parameter was omitted.
Also now I noticed that my new builds without prefix set created directory started with null.
So instead having

s3://my-bucket-name/my-job-name/master/425/artifacts/....

this was created

s3://my-bucket-name/nullmy-job-name/master/425/artifacts/....

So this CasC solved the issue

aws:
  awsCredentials:
    region: "eu-west-2"
  s3:
    container: "my-s3-bucket"
    disableSessionToken: false
    useHttp: false
    usePathStyleUrl: false
    useTransferAcceleration: false
    prefix: ""

Even I have now set prefix to empty string, CasC plugin on "View Configuration" did not added it there.

Do you still think this should be raised with Artifact Manager on S3 plugn?

from configuration-as-code-plugin.

yes it should handle that case

from configuration-as-code-plugin.