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?
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
I'm happy to announce that Bamboo 7.1 has been released and it’s overflowing with awesome new features. Top-voted issues First and foremost, a bunch of JAC top voted issues has been delivered - y...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event