- 14 Oct, 2015 3 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 13 Oct, 2015 4 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
Douwe Maan authored
-
- 08 Oct, 2015 2 commits
-
-
Douwe Maan authored
-
Douwe Maan authored
-
- 07 Oct, 2015 3 commits
-
-
Robert Speicher authored
[ci skip]
-
Douwe Maan authored
-
Douwe Maan authored
-
- 05 Oct, 2015 6 commits
-
-
Robert Speicher authored
This option only existed to ease the CI-to-CE/EE migration process. This commit partially reverts 8b05abe8
-
Yorick Peterse authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 03 Oct, 2015 1 commit
-
-
Guilherme Garnier authored
-
- 02 Oct, 2015 1 commit
-
-
Yorick Peterse authored
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.
-
- 01 Oct, 2015 1 commit
-
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 30 Sep, 2015 2 commits
-
-
Kamil Trzcinski authored
- It delegates name, path, gitlab_url, ssh_url_to_repo - Remove ability to set this parameters using CI API This fixes GitLab project rename, namespace change, repository rename, etc.
-
Петров Роман authored
-
- 25 Sep, 2015 1 commit
-
-
Paul Beattie authored
This adds support for AWS S3 SSE with S3 managed keys, this means the data is encrypted at rest and the encryption is handled transparently to the end user as well as in the AWS Console. This is optional and not required to make S3 uploads work.
-
- 24 Sep, 2015 2 commits
-
-
Ben Boeckel authored
-
Ben Boeckel authored
-
- 23 Sep, 2015 2 commits
-
-
Douwe Maan authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 22 Sep, 2015 3 commits
-
-
Patricio Cano authored
Added ability to update or set the identity of an existing user, like the documentation said it was possible, but actually wasn't.
-
Achilleas Pipinellis authored
This was causing the task `gitlab-rake gitlab:incoming_email:check` to fail.
-
Kamil Trzcinski authored
-
- 21 Sep, 2015 6 commits
-
-
Jared Szechy authored
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Douwe Maan authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 20 Sep, 2015 3 commits
-
-
Robert Speicher authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-