gitlab-org--gitlab-foss/.gitlab-ci.yml

# This file is generated by GitLab CI
before_script:
  - ./scripts/prepare_build.sh
  - ruby -v
  - which ruby
  - gem install bundler --no-ri --no-rdoc
  - cp config/gitlab.yml.example config/gitlab.yml
  - touch log/application.log
  - touch log/test.log
  - bundle install --without postgres production --jobs $(nproc)  "${FLAGS[@]}"
  - bundle exec rake db:create RAILS_ENV=test

spec:feature:
  script:
    - RAILS_ENV=test SIMPLECOV=true bundle exec rake spec:feature
  tags:
    - ruby
    - mysql

spec:api:
  script:
    - RAILS_ENV=test SIMPLECOV=true bundle exec rake spec:api
  tags:
    - ruby
    - mysql

spec:benchmark:
  script:
    - RAILS_ENV=test bundle exec rake spec:benchmark
  tags:
    - ruby
    - mysql
  allow_failure: true

spec:other:
  script:
    - RAILS_ENV=test SIMPLECOV=true bundle exec rake spec:other
  tags:
    - ruby
    - mysql

spinach:project:
  script:
    - RAILS_ENV=test SIMPLECOV=true bundle exec rake spinach:project
  tags:
    - ruby
    - mysql

spinach:other:
  script:
    - RAILS_ENV=test SIMPLECOV=true bundle exec rake spinach:other
  tags:
    - ruby
    - mysql

teaspoon:
  script:
    - RAILS_ENV=test bundle exec teaspoon
  tags:
    - ruby
    - mysql

rubocop:
  script:
    - bundle exec rubocop
  tags:
    - ruby
    - mysql

brakeman:
  script:
    - bundle exec rake brakeman
  tags:
    - ruby
    - mysql
new syntax of .gitlab-ci.yml 2015-06-15 05:00:13 -04:00			`# This file is generated by GitLab CI`
Refactor CI script Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2015-06-04 10:54:32 -04:00			`before_script:`
Use correct name for the script. 2015-06-18 04:56:35 -04:00			`- ./scripts/prepare_build.sh`
added ci yaml 2015-06-03 16:05:33 -04:00			`- ruby -v`
			`- which ruby`
Add a build preparation script, modify gitlab.ci.yml to use the script. 2015-06-17 06:23:43 -04:00			`- gem install bundler --no-ri --no-rdoc`
added ci yaml 2015-06-03 16:05:33 -04:00			`- cp config/gitlab.yml.example config/gitlab.yml`
			`- touch log/application.log`
			`- touch log/test.log`
Add a build preparation script, modify gitlab.ci.yml to use the script. 2015-06-17 06:23:43 -04:00			`- bundle install --without postgres production --jobs $(nproc) "${FLAGS[@]}"`
added ci yaml 2015-06-03 16:05:33 -04:00			`- bundle exec rake db:create RAILS_ENV=test`
Split rspec and spinach tests in parallel 2015-06-23 10:43:24 -04:00
			`spec:feature:`
			`script:`
			`- RAILS_ENV=test SIMPLECOV=true bundle exec rake spec:feature`
			`tags:`
			`- ruby`
			`- mysql`

			`spec:api:`
			`script:`
			`- RAILS_ENV=test SIMPLECOV=true bundle exec rake spec:api`
			`tags:`
			`- ruby`
			`- mysql`

