Gitlab-CI和宝石公寓

Question

I'm experiencing a strange problem while trying to set up Gitlab CI on my Rails 5.1 project wich uses apartment gem for multitennancy support. I've got docker-compose set up to build my containers and run tests. And they are passing on my local machine, but Gitlab pipelines keep failing with this error.

$ bundle exec rspec
/builds/demiurge/new_world/spec/models/char/skill_spec.rb:5: warning: toplevel constant Skill referenced by Char::Skill
Run options: include {:focus=>true}

All examples were filtered out; ignoring {:focus=>true}

An error occurred in a `before(:suite)` hook.
Failure/Error: Apartment::Tenant.create slug

ActiveRecord::StatementInvalid:
  PG::InFailedSqlTransaction: ERROR:  current transaction is aborted, commands ignored until end of transaction block
  : SET search_path TO "public", "shared_extensions"
# ./app/models/world.rb:36:in `create_tenant'
# ./spec/rails_helper.rb:52:in `block (2 levels) in <top (required)>'
# ------------------
# --- Caused by: ---
# PG::UndefinedObject:
#   ERROR:  type "hstore" does not exist
#   LINE 1: ...har_id" integer, "type" character varying, "data" hstore, "p...
#                                                                ^
#   ./db/schema.rb:292:in `block in <top (required)>'


Finished in 0.58676 seconds (files took 5 seconds to load)
0 examples, 0 failures, 1 error occurred outside of examples

My docker-compose setup is simple:

cache:
 image: redis:alpine
 ports:
   - 6379:6379

db:
 image: postgres:9.6-alpine
 volumes:
   - ./data/db/data:/var/lib/postgresql/data
 ports:
   - 5432:5432

And my gilab-ci.yml looks like this . And I also have a lib/tasks/apartment.rake task set up like this that is supposed to enable hstore on DB creation. The task passes on CI, but it still returnes the same error.

Answer 1

ERROR: type "hstore" does not exist This error tells you that the hstore extension is not present on your postgres database.
You have to enable it in a migration before using this datatype anywhere.

def change
  enable_extension "hstore"
end

You have to ensure that the database user is a superuser