I can, but I’m not sure that will help resolve this issue.
The problem is not with the bash script, it’s with the URL that is being hit to get the S3 bucket that the report(s) should be uploaded to. At that point, the request that is being made is rejected because the commit id is a 12 character hash, instead of a 40 character hash (or a number of digits followed by a colon followed by the 12 character hash).
I was able to fix this at the codeship end before moving to Codeship Pro by generating the long hash instead, but in Codeship Pro, we don’t have access to the git repository inside the containers that are running the code, only the environment variables that are provided.
What is the purpose of the leading
\d+: on the short hash? Is that intentional? It’s not something I’ve ever come across in git, although it does look a bit like what mercurial revision:hash used to look like.