Basic setup for an RSpec based benchmark suite This benchmark suite uses benchmark-ips (https://github.com/evanphx/benchmark-ips) behind the scenes. Specs can be turned into benchmark specs by setting "benchmark" to "true" in the top-level describe block like so: describe SomeClass, benchmark: true do end Writing benchmarks can be done using custom RSpec matchers, for example: describe MaruTheCat, benchmark: true do describe '#jump_in_box' do it 'should run 1000 iterations per second' do maru = described_class.new expect { maru.jump_in_box }.to iterate_per_second(1000) end end end By default the "iterate_per_second" expectation requires a standard deviation under 30% (this is just an arbitrary default for now). You can change this by chaining "with_maximum_stddev" on the expectation: expect { maru.jump_in_box }.to iterate_per_second(1000) .with_maximum_stddev(10) This will change the expectation to require a maximum deviation of 10%. Alternatively you can use the it block style to write specs: describe MaruTheCat, benchmark: true do describe '#jump_in_box' do subject { -> { described_class.new } } it { is_expected.to iterate_per_second(1000) } end end Because "iterate_per_second" operates on a block, opposed to a static value, the "subject" method must return a Proc. This looks a bit goofy but I have been unable to find a nice way around this. 2015-10-02 11:00:23 -04:00			`spec:benchmark:`
			`script:`
			`- RAILS_ENV=test bundle exec rake spec:benchmark`
			`tags:`
			`- ruby`
			`- mysql`
Allow benchmark failures for the time being This will be disallowed again once the existing benchmarks pass (which relies on #2341). 2015-10-05 05:08:52 -04:00			`allow_failure: true`
Basic setup for an RSpec based benchmark suite This benchmark suite uses benchmark-ips (https://github.com/evanphx/benchmark-ips) behind the scenes. Specs can be turned into benchmark specs by setting "benchmark" to "true" in the top-level describe block like so: describe SomeClass, benchmark: true do end Writing benchmarks can be done using custom RSpec matchers, for example: describe MaruTheCat, benchmark: true do describe '#jump_in_box' do it 'should run 1000 iterations per second' do maru = described_class.new expect { maru.jump_in_box }.to iterate_per_second(1000) end end end By default the "iterate_per_second" expectation requires a standard deviation under 30% (this is just an arbitrary default for now). You can change this by chaining "with_maximum_stddev" on the expectation: expect { maru.jump_in_box }.to iterate_per_second(1000) .with_maximum_stddev(10) This will change the expectation to require a maximum deviation of 10%. Alternatively you can use the it block style to write specs: describe MaruTheCat, benchmark: true do describe '#jump_in_box' do subject { -> { described_class.new } } it { is_expected.to iterate_per_second(1000) } end end Because "iterate_per_second" operates on a block, opposed to a static value, the "subject" method must return a Proc. This looks a bit goofy but I have been unable to find a nice way around this. 2015-10-02 11:00:23 -04:00
Split rspec and spinach tests in parallel 2015-06-23 10:43:24 -04:00			`spec:other:`
			`script:`
			`- RAILS_ENV=test SIMPLECOV=true bundle exec rake spec:other`
			`tags:`
			`- ruby`
			`- mysql`

			`spinach:project:`
new syntax of .gitlab-ci.yml 2015-06-15 05:00:13 -04:00			`script:`
Split rspec and spinach tests in parallel 2015-06-23 10:43:24 -04:00			`- RAILS_ENV=test SIMPLECOV=true bundle exec rake spinach:project`
new syntax of .gitlab-ci.yml 2015-06-15 05:00:13 -04:00			`tags:`
			`- ruby`
			`- mysql`

Split rspec and spinach tests in parallel 2015-06-23 10:43:24 -04:00			`spinach:other:`
new syntax of .gitlab-ci.yml 2015-06-15 05:00:13 -04:00			`script:`
Split rspec and spinach tests in parallel 2015-06-23 10:43:24 -04:00			`- RAILS_ENV=test SIMPLECOV=true bundle exec rake spinach:other`
new syntax of .gitlab-ci.yml 2015-06-15 05:00:13 -04:00			`tags:`
			`- ruby`
			`- mysql`

Remove jasmine:ci task, execute teaspoon directly on CI 2015-06-28 16:27:40 -04:00			`teaspoon:`
new syntax of .gitlab-ci.yml 2015-06-15 05:00:13 -04:00			`script:`
Remove jasmine:ci task, execute teaspoon directly on CI 2015-06-28 16:27:40 -04:00			`- RAILS_ENV=test bundle exec teaspoon`
new syntax of .gitlab-ci.yml 2015-06-15 05:00:13 -04:00			`tags:`
			`- ruby`
			`- mysql`

Split rspec and spinach tests in parallel 2015-06-23 10:43:24 -04:00			`rubocop:`
new syntax of .gitlab-ci.yml 2015-06-15 05:00:13 -04:00			`script:`
			`- bundle exec rubocop`
			`tags:`
			`- ruby`
			`- mysql`

Split rspec and spinach tests in parallel 2015-06-23 10:43:24 -04:00			`brakeman:`
new syntax of .gitlab-ci.yml 2015-06-15 05:00:13 -04:00			`script:`
			`- bundle exec rake brakeman`
			`tags:`
			`- ruby`
Add a build preparation script, modify gitlab.ci.yml to use the script. 2015-06-17 06:23:43 -04:00			`- mysql`