- 12 3月, 2016 1 次提交
-
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
- 09 3月, 2016 2 次提交
-
-
-
由 Yorick Peterse 提交于
This wasn't included in gitlab-org/gitlab-ce!3000.
-
- 06 3月, 2016 1 次提交
-
-
由 Robert Speicher 提交于
This was removed from the interface in https://github.com/gitlabhq/gitlabhq/pull/6027 but its implementation lingered around for two years.
-
- 04 3月, 2016 1 次提交
-
-
由 Jacob Vosmaer 提交于
-
- 26 2月, 2016 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
The only major difference with the EE version is the change from a light and dark logo to only a header logo The dark logo wasn't used anyway, so it seemed to make sense to me to rename the field to the actual function of it
-
- 20 2月, 2016 6 次提交
-
-
-
-
-
由 Rubén Dávila 提交于
-
由 Grzegorz Bizon 提交于
-
由 Grzegorz Bizon 提交于
-
- 17 2月, 2016 1 次提交
-
-
由 Tap 提交于
- Add label description - Show label row when filtering issues or merge requests by label
-
- 09 2月, 2016 2 次提交
-
-
由 Valery Sizov 提交于
-
由 Jason Lee 提交于
-
- 04 2月, 2016 1 次提交
-
-
由 Kamil Trzcinski 提交于
-
- 03 2月, 2016 2 次提交
-
-
由 Kamil Trzcinski 提交于
Add the `read_build` ability if user is anonymous or guest and allow_guest_to_access_builds is enabled.
-
由 James Lopez 提交于
-
- 02 2月, 2016 1 次提交
-
-
由 Stan Hu 提交于
Currently any spam detected by Akismet by non-members via API will be logged in a separate table in the admin page. Closes #5612
-
- 29 1月, 2016 4 次提交
-
-
由 Drew Blessing 提交于
-
由 Josh Frye 提交于
-
由 Josh Frye 提交于
-
由 Robert Speicher 提交于
This partially reverts 6a5cd3ca - we keep the migration and add a new migration that reverts it in order to keep migration history intact.
-
- 21 1月, 2016 1 次提交
-
-
由 Douwe Maan 提交于
-
- 20 1月, 2016 1 次提交
-
-
由 Tomasz Maczukin 提交于
-
- 19 1月, 2016 3 次提交
-
-
由 Douwe Maan 提交于
-
由 Yorick Peterse 提交于
This greatly improves the performance of Project#external_issue_tracker by moving most of the fields queried in Ruby to the database and letting the database handle all logic. Prior to this change the process of finding an external issue tracker was along the lines of the following: 1. Load all project services into memory. 2. Reduce the list to only services where "issue_tracker?" returns true 3. Reduce the list from step 2 to service where "default?" returns false 4. Find the first service where "activated?" returns true This has to two big problems: 1. Loading all services into memory only to reduce the list down to a single item later on is a waste of memory (and slow timing wise). 2. Calling Array#select followed by Array#reject followed by Array#find allocates extra objects when this really isn't needed. To work around this the following service fields have been moved to the database (instead of being hardcoded): * category * default This in turn means we can get the external issue tracker using the following query: SELECT * FROM services WHERE active IS TRUE AND default IS FALSE AND category = 'issue_tracker' AND project_id = XXX LIMIT 1 This coupled with memoizing the result (just as before this commit) greatly reduces the time it takes for Project#external_issue_tracker to complete. The exact reduction depends on one's environment, but locally the execution time is reduced from roughly 230 ms to only 2 ms (= a reduction of almost 180x). Fixes gitlab-org/gitlab-ce#10771
-
由 Jeroen Nijhof 提交于
-
- 15 1月, 2016 1 次提交
-
-
由 Kirilll Zaycev 提交于
-
- 14 1月, 2016 2 次提交
-
-
由 Grzegorz Bizon 提交于
Artifacts metadata field will be used to store a filename of gzipped file containing metadata definition for given artifacts archive.
-
由 Robert Speicher 提交于
-
- 13 1月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
-
- 07 1月, 2016 1 次提交
-
-
由 Yorick Peterse 提交于
InfluxDB over UDP doesn't use authentication, thus there's no need for these settings.
-
- 05 1月, 2016 1 次提交
-
-
由 Andriy Dyadyura 提交于
-
- 04 1月, 2016 1 次提交
-
-
由 Valery Sizov 提交于
-
- 29 12月, 2015 3 次提交
-
-
由 Yorick Peterse 提交于
This removes the need for Sidekiq and any overhead/problems introduced by TCP. There are a few things to take into account: 1. When writing data to InfluxDB you may still get an error if the server becomes unavailable during the write. Because of this we're catching all exceptions and just ignore them (for now). 2. Writing via UDP apparently requires the timestamp to be in nanoseconds. Without this data either isn't written properly. 3. Due to the restrictions on UDP buffer sizes we're writing metrics one by one, instead of writing all of them at once.
-
由 Gabriel Mazetto 提交于
-
由 Yorick Peterse 提交于
-
- 25 12月, 2015 2 次提交
-
-
由 Gabriel Mazetto 提交于
-
由 Gabriel Mazetto 提交于
-