- 06 Apr, 2017 1 commit
-
-
Kamil Trzciński authored
-
- 31 Mar, 2017 1 commit
-
-
Yorick Peterse authored
These changes are ported over from https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/1502 to reduce the number of merge conflicts that may occur.
-
- 02 Mar, 2017 1 commit
-
-
Tomasz Maczukin authored
-
- 28 Feb, 2017 1 commit
-
-
Robert Schilling authored
-
- 15 Feb, 2017 3 commits
-
-
Lin Jen-Shin authored
C: Style/MultilineOperationIndentation: Align the operands of an expression in an assignment spanning multiple lines.
-
Lin Jen-Shin authored
TODO: Add tests and screenshots
-
- 25 Jan, 2017 4 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
The conflict happens when we try to update a build, but fail to do so due to fact that we update the same build concurrently for two different runners.
-
Kamil Trzcinski authored
-
- 20 Jan, 2017 1 commit
-
- 04 Jan, 2017 1 commit
-
-
Lin Jen-Shin authored
* We realized that headers were not set whenever we give 204 because `render_api_error!` doesn't preserve the headers. * We also realized that `update_runner_info` would be called in POST /builds/register every time therefore runner is updated every time, ticking the queue, making this last_update didn't work very well, and the test would be failing due to that.
-
- 19 Dec, 2016 1 commit
-
- 16 Dec, 2016 2 commits
-
-
Kim "BKC" Carlbäcker authored
-
Kim "BKC" Carlbäcker authored
-
- 15 Dec, 2016 2 commits
-
-
Kim "BKC" Carlbäcker authored
-
Kim "BKC" Carlbäcker authored
-
- 14 Dec, 2016 3 commits
-
-
Lin Jen-Shin authored
Closes #25309
-
Kim "BKC" Carlbäcker authored
-
Kim "BKC" Carlbäcker authored
-
- 03 Oct, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 13 Sep, 2016 1 commit
-
-
Tomasz Maczukin authored
-
- 07 Sep, 2016 1 commit
-
-
Kamil Trzcinski authored
-
- 05 Sep, 2016 1 commit
-
-
Jacob Vosmaer authored
-
- 17 Aug, 2016 1 commit
-
-
Yorick Peterse authored
GitLab Performance Monitoring is now able to track custom events not directly related to application performance. These events include the number of tags pushed, repositories created, builds registered, etc. The use of these events is to get a better overview of how a GitLab instance is used and how that may affect performance. For example, a large number of Git pushes may have a negative impact on the underlying storage engine. Events are stored in the "events" measurement and are not prefixed with "rails_" or "sidekiq_", this makes it easier to query events with the same name triggered from different parts of the application. All events being stored in the same measurement also makes it easier to downsample data. Currently the following events are tracked: * Creating repositories * Removing repositories * Changing the default branch of a repository * Pushing a new tag * Removing an existing tag * Pushing a commit (along with the branch being pushed to) * Pushing a new branch * Removing an existing branch * Importing a repository (along with the URL we're importing) * Forking a repository (along with the source/target path) * CI builds registered (and when no build could be found) * CI builds being updated * Rails and Sidekiq exceptions Fixes gitlab-org/gitlab-ce#13720
-
- 29 Jun, 2016 1 commit
-
- 28 Jun, 2016 3 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
We store the sizes as a hash from path to bytes like: ``` ruby {'ci_artifacts.txt' => 27, 'other_artifacts_0.1.2/another-subdirectory/banana_sample.gif' => 71759, 'other_artifacts_0.1.2/doc_sample.txt' => 1314, 'rails_sample.jpg' => 35255, 'tests_encoding/utf8 test dir ✓/regular_file_2' => 7} ``` So that it's easier to access than reading gzip file again.
-
- 16 Jun, 2016 2 commits
-
-
James Lopez authored
This reverts commit 13e37a3e.
-
James Lopez authored
-
- 13 Jun, 2016 2 commits
-
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
- 20 Apr, 2016 6 commits
-
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
[ci skip]
-
Tomasz Maczukin authored
[ci skip]
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-
Tomasz Maczukin authored
-