- 23 Sep, 2016 2 commits
-
-
Ahmad Sherif authored
-
Ahmad Sherif authored
-
- 22 Sep, 2016 2 commits
-
-
Lin Jen-Shin authored
-
Lin Jen-Shin authored
Closes #22438
-
- 21 Sep, 2016 7 commits
-
-
Zeger-Jan van de Weg authored
-
Z.J. van de Weg authored
Closes gitlab-org/gitlab-ce#22330
-
Robert Speicher authored
-
Robert Speicher authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
- For target project show only environments for target branch or with tags - For source project show only environments for source branch
-
- 20 Sep, 2016 20 commits
-
-
Timothy Andrew authored
- Instead of overriding `create` and `update` in `MergeRequests::BaseService` - Get all merge request service specs passing
-
Timothy Andrew authored
- Don't use `TableReferences` - using `.arel_table` is shorter! - Move some database-related code to `Gitlab::Database` - Remove the `MergeRequest#issues_closed` and `Issue#closed_by_merge_requests` associations. They were either shadowing or were too similar to existing methods. They are not being used anywhere, so it's better to remove them to reduce confusion. - Use Rails 3-style validations - Index for `MergeRequest::Metrics#first_deployed_to_production_at` - Only include `CycleAnalyticsHelpers::TestGeneration` for specs that need it. - Other minor refactorings.
-
Robert Speicher authored
-
Robert Speicher authored
We were calling `.where` and `.send` on the relation, but never doing anything with the return value, resulting in proper access-level filtering never being of any consequence.
-
Robert Speicher authored
-
Dan Dunckel authored
-
Kamil Trzcinski authored
-
Timothy Andrew authored
And `scss_lint`
-
Timothy Andrew authored
- Move things common to `Issue` and `MergeRequest` into `Issuable` - Move more database-specific functions into `Gitlab::Database` - Indentation changes and other minor refactorings.
-
Lin Jen-Shin authored
However, if MergeRequest#all_commits_sha would want to handle non-persisted merge request, by judging its name, it should not just give 1 SHA, but all of them. But we don't really care all_commits_sha for non-persisted merge request anyway. So I think we should just ignore that case. Better to not implementing something than implementing it in a wrong and confusing way.
-
Timothy Andrew authored
-
Timothy Andrew authored
1. Change multiple updates to a single `update_all` 2. Use cascading deletes 3. Extract an average function for the database median. 4. Move database median to `lib/gitlab/database` 5. Use `delete_all` instead of `destroy_all` 6. Minor refactoring
-
Timothy Andrew authored
1. Dispatch between the two strategies automatically based on the current database type. 2. The MySQL version needs to run multiple statements, so the `cycle_analytics` model is modified to support this.
-
Timothy Andrew authored
1. Add indexes to `CreateMergeRequestsClosingIssues` columns. 2. Remove an extraneous `check_if_open` check that is redundant now. It would've been better to rebase this in, but that's not possible because more people are working on this branch.
-
Timothy Andrew authored
1. Look for merge requests (and issues that they close) that have been deployed to production in the last X days (where X is given by the `from` parameter). 2. Cycle analytics queries only operate on this fitered set of merge requests and issues.
-
Timothy Andrew authored
-
Timothy Andrew authored
-
Stan Hu authored
In https://gitlab.com/gitlab-org/gitlab-ce/builds/4218398, the build failed because the last_activity_at column was only being updated once per hour. We can fix this spec by stubbing out the throttling and adjusting the spec to test the right event timestamp.
-
- 19 Sep, 2016 9 commits
-
-
Dan Dunckel authored
-
Z.J. van de Weg authored
-
Z.J. van de Weg authored
-
Lin Jen-Shin authored
This way we could also show pipelines from commits which were discarded due to a force push.
-
Kamil Trzcinski authored
-
Yorick Peterse authored
The lock in turn is only obtained when actually needed, reducing some load on Redis. Fixes gitlab-org/gitlab-ce#22213
-
Kamil Trzcinski authored
This solves Pipelines in `running` after all stages do finish.
-
Kamil Trzcinski authored
-
Timothy Andrew authored
1. Add `summary` section. 2. `stats` is `null` if no stats are present. 3. `stats` and `summary` are both arrays.
-