summaryrefslogtreecommitdiff
path: root/app/controllers/projects
Commit message (Collapse)AuthorAgeFilesLines
* Add Pipelines for CommitKamil Trzcinski2016-09-271-8/+9
|
* Fix IssuesController#show degradation including project on loaded notesincludes-projects-to-render-issue-notesPaco Guzman2016-09-271-1/+1
|
* Revert part of "Merge branch 'update_issues_mr_counter' into 'master'Rémy Coutable2016-09-222-4/+0
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Merge branch 'and-you-get-awards' into 'master' Rémy Coutable2016-09-211-1/+4
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | And Snippets get awards ## What does this MR do? Makes snippets more awesome, by making them awardables ## Why was this MR needed? Because Snippets were left behind. ## What are the relevant issue numbers? Closes #17878 See merge request !4456
| * Start Frontend work, fix routing problemZ.J. van de Weg2016-09-191-1/+4
| |
* | Merge branch 'post-merge-improve-of-ci-permissions' into 'master' Rémy Coutable2016-09-211-3/+3
|\ \ | | | | | | | | | | | | | | | | | | Post-merge improve of CI permissions Improves code from !6409 See merge request !6432
| * | Post-merge improve of CI permissionsKamil Trzcinski2016-09-201-3/+3
| | |
* | | Merge branch '21170-cycle-analytics' into 'master' Stan Hu2016-09-211-0/+67
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cycle Analytics: first iteration ## What does this MR do? - Implement the first iteration of the "Cycle Analytics" feature. ## What are the relevant issue numbers? - Closes #21170 ## Screenshots ![cycle_analytics_screencast.gif](/uploads/d23c3c912caa6935fd47b53ca3a56b97/cycle_analytics.gif) ## Backend Tasks - [x] Implementation - [x] Phases - [x] Issue (Tracker) - [x] Plan (Board) - [x] Code (IDE) - [x] Test (CI) - [x] Review (MR) - [x] Staging (CD) - [x] Production (Total) - [x] Make heuristics more modular - [x] Scope to project - [x] Date range (30 days, 90 days) - [x] Access restriction - [x] Test - [x] Find a better way to test these phases - [x] Phases - [x] Issue (Tracker) - [x] Plan (Board) - [x] Code (IDE) - [x] Test (CI) - [x] Review (MR) - [x] Staging (CD) - [x] Production (Total) - [x] Test for "end case happens before start case" - [x] Consolidate helper - [x] Miniboss review - [x] Performance testing with mock data - [x] Improve performance - [x] Pre-calculate "merge requests closing issues - [x] Pre-calculate everything else - [x] Test performance against 10k issues - [x] Test all pre-calculation code - [x] Ci::Pipeline -> build start/finish - [x] Ci::Pipeline#merge_requests - [x] Issue -> record default metrics after save - [x] MergeRequest -> record default metrics after save - [x] Deployment -> Update "first_deployed_to_production_at" for MR metrics - [x] Git Push -> Update "first commit mention" for issue metrics - [x] Merge request create/update/refresh -> Update "merge requests closing issues" - [x] Remove `MergeRequestsClosingIssues` when necessary - [x] Changes to unblock Fatih - [x] Add summary data - [x] `stats` should be array - [x] Let `stats` be `null` if all `stats` are null - [x] Indexes for "merge requests closing issues" - [x] Test summary data - [x] Scope everything to project - [x] Find out why tests were passing - [x] Filter should include issues/MRs which have made it to production within the range - [x] Don't create duplicate `MergeRequestsClosingIssues` - [x] Fix tests - [x] MySQL median - [x] Assign to Douwe for review - [x] Fix conflicts - [x] Implement suggestions from Yorick's review - [x] Test on PG - [x] Test on MySQL - [x] Refactor - [x] Cleanup - [x] What happens if we have no data at all? - [x] Extract common queries to methods / scopes - [x] Remove unused queries - [x] Downtime for foreign key migrations - [x] Find a way around "if issue.metrics.present?" all over the place - [x] Find a way around "if merge_request.metrics.present?" all over the place - [x] Test migrations on a fresh database - [x] MySQL - [x] Pg - [x] Access issues - While the project is public and the visibility is set to "Everyone with access", you cannot visit the cycle analytics page when signed out. - [x] CHANGELOG - [x] Implement suggestions from Douwe's review - [x] First set of comments - [x] Second set of comments - [x] Third set of comments - [x] Fourth set of comments - [x] Make sure build is green - [ ] Make issue for "polish" - [ ] EE MR See merge request !5986
| * | | Implement fourth round of comments from @DouweM.Timothy Andrew2016-09-211-3/+8
| | | | | | | | | | | | | | | | | | | | | | | | - Pluralize summary titles - Remove the `run_query` method - always return sql strings from the `date_time_sql` methods
| * | | Move JSON generation (cycle analytics) into a controller method.Timothy Andrew2016-09-201-2/+34
| | | | | | | | | | | | | | | | Helper methods are meant for views
| * | | Merge remote-tracking branch 'origin/master' into 21170-cycle-analyticsTimothy Andrew2016-09-208-74/+100
| |\ \ \ | | | |/ | | |/|
| * | | Move cycle analytics JSON generation to a helper.Timothy Andrew2016-09-171-1/+3
| | | | | | | | | | | | | | | | | | | | 1. Use a new format, with each stage having a `title`, `description`, and `value.
| * | | Add a JSON version of the `CycleAnalytics` page.Timothy Andrew2016-09-081-0/+5
| | | |
| * | | Merge remote-tracking branch 'origin/master' into 21170-cycle-analyticsTimothy Andrew2016-09-0713-27/+64
| |\ \ \
| * | | | Authorize access to cycle analytics.Timothy Andrew2016-08-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | All users with "Reporter" access (and above) to a project can see the Cycle Analytics page.
| * | | | Fetch cycle analytics data for a specific date range.Timothy Andrew2016-08-261-1/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Supported date ranges are 30 / 90 days ago. The default is 90 days ago. 2. All issues created before "x days ago" are filtered out, even if they have other related data (test runs, merge requests) within the filter range.
| * | | | Scope Cycle Analytics queries to a projectTimothy Andrew2016-08-261-1/+1
| | | | |
| * | | | Add the "Plan" Cycle Analytics query.Timothy Andrew2016-08-261-28/+1
| | | | | | | | | | | | | | | | | | | | | | | | | 1. Move from raw SQL to ActiveRecord. 2. Add a non-persisted `CycleAnalytics` model to store all the queries.
| * | | | Display numbers for the "Issue (Tracker)" cycle analytics metric.Timothy Andrew2016-08-261-0/+32
| | | | | | | | | | | | | | | | | | | | 1. Code is messy and untested, but it is a start.
* | | | | fix issues mr counterbarthc2016-09-202-20/+5
| |_|_|/ |/| | |
* | | | Move logic to check ci? or lfs_deploy_token? to Gitlab::Auth::ResultKamil Trzcinski2016-09-201-7/+3
| | | |
* | | | Revert "Revert all changes introduced by ↵lfs-supportKamil Trzcinski2016-09-191-0/+6
| |_|/ |/| | | | | | | | | | | | | | https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6043" This reverts commit 6d43c95b7011ec7ec4600e00bdc8df76bb39813c.
* | | Revert all changes introduced by ↵Kamil Trzcinski2016-09-191-6/+0
| | | | | | | | | | | | https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/6043
* | | Merge branch 'master' into per-build-tokenKamil Trzcinski2016-09-192-1/+5
|\ \ \
| * | | Render invalid template for merge requests without source project and openKatarzyna Kobierska2016-09-161-0/+4
| | | |
| * | | Fix spelling: sucessfully -> successfullyStan Hu2016-09-151-1/+1
| | | | | | | | | | | | | | | | Originally from gitlab-org/gitlab-ee!682
* | | | Don't leak build tokens in build logsKamil Trzcinski2016-09-191-1/+5
| | | |
* | | | Improve authentication_result usageKamil Trzcinski2016-09-161-11/+18
| | | |
* | | | Simplify checking of allowed abilities in git_http_client_controllerKamil Trzcinski2016-09-161-42/+33
| | | |
* | | | Rename capabilities to authentication_abilitiesKamil Trzcinski2016-09-162-7/+9
| | | |
* | | | Added builds_spec and git_http_specsKamil Trzcinski2016-09-151-1/+1
| | | |
* | | | Merge remote-tracking branch 'origin/lfs-support-for-ssh' into per-build-tokenKamil Trzcinski2016-09-151-22/+49
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | # Conflicts: # app/controllers/projects/git_http_client_controller.rb # app/helpers/lfs_helper.rb # lib/gitlab/auth.rb # spec/requests/lfs_http_spec.rb
| * | | | Refactored authentication code to make it a bit clearer, added test for ↵Patricio Cano2016-09-151-8/+17
| | | | | | | | | | | | | | | | | | | | wrong SSH key.
| * | | | Further refactoring of authentication code, and code style fixes.Patricio Cano2016-09-151-8/+12
| | | | |
| * | | | Use special characters for `lfs+deploy-key` to prevent a someone from ↵Patricio Cano2016-09-151-2/+2
| | | | | | | | | | | | | | | | | | | | creating a user with this username, and method name refactoring.
| * | | | Better authentication handling, syntax fixes and better actor handling for ↵Patricio Cano2016-09-151-14/+13
| | | | | | | | | | | | | | | | | | | | LFS Tokens
| * | | | Refactor LFS token logic to use a Redis key instead of a DB field, making it ↵Patricio Cano2016-09-151-2/+1
| | | | | | | | | | | | | | | | | | | | a 1 use only token.
| * | | | Added LFS support to SSHPatricio Cano2016-09-151-12/+30
| |/ / / | | | | | | | | | | | | - Required on the GitLab Rails side is mostly authentication and API related.
* | | | Fix most of specsKamil Trzcinski2016-09-151-2/+5
| | | |
* | | | Fix existing authorization specsKamil Trzcinski2016-09-151-1/+1
| | | |
* | | | Merge remote-tracking branch 'origin/master' into per-build-tokenKamil Trzcinski2016-09-152-12/+4
|\ \ \ \ | |/ / / | | | | | | | | | | | | # Conflicts: # db/schema.rb
| * | | Add test checking method closed_without_source_projectKatarzyna Kobierska2016-09-131-6/+0
| | | |
| * | | Checks if deleting forked project closed all open merge requestsKatarzyna Kobierska2016-09-131-2/+2
| | | |
| * | | fixes distinction between renaming a file and updating its content and21092-file-execution-flag-is-not-preserved-when-editing-filestiagonbotelho2016-09-091-6/+4
| | | | | | | | | | | | | | | | refactors update file
* | | | Make result to return project and capabilities grantedKamil Trzcinski2016-09-132-9/+5
| | | |
* | | | Use a permissions of user to access all dependent projects from CI jobs ↵Kamil Trzcinski2016-09-132-2/+12
|/ / / | | | | | | | | | (this also includes a container images, and in future LFS files)
* | | Merge branch 'gitlab-workhorse-safeties' into 'master' Jacob Vosmaer (GitLab)2016-09-093-8/+10
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Security and safety improvements for gitlab-workhorse integration Companion to https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/60 - Use a custom content type when sending data to gitlab-workhorse - Verify (using JWT and a shared secret on disk) that internal API requests came from gitlab-workhorse This will allow us to build features in gitlab-workhorse that require more trust, and protect us against programming mistakes in the future. This is designed so that no action is required for installations from source. For omnibus-gitlab we need to add code that manages the shared secret. See merge request !5907
| * | | Verify JWT messages from gitlab-workhorseJacob Vosmaer2016-09-053-8/+10
| | | |
* | | | Merge branch 'dz-bulk-edit-mr' into 'master' Rémy Coutable2016-09-081-26/+0
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add bulk update support for merge requests list ## What does this MR do? Adds new feature: ability to update multiple merge requests at once from index page (same like we have for issues already) ## Are there points in the code the reviewer needs to double check? I don't think so ## Why was this MR needed? * consistency with issues * save user time when you want set same label/milestone to 20 merge requests ## Screenshots (if relevant) ![Screenshot_2016-09-08_11.48.49](/uploads/fe50b2472330e211eb8d6d6dafb15667/Screenshot_2016-09-08_11.48.49.png)![Screenshot_2016-09-08_11.48.46](/uploads/4833c3705120ec028f7a62a4e128998d/Screenshot_2016-09-08_11.48.46.png) ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [x] ~~[Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)~~ - [x] ~~API support added~~ - Tests - [x] Added for this feature/bug - [x] All builds are passing - [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html) - [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [x] Branch has no merge conflicts with `master` (if you do - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/20087 See merge request !6226
| * | | | Add bulk update support for merge requests listDmitriy Zaporozhets2016-09-081-26/+0
| | | | | | | | | | | | | | | | | | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
View Lorry Controller Status