- 01 6月, 2017 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 07 4月, 2017 1 次提交
-
-
由 Kamil Trzciński 提交于
-
- 31 3月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
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.
-
- 03 3月, 2017 1 次提交
-
-
由 Tomasz Maczukin 提交于
-
- 28 2月, 2017 1 次提交
-
-
由 Robert Schilling 提交于
-
- 15 2月, 2017 3 次提交
-
-
由 Lin Jen-Shin 提交于
C: Style/MultilineOperationIndentation: Align the operands of an expression in an assignment spanning multiple lines.
-
由 Lin Jen-Shin 提交于
TODO: Add tests and screenshots
-
- 25 1月, 2017 4 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
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 提交于
-
- 20 1月, 2017 1 次提交
-
- 04 1月, 2017 1 次提交
-
-
由 Lin Jen-Shin 提交于
* 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 12月, 2016 1 次提交
- 16 12月, 2016 4 次提交
-
-
由 Kim "BKC" Carlbäcker 提交于
-
由 Kim "BKC" Carlbäcker 提交于
-
由 Kim "BKC" Carlbäcker 提交于
-
由 Kim "BKC" Carlbäcker 提交于
-
- 15 12月, 2016 1 次提交
-
-
由 Lin Jen-Shin 提交于
Closes #25309
-
- 14 12月, 2016 2 次提交
-
-
由 Kim "BKC" Carlbäcker 提交于
-
由 Kim "BKC" Carlbäcker 提交于
-
- 03 10月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 13 9月, 2016 1 次提交
-
-
由 Tomasz Maczukin 提交于
-
- 07 9月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 05 9月, 2016 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 17 8月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
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 6月, 2016 1 次提交
-
- 28 6月, 2016 3 次提交
-
-
由 Lin Jen-Shin 提交于
-
由 Lin Jen-Shin 提交于
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 6月, 2016 2 次提交
-
-
由 James Lopez 提交于
This reverts commit 13e37a3e.
-
由 James Lopez 提交于
-
- 13 6月, 2016 2 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Kamil Trzcinski 提交于
-
- 20 4月, 2016 5 次提交
-
-
由 Tomasz Maczukin 提交于
-
由 Tomasz Maczukin 提交于
[ci skip]
-
由 Tomasz Maczukin 提交于
[ci skip]
-
由 Tomasz Maczukin 提交于
-
由 Tomasz Maczukin 提交于
-