-
Notifications
You must be signed in to change notification settings - Fork 4k
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
(pipelines.CodePipeline): unable to use additional_inputs #17224
Comments
Ignore that, see below |
Hmm this looks like |
The
Is there a way to modify this from within cdk? Like try using POSIX compliant |
OK I've made this deployment successful. It is the issue with the shell. We cannot use
That solves it. That also means that this should be treated as a bug using ShellStep seems to make it impossible to have |
Hey @ustulation, It looks from your comments like you have figured out the problem independently. Can we consider this resolved, or does it still need attention from a team member? |
I'll leave that to yous but I would consider this to be a bug. The fact that |
I experimented this error and ended downgrading to version 1.128. I needed to move forward with another change and could not verify why this was happening. |
The rendering of `additionalInputs` was using a bashism that is not supported by CodeBuild by default. Turn ``` [[ ! -d "directory" ]] ``` into ``` [ ! -d "directory" ] ``` Fixes #17224
The rendering of `additionalInputs` was using a bashism that is not supported by CodeBuild by default. Turn ``` [[ ! -d "directory" ]] ``` into ``` [ ! -d "directory" ] ``` Fixes #17224 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
The rendering of `additionalInputs` was using a bashism that is not supported by CodeBuild by default. Turn ``` [[ ! -d "directory" ]] ``` into ``` [ ! -d "directory" ] ``` Fixes #17224 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
The rendering of `additionalInputs` was using a bashism that is not supported by CodeBuild by default. Turn ``` [[ ! -d "directory" ]] ``` into ``` [ ! -d "directory" ] ``` Fixes aws#17224 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
I came here after googling the error message. Although the issue as originally reported has been fixed, the documentation on how to properly use additionalInputs could be better. I'll create a new issue for that. |
@rix0rrr In a CodeBuildStep running a powershell script, using a
The additional input is a codecommit source, in this case. Looks like it's trying to run bash commands in powershell. More specifically: Powershell does have some bash-like aliases, but Tried the OP's workaround, using Any idea how to fix this? Note: If we specify the same |
What is the problem?
No matter what name I supply for the additional inputs directory, it fails at:
followed by:
followed by:
followed by:
causing the build to fail.
Reproduction Steps
My code simply looks like:
I've put
blah
etc in place of real github sources are they are all private repositories. The code is pulled in fine, but the build/synth step fails forsource0
above.I've tried various combinations like
../blah-1234
(to create it in a sibling directory) etc. but all fail with similar error messages.I'm suspicious of:
and think it's something in the aws script that's failing somewhere?
What did you expect to happen?
I expected the build to pass
What actually happened?
The build failed
CDK CLI Version
1.129.0
Framework Version
No response
Node.js Version
N/A
OS
Arch Linux
Language
Python
Language Version
No response
Other information
No response
The text was updated successfully, but these errors were encountered: