As we are migrating from drone 0.4 to 0.7 we are running in to an issue with our s3 uploads.
During the s3 step the process exits with ‘file does not exist’.
Is this perhaps because the ‘plugins/s3’ image cannot access the workspace directory used in the build-step?
Any tips on where to look would be helpful, as the current documentation is quite lacking on these points.
I cannot advise further without seeing your yaml configuration.
The likely root cause is that you are trying to upload a file outside the workspace which is not possible. The S3 plugin will only have access to the workspace and files in the workspace. You can learn more about the worskpace at http://docs.drone.io/workspace/
For example, this will not work because the file is outside the workspace:
However, the ‘source’ is not taken as a file but the entire path is placed in the bucket. This is definitely very different behaviour as before. We could just point to the file using the source-path and put the file in the target-path. Now it creates the entire source-path inside the target. This to me is very odd behaviour and not what we want to use at all, is there a way to get the old behaviour?
The plugin now supports globbing. Have you considered how this might impact the design or the ability for the plugin to automatically trim the path prefix? The current approach does not try to be clever. It is simple and declarative and documented. If you think it can be improved, send a pull request.