Gitlab CE - always build success

Summary

We are using AWS ElasticBeanstalk in our stack and till gitlab version 8.8.0 everything was working but now every time AWS returns error gitlab says that build is successful.

Steps to reproduce

Do deploy to AWS ElasticBeanstalk

Expected behavior

Hook /opt/elasticbeanstalk/hooks/appdeploy/post/98_warmup_cache.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.

INFO: Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].

ERROR: Unsuccessful command execution on instance id(s) 'i-b1100e70'. Aborting the operation.

ERROR: Failed to deploy application.

Build failed

Actual behavior

Hook /opt/elasticbeanstalk/hooks/appdeploy/post/98_warmup_cache.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.

INFO: Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].

ERROR: Unsuccessful command execution on instance id(s) 'i-b1100e70'. Aborting the operation.

ERROR: Failed to deploy application.

Build succeeded

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)

Output of checks

Results of GitLab application Check

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:check SANITIZE=true)

(For installations from source run and paste the output of: sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)

(we will only investigate if the tests are passing)

Results of GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of: sudo gitlab-rake gitlab:env:info)

(For installations from source run and paste the output of: sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production)

Possible fixes

(If you can, link to the line of code that might be responsible for the problem)

Edited Jul 27, 2020 by Jason Yavorsky