-
Notifications
You must be signed in to change notification settings - Fork 982
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes root-directory name of YAML_FILE - path to uppercase automatically, which leads to YAML_FILE_ERROR: no such file or directory #470
Comments
It looks like you're using Windows, which is not fully supported by CodeBuild Local. Looking at the logs provided, it seems that the relative file paths are being misinterpreted as UNC absolute paths. Specifying a leading |
Yes, I'm on Just tried it with The entire output till failure was:
This time, the program prepended the full path, but again made the first letter capital ( |
|
Following your advice, I replaced to get the final command: The output was yet again:
Then, for the sake of completeness, I replaced also to obtain the final command: Regarding the output, it did not have a notable effect:
NOTE on double-quotes around the paths containing the Windows-separator "": This is mandatory since without quotes e.g. the buildspec.yml - file would be interpreted like so: |
Not positive, but maybe this issue is addressed by pending PR #619 or my version See comment #328 (comment) |
I run the AWS-CodeBuild locally with the following command in the root-directory of the related project "projectname":
The output Build Command in the CLI is:
Error:
/Src/build/buildspec.tests.pre-deploy.yml:
no such file or directoryThe actual root-directory starts with a lower case like so:
src\build\buildspec.tests.pre-deploy.yml
Now this begs the question why the software would change the first letter from lowercase to uppercase?
Next, what does the following state stand for:
DOWNLOAD_SOURCE State: FAILED
Is it related to the previous ill-renaming of the root-directory
/scr/
?The text was updated successfully, but these errors were encountered: