The logs just pipe stdout and stderr. If you want to stop and fail the build as soon as the text shows up, then you would need to develop a log checking thread/process to whatever you are running. In other words, it's not a Bamboo thing.
If you can wait until the job is finished, then you can create another job in a subsequent stage that gets the log contents via an http "GET". You can use a program like curl or write up something using the scripting language of your choice. The URL is consistent and looks something like: "http://bamboo_url/download/PROJ-PLAN-JOB/build_logs/PROG-PLAN-JOB-BUILDNUM.log". The build number and build result keys are Bamboo variables. Once you have the log text, it's a simple matter of grepping for the line and then exiting with either a 0 exit code (success) or non-zero exit code (failure).
@chris Agreed. In TeamCity this was super easy, unfortunate to discover this limitation...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.