Region Override failing


#1

Drone s3 plugin

Hello, thanks for checking out my issue.

I have a pipeline setup to run serenity tests at deploy/master merge time.
We are trying to push the serenity test report into an s3 bucket.

Unfortunately, the region override seems to be failing, pointing at us-east-1 though I have set eu-west-2 override on the plugin. Any ideas on how to get around this would be most welcome.

Yaml

 upload-serenity-report:
    image: plugins/s3
    secrets: [ S3_BUCKET_NAME, aws_access_key_id, aws_secret_access_key ]
    settings:
      region: eu-west-2
      bucket: $${S3_BUCKET_NAME}
      access_key:
        from_secret: aws_access_key_id
      secret_key:
        from_secret: aws_secret_access_key
      source: /target/site/serenity/**
      target: /$${DRONE_BUILD_NUMBER}/report/
    when:
      branch: master
      event: push
      status:
        - success
        - failure

Error report from Drone

time="2019-02-08T09:44:20Z" level=info msg="Attempting to upload" bucket=us-east-1 endpoint= region=us-east-1

0s

2

time="2019-02-08T09:44:20Z" level=error msg="Could not match files" error="file does not exist"

0s

3

time="2019-02-08T09:44:20Z" level=fatal msg="file does not exist"

The plugin docs are here http://plugins.drone.io/drone-plugins/drone-s3/

Again, much appreciated for any ideas.


#2

which version of drone are you using? because the yaml looks like a combination of the 0.8 and 1.0 yaml which is probably invalid and could explain the reason it isn’t working as expected. (Also it would be helpful if you could post the yaml as a formatted code block so that spacing is preserved)


#3

Hey, thanks for your reply, apologies i am new to this site and did not know the formatting, have updated the original post.

I appreciate my syntax is probably a bit all over the place I have tried to write this several different ways before crying for help, we are on drone 0.8.


#4

The settings section was introduced in 1.0 and will need to be removed. Take all the parameters in the settings block and move them directly under upload-serenity-report and the yaml should be 0.8 compliant.


#5

Hello, my friend, this was it. Thank you so much :blush: we are just checking the bucket to see if the report really went in… but feedback from drone was :white_check_mark:

Thank you again.