summaryrefslogtreecommitdiff
path: root/.gitlab-ci.yml
Commit message (Collapse)AuthorAgeFilesLines
* update gitlab-ci script syntaxJames Lopez2016-02-261-1/+1
|
* Update URL syntaxJames Lopez2016-02-251-1/+1
|
* updated gitlab-ci script to include builds URLJames Lopez2016-02-241-2/+285
|
* testJames Lopez2016-02-241-5/+1
|
* testing scriptJames Lopez2016-02-241-285/+6
|
* updated gitlab ci based on feedbackJames Lopez2016-02-241-2/+2
|
* fix gitlab-ci.ymlJames Lopez2016-02-221-3/+3
|
* Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce into ↵James Lopez2016-02-221-33/+33
|\ | | | | | | | | | | | | feature/slack-notifications-on-ci # Conflicts: # .gitlab-ci.yml
| * revert back to ruby 2.1 - use 2.1.8James Lopez2016-02-191-145/+145
| |
| * revert back to ruby 2.1James Lopez2016-02-191-144/+144
| |
* | resolve merge conflictJames Lopez2016-02-181-1/+9
| |
* | Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce into ↵James Lopez2016-02-181-4/+131
|\ \ | |/ | | | | | | | | | | feature/slack-notifications-on-ci # Conflicts: # .gitlab-ci.yml
| * Use caching, instead of haxxy /cacheuse-cachingKamil Trzcinski2016-02-101-0/+46
| |
| * split gitlab-ci builds for ruby 2.1James Lopez2016-02-081-4/+85
| |
* | default slack notification channelJames Lopez2016-02-081-1/+1
| |
* | update with branch and tags restrictionJames Lopez2016-02-051-6/+5
| |
* | removed slack task and added bash script instead. Updated gitlab-ci config fileJames Lopez2016-02-051-4/+7
| |
* | uncomment restriction to branches or tagsJames Lopez2016-02-031-3/+3
| |
* | refactored rake task and make build passJames Lopez2016-02-031-1/+1
| |
* | update gitlab ci configJames Lopez2016-02-031-1/+1
| |
* | update ci configuration to send slack notifications on failure and added ↵James Lopez2016-02-031-1/+32
|/ | | | rake task
* merge spec and spinach jobsJames Lopez2016-01-271-97/+4
|
* update gitlab ci settings to include ruby 2.1 imagesJames Lopez2016-01-271-0/+116
|
* Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce into update-ruby-2.2.4James Lopez2016-01-251-1/+1
|\
| * Speed-up docker based buildsspeed-up-buildsKamil Trzcinski2016-01-221-1/+1
| | | | | | | | | | | | | | Enable to: - Use APT cache - Use Bundler cache - Use PhantomJS cache
* | Merge branch 'master' of gitlab.com:gitlab-org/gitlab-ce into update-ruby-2.2.4James Lopez2016-01-221-2/+10
|\ \ | |/ | | | | | | # Conflicts: # .gitlab-ci.yml
| * More docker stuff in gitlab-ci.ymlJacob Vosmaer2016-01-221-4/+10
| |
| * Allow empty Mysql password on CImysql-password-ciJacob Vosmaer2016-01-221-0/+3
| |
* | update gitlab ci docker image versionJames Lopez2016-01-211-0/+1
|/
* Ensure that doesn't have pending migrations when running the specsDouglas Barbosa Alexandre2016-01-191-2/+2
|
* Precompile assets before running feature specs. #4662Rubén Dávila2015-12-281-0/+1
|
* Revert "Merge branch 'remove-redcloth' into 'master' "revert-2037Douwe Maan2015-12-111-1/+2
| | | | | This reverts commit e426c027b0a2a3aa0dea1d833008f2bfd814f483, reversing changes made to c3676aa156981092b7f03f1a3e74bb819cfa2fc3.
* Run db:reset before db:create on CIrs-reset-dbRobert Speicher2015-12-091-1/+1
|
* Merge branch 'split-up-builds' into 'master' Dmitriy Zaporozhets2015-12-091-2/+30
|\ | | | | | | | | | | | | Split up 20min+ `spec:other` and `spinach:project` builds to increase parallelization See merge request !2036
| * Split up spec:other even moreDouwe Maan2015-12-091-0/+14
| |
| * Split up specs moreDouwe Maan2015-12-091-1/+8
| |
| * Split up feature specs moreDouwe Maan2015-12-091-2/+9
| |
* | Remove RedCloth and no longer allow bundle-audit to failDouwe Maan2015-12-091-2/+1
|/
* Allow bundler:audit to failDmitriy Zaporozhets2015-11-231-0/+1
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Fix gitlab-ci.yml syntaxDmitriy Zaporozhets2015-11-231-3/+3
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Add bundler-audit to CIDmitriy Zaporozhets2015-11-231-0/+8
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Code duplication check should be enabled nowremove-code-duplicationDmitriy Zaporozhets2015-11-171-1/+0
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Allow flay to fail for now since there is still a lot of refactoring todoDmitriy Zaporozhets2015-11-161-0/+1
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Dont allow code duplication check to failDmitriy Zaporozhets2015-11-161-1/+0
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Don't allow flog failure any moreDmitriy Zaporozhets2015-11-131-1/+0
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Add flay: tool to find duplicate codeflayDmitriy Zaporozhets2015-11-111-0/+8
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Allow flog failure for nowDmitriy Zaporozhets2015-11-111-0/+1
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Add method complexity check to CIflogDmitriy Zaporozhets2015-11-101-0/+7
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Allow benchmark failures for the time beingYorick Peterse2015-10-051-0/+1
| | | | | This will be disallowed again once the existing benchmarks pass (which relies on #2341).
* Basic setup for an RSpec based benchmark suitebenchmark-suiteYorick Peterse2015-10-021-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.