[Outside of our control] Change the directory to the current WORKING_DIR for AWS Batch and Google Batch task runners

[anna-geller]

Feature description

Azure already works

TODO: cd to the workingDir after starting the taskrun container/process

• [ ] AWS Batch
• [ ] Google Batch

EDIT: likely will never be done:

1. Reference issue at GCP side: https://github.com/googleapis/google-cloud-java/issues/10670
2. No mechanism to track Batch feature requests open to the public other than keeping an eye on the changelog

[loicmathieu]

After more thoughts, it can cause issues for images where the entry point is not a shell (for ex AWS CLI).

So we decided to warn in the description for now, we open issues on both AWS and GCP side to be able to fix it upstream.

The following sentence has been added to both description:

Warning, contrarily to other task runners, this task runner didn't run the task in the working directory but in the root directory. You must use the {{workingDir}} Pebble expression or the WORKING_DIR environment variable to access files.

[loicmathieu]

Reference issue at AWS side: https://github.com/aws/aws-sdk/issues/716

[loicmathieu]

Reference issue at GCP side: https://github.com/googleapis/google-cloud-java/issues/10670