Hi guys,
I use Amazon CodeDeploy for my Bamboo build process. Out of the blue, CodeDeploy is failing when it runs my 'AfterInstall' bash scripts. What's odd is that this was working fine, and then suddenly it stopped working. Also, if I run CodeDeploy from within the AWS console, it works fine. The issue is only when Bamboo triggers CodeDeploy.
Again, the issue started out of the blue when the process was working and no changes were made.
CodeDeploy is finding and running the Bash file, but it throws this error and fails: [stderr]/usr/bin/env: bash : No such file or directory
Again, this works fine if I run it from CodeDeploy directly. Any idea of what could be going on or know of any changes in how Bamboo calls CodeDeploy?
Thanks!
-Jeff
FYI, this was caused by my elastic instance changing from a Linux image to a Windows image. Because of this, the file changed from a LF to a CRLF and added carriage returns to my bash files.
I fixed this 2 differnet ways:
I disabled all Windows options in my 'Image Configurations'.
In .gitattributes i added the line
*.sh eol=lf
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.