In prod, the cloud controller rakefile is used when running migrations, i.e. bundle exec rake db:migrate, so we can't require ci_reporter from the rake file as that gem won't have been installed since it is only installed as part of the test group. Note that this is the only component that we need the rakefile for in prod, so it is the only one that needs such an update, which is good, because there isn't a standard way to tell if the DEA's, Rotuer's, etc. rakefiles are being invoked in in prod or test mode. Change-Id: I92af1cd18f0f5f03c4407cf7751265114bc770d3
…of rejecting it with an "Invalid uploaded file". This situation can arise as a result of the resource pool already containing all of the contents of an app."
…cting it with an "Invalid uploaded file". This situation can arise as a result of the resource pool already containing all of the contents of an app. Change-Id: I8205746c15a7405f9cc64b4be1d3e0c196b645ec
…e. For example, if database connection failed due to the failure on the database server, HM just logs:"
…example, if database connection failed due to the failure on the database server, HM just logs: ERROR -- ActiveRecord::StatementInvalid("PGError: ... and no recovery actions are taken so that we happen to fall into the infinite loop of errors, after the database server is recovered. (In this case, we need to repair HM by rebooting it's process manually....) I added 'exit!' to reduce this manual operation. Change-Id: Ief34645165884ae8779f3337cb9dae3fb15a5dec
…ride the domain (instead of vcap.me)"
… for a container"
…e domain (instead of vcap.me) Change-Id: If6b6cc63e21f9cbd20c3787ec0e2d159932ec477