bitbucket-upload-file pipe fails when PWD of script is not CLONE_DIR

Question

When using 0.7.3 of the upload pipe you can shoot yourself in the foot if you have navigated away from the clone dir with your script entries in the step.

The pipe will not find any globbed file patterns.

You need to navigate to `$BITBUCKET_CLONE_DIR` before inintializing the pipe.

When the pipe starts the nested container it uses `--workdir=${pwd}`. So if your main container is on a different working directory, the glob pattern will be wrong since it's only correct when relative to the clone dir.

Please adjust the documentation to mention that your working directory needs to be the clone dir before invoking the upload pipe.

Igor Stoyanov · Accepted Answer

@Markus Napp . Thank you you for your suggestion.

It is already added in the variables description.

FILENAME (*) - Name of the local file to upload. Supports glob patterns "*". e.g. *.html. Limit max 10 files, if limit reached - build fails. Accepts files only from BITBUCKET_CLONE_DIR or any subfolders in this path.

Also we will consider adding some logs to the pipe, so the logic will be more clear during pipe execution.

Regards, Igor