Closed davidjb closed 4 days ago
@davidjb Thanks for finding and providing a fix for this. I just spent 2 hours trying to figure out why this was broken in my job.
@brentmmarks can this get prioritized into the next release please? The impacted line export PATH=$PATH:/usr/local/bin/sam
is obviously incorrect. One does not generally include an executable in the PATH.
This was already addressed on #76, and it is on current version. I'm closing.
At present, any commands run after
sam/install
will fail - at least within the most recent machine image (ubuntu-2204:2023.07.2
). This PR fixes subsequent CI commands from failing to be processed by avoiding manipulatingPATH
incorrectly.With an example config like so, commands before
sam/install
will work but anything after - the finalrun
step - fails withExited with code exit status 127
because thesam/install
command has adjusted thePATH
incorrectly to add/usr/local/bin/sam
as a directory:PATH
should only feature directories; fromman bash
:/usr/local/bin
is already on thePATH
as already implicitly tested by line 46 (which sam
) which would already be failing immediately ifsam
couldn't be found (such as in different execution environments), so this PR simply removes the redundant, breaking line.Edit: a workaround until this is merged is that
sam/install
can just be replaced with its raw script: