- 17 Jul, 2015 22 commits
-
-
Stan Hu authored
Add support for destroying project milestones ### What does this MR do? This MR adds a "Remove" button to the project milestones page and the milestone page itself. ### Why was this MR needed? Because lots of people talked about needing to clean their toilets. :) ### What are the relevant issue numbers? Closes https://github.com/gitlabhq/gitlabhq/issues/1504 ### Screenshots ![image](https://gitlab.com/gitlab-org/gitlab-ce/uploads/ef8c7a3ea1db7b37cccae3869ac4de0a/image.png) ![image](https://gitlab.com/gitlab-org/gitlab-ce/uploads/33eb01c7bc30fb235de96db5efb8746d/image.png) See merge request !980
-
Dmitriy Zaporozhets authored
Validate format of project_url and token for GitLab CI service. If `project_url` and `token` for are invalid, [service_hook creation](https://gitlab.com/gitlab-org/gitlab-ce/blob/7-13-stable/app/models/project_services/gitlab_ci_service.rb#L30-34) will silently fail due to validation of URL in `WebHook`. Given that token is a sequence of numbers and letters for GitLab CI making sure that there are no unexpected characters should be enough to prevent service_hook being nil. Fixes #1997 See merge request !987
-
Dmitriy Zaporozhets authored
Avoid copy of strings in memory for parsing git grep result Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> See merge request !967
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Marin Jankovski authored
-
Dmitriy Zaporozhets authored
-
Dmitriy Zaporozhets authored
Advanced cache Fixes #1993 * Build missing cache values in background job after each push * Store commit_count in project table. Refresh in background job * moved repository size calculation in background job ## Advantages Every time push is triggered - we build cache for project even without user visiting project page. That means first visit is as fast as others now. This is especially good for active projects where people have some requests fast because of cache and some slow - because cache was build in their request. Between cache expired and cache built we we had gap when Linux repo can give 502 error because calculation commits count takes 30 seconds or even more. Using value from database fix this problem. Before cache is updated you see old value from database. After - you see new one. Basically this merge request is super win to GitLab. We don't do some heavy operations in user request but instead in background job. ## Temporary problem After this migration all projects will have `0` commits in database. It fill be replaced with real value on next push. I did not add recalculation to migration because it will last forever on big instances. Can be fixed by adding rake task which will go in background on live instance without downtime See merge request !986
-
Marin Jankovski authored
-
Valery Sizov authored
The release manager owns the stable branches I think this helps the release manager because it means they don't have to worry about others pushing commits at the last minute. See merge request !1907
-
Dmitriy Zaporozhets authored
Expire Rails cache entries after two weeks This should help prevent endless Redis growth. See merge request !1903
-
Jacob Vosmaer authored
I think this helps the release manager because it means they don't have to worry about others pushing commits at the last minute.
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Marin Jankovski authored
-
Stan Hu authored
Closes https://github.com/gitlabhq/gitlabhq/issues/1504
-
Marin Jankovski authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
-
Sytse Sijbrandij authored
-
Sytse Sijbrandij authored
-
Sytse Sijbrandij authored
-
- 16 Jul, 2015 8 commits
-
-
Job van der Voort authored
Added note about chef Added note about chef being required to generate GitLab config. because of tweet https://twitter.com/grahamgilbert/status/621015318442459136 See merge request !982
-
Job van der Voort authored
Added new doc about creating a new branch Added new document about creating a branch and fixed bullets in all the other documents. Also fixed "git push REMOTE BRANCH". See merge request !1894
-
karen Carias authored
-
karen Carias authored
-
Sytse Sijbrandij authored
Document should start from h1 title. Also put badges on top for easier tracking Looks much better with new project page design. See merge request !983
-
Dmitriy Zaporozhets authored
-
Marin Jankovski authored
-
Marin Jankovski authored
-
- 15 Jul, 2015 7 commits
-
-
karen Carias authored
-
karen Carias authored
-
Dmitriy Zaporozhets authored
Time ago fix for branch compare page https://dev.gitlab.org/gitlab/gitlabhq/issues/2508 See merge request !1904
-
Valery Sizov authored
-
Jacob Vosmaer authored
This should help prevent endless Redis growth.
-
Stan Hu authored
Remove author information from "post" in merge_requests API.
-
Stan Hu authored
api: expose work_in_progress flag See merge request !948
-
- 14 Jul, 2015 3 commits
-
-
Kamil Trzciński authored
Fix docker image See merge request !979
-
Kamil Trzcinski authored
-
Sytse Sijbrandij authored
-