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
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot