summaryrefslogtreecommitdiff
path: root/spec/models
Commit message (Collapse)AuthorAgeFilesLines
* Further remove code branches by database typeAndreas Brandl2019-07-291-5/+1
| | | | | | | | We dropped MySQL support and a lot of mysql specific code has been removed in https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/29608. This comes in from the other direction and removes any `if postgresql?` branches.
* Add Job specific variablesMatija Čupić2019-07-292-1/+24
| | | | | Adds Job specific variables to facilitate specifying variables when running manual jobs.
* Merge branch '32495-improve-slack-notification-on-pipeline-status' into 'master'Robert Speicher2019-07-262-87/+400
|\ | | | | | | | | | | | | Make pipeline failure Slack notifications prettier and more informative Closes #32495 See merge request gitlab-org/gitlab-ce!27683
| * Improve pipeline status Slack notifications32495-improve-slack-notification-on-pipeline-statusNathan Friend2019-07-252-87/+400
| | | | | | | | | | | | This commit adds some formatting to the Slack notifications for pipeline statuses, as well as adds information about the stage and jobs that failed in the case of pipeline failure.
* | Merge branch 'remove-nested-groups-checks' into 'master'Lin Jen-Shin2019-07-2616-81/+65
|\ \ | | | | | | | | | | | | | | | | | | Remove code related to object hierarchy and MySQL Closes #65056 and #65055 See merge request gitlab-org/gitlab-ce!31095
| * | Remove code related to object hierarchy in MySQLremove-nested-groups-checksHeinrich Lee Yu2019-07-2516-81/+65
| | | | | | | | | | | | | | | These are not required because MySQL is not supported anymore
* | | Merge branch 'mc/feature/find-all-artifacts-for-sha' into 'master'Robert Speicher2019-07-262-53/+37
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Find build by sha from ref Closes #64534 and #45697 See merge request gitlab-org/gitlab-ce!30843
| * | | Extract common spec elements to shared_examplesmc/feature/find-all-artifacts-for-shaMatija Čupić2019-07-261-92/+8
| | | |
| * | | Rename latest_successful to be more explicitMatija Čupić2019-07-262-16/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * Reword Project#latest_successful_build_for to Project#latest_successful_build_for_ref * Reword Ci::Pipeline#latest_successful_for to Ci::Pipeline#latest_successful_build_for_ref
| * | | Add specs for latest_successful methods for SHAsMatija Čupić2019-07-232-0/+68
| | | |
* | | | Merge branch 'remove_deployment_metrics_deployment_platform_fallback' into ↵Kamil Trzciński2019-07-261-12/+0
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 'master' Remove fallback to deployment_platform_cluster in `DeploymentMetrics` See merge request gitlab-org/gitlab-ce!31126
| * | | | Removes potentially incorrect, and slow fallbackremove_deployment_metrics_deployment_platform_fallbackThong Kuah2019-07-251-12/+0
| | |_|/ | |/| | | | | | | | | | | | | | | | | | | | | | Deployment_platform is relatively expensive and calling this after the fact means that this may not be the cluster that was deployed to. Correspondingly reduce the leeway given in the related N+1 spec
* | | | Merge branch 'sh-support-docker-oci-images' into 'master'Dmitriy Zaporozhets2019-07-251-1/+1
|\ \ \ \ | |_|_|/ |/| | | | | | | | | | | | | | | | | | | Support Docker OCI images Closes gitlab-ee#12877 and #58685 See merge request gitlab-org/gitlab-ce!31127
| * | | Support Docker OCI imagessh-support-docker-oci-imagesStan Hu2019-07-251-1/+1
| |/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Docker Distribution v2.7.0 shipped with OCI support, but our container registry client was not updated to handle the manifest format in the HTTP `Accept` header. As a result, API calls to retrieve a manifest would return with an error, "OCI manifest found, but accept header does not support OCI manifests". This would result in blank fields in the container registry page and prevent tags from being deleted. To fix this, we just need to add `application/vnd.oci.image.manifest.v1+json` to the `Accept` header and configure Faraday to parse the response as JSON. The response structure is the same as the standard Docker Distribution V2 manifest. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/58685 Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/12877
* | | Merge branch 'make-relative-positioning-module-reusable' into 'master'Bob Van Landuyt2019-07-252-242/+8
|\ \ \ | |/ / |/| | | | | | | | Make RelativePositioning reusable See merge request gitlab-org/gitlab-ce!30993
| * | Make RelativePositioning reusablemake-relative-positioning-module-reusableAdam Hegyi2019-07-242-242/+8
| | | | | | | | | | | | | | | | | | | | | | | | RelativePositioning module was heavily dependent on the Issue model. This changes makes it easier to reuse the functionality provided by RelativePositioning in other models. Needed by: https://gitlab.com/gitlab-org/gitlab-ee/issues/12196
* | | Merge branch '63730-fix-500-status-labels-pd' into 'master'Robert Speicher2019-07-241-0/+13
|\ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Add where condition to filter out labels with type here Closes #63730 See merge request gitlab-org/gitlab-ce!30885
| * | | Add where condition to filter out invalid labels with nil type63730-fix-500-status-labels-pdPatrick Derichs2019-07-241-0/+13
| | | |
* | | | Merge branch '62128-remove-ignore-rule-for-project-auto-devops-domain' into ↵Douwe Maan2019-07-241-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 'master' Remove ignore rule for ProjectAutoDevops#domain See merge request gitlab-org/gitlab-ce!30989
| * | | | Remove ignore rule for ProjectAutoDevops#domain62128-remove-ignore-rule-for-project-auto-devops-domainTiger2019-07-221-1/+1
| | | | |
* | | | | Merge branch 'optimise-import-performance' into 'master'Stan Hu2019-07-241-4/+1
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Optimise import performance Closes #64924 See merge request gitlab-org/gitlab-ce!31045
| * | | | | Optimise import performanceoptimise-import-performanceKamil Trzciński2019-07-241-4/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Fix `O(n)` complexity of `append_or_update_attribute`, we append objects to an array and re-save project - Remove the usage of `keys.include?` as it performs `O(n)` search, instead use `.has_key?` - Remove the usage of `.keys.first` as it performs a copy of all keys, instead use `.first.first`
* | | | | | [ADD] outbound requests whitelistReuben Pereira2019-07-241-0/+11
| |_|_|/ / |/| | | | | | | | | | | | | | Signed-off-by: Istvan szalai <istvan.szalai@savoirfairelinux.com>
* | | | | Prefer `flat_map` over `map` + `flatten` in specsPeter Leitzen2019-07-241-2/+1
| |_|/ / |/| | | | | | | | | | | | | | | Although `flat_map` is equivalent to `map` + `flatten(1)` (note the level 1) we can apply this same refactoring to all cases.
* | | | Remove dead MySQL codeNick Thomas2019-07-231-21/+6
| |_|/ |/| | | | | | | | None of this code can be reached any more, so it can all be removed
* | | Merge branch 'bvl-mark-remote-mirrors-as-failed-sooner' into 'master'Robert Speicher2019-07-231-3/+12
|\ \ \ | | | | | | | | | | | | | | | | Mark mirrors as failed 1 hour after they started See merge request gitlab-org/gitlab-ce!30999
| * | | Mark mirrors as failed 1 hour after they startedBob Van Landuyt2019-07-231-3/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We call `Project#mark_stuck_remote_mirrors_as_failed!` from the `Git::BaseHooksService`. So that gets called every time we push tags or branches. Before this would only mark started mirrors as failed if they had been started 24 hours ago. A push would never take 24 hours, especially not when we run it so often. Lowering that threshold 1 hour should at least allow us to retry broken mirrors more often on pushes. The timeout for the initial push is set somewhat longer to accommodate for pushing large repos. Both numbers are currently picked arbitrarily.
* | | | Merge branch 'safe-archiving-for-traces' into 'master'Kamil Trzciński2019-07-232-0/+53
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Extra logging for new live trace architecture See merge request gitlab-org/gitlab-ce!30892
| * | | | Validate the existence of archived traces before removing live tracesafe-archiving-for-tracesShinya Maeda2019-07-232-0/+53
| | |/ / | |/| | | | | | | | | | | | | | Often live traces are removed even though the archived trace doesn't exist. This commit checkes the existence strictly.
* | | | Merge branch 'sh-use-shared-state-cluster-pubsub' into 'master'Kamil Trzciński2019-07-231-2/+2
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Use persistent Redis cluster for Workhorse pub/sub notifications See merge request gitlab-org/gitlab-ce!30990
| * | | | Use persistent Redis cluster for Workhorse pub/sub notificationssh-use-shared-state-cluster-pubsubStan Hu2019-07-221-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, in Omnibus, Workhorse expected to listen via the Redis shared state cluster for the `workhorse:notifications` publish/subscribe channel, but the Rails code was using the Sidekiq queue cluster for this. To fix this inconsistency, we make the Rails code use the persistent cluster, since we don't want Workhorse to be looking at anything Sidekiq-related.
* | | | | Merge branch '63485-fix-pipeline-emails-to-use-group-setting' into 'master'Nick Thomas2019-07-232-0/+70
|\ \ \ \ \ | |_|_|/ / |/| | | | | | | | | | | | | | | | | | | | | | | | Make pipeline emails respect group email setting Closes #63485 See merge request gitlab-org/gitlab-ce!30907
| * | | | Make pipeline emails respect group email setting63485-fix-pipeline-emails-to-use-group-settingHeinrich Lee Yu2019-07-232-0/+70
| | |/ / | |/| | | | | | | | | | | | | | When a user's notification email is set for a group, we should use that for pipeline emails
* | | | Merge branch 'if-64257-active_session_lookup_key_cleanup' into 'master'Bob Van Landuyt2019-07-231-1/+1
|\ \ \ \ | | | | | | | | | | | | | | | | | | | | Rake task to cleanup expired ActiveSession lookup keys See merge request gitlab-org/gitlab-ce!30668
| * | | | Rake task to cleanup expired ActiveSession lookup keysif-64257-active_session_lookup_key_cleanupImre Farkas2019-07-221-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In some cases ActiveSession.cleanup was not called after authentication, so for some user ActiveSession lookup keys grew without ever cleaning up. This Rake task manually iterates over the lookup keys and removes ones without existing ActiveSession.
* | | | | Merge branch 'gsemet/gitlab-ce-gsemet-master-patch-33258' into 'master'Sean McGivern2019-07-231-0/+20
|\ \ \ \ \ | |_|/ / / |/| | | | | | | | | | | | | | Multiple pipeline support for Build status See merge request gitlab-org/gitlab-ce!30828
| * | | | Add specs for specifying pipeline behaviorMatija Čupić2019-07-231-0/+20
| | | | | | | | | | | | | | | | | | | | | | | | | Adds specs for testing the new behavior of specifying a pipeline when POSTing a status.
* | | | | Merge branch 'group_with_cluster_factory' into 'master'Robert Speicher2019-07-221-6/+4
|\ \ \ \ \ | |_|_|/ / |/| | | | | | | | | | | | | | Adds cluster_for_group factory for convenience See merge request gitlab-org/gitlab-ce!30826
| * | | | Adds cluster_for_group factory for convienencegroup_with_cluster_factoryThong Kuah2019-07-191-6/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Also means we don't have to resort to an update statement to set parent for child groups who also have clusters. This is much shorter than ``` create(:cluster, :provided_by_gcp, :group, groups: [group]) ```
* | | | | Validate certificate chain only if it's changedVladimir Shushlin2019-07-221-0/+24
| | | | | | | | | | | | | | | | | | | | | | | | | This validation prevents the domain from being saved from the UI e.g. when user tries to enable Let's Encrypt integration
* | | | | Merge branch 'maintainers-can-create-subgroup' into 'master'Sean McGivern2019-07-221-0/+7
|\ \ \ \ \ | | | | | | | | | | | | | | | | | | | | | | | | Add a group setting to allow Maintainers to create sub-groups See merge request gitlab-org/gitlab-ce!29718
| * | | | | Make subgroup_creation_level default to maintainer at SQL levelFabio Papa2019-07-191-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Migration updates existing groups to "owner", then sets default to "maintainer" so that new groups will default to that - Update spec examples
| * | | | | Make maintainers the default setting for creating subgroupsFabio Papa2019-07-191-0/+8
| | | | | |
| * | | | | Remove an example that is no longer necessaryFabio Papa2019-07-191-9/+0
| | | | | |
| * | | | | Style rules; Revert some examplesFabio Papa2019-07-191-2/+4
| | | | | |
| * | | | | Make subgroup_creation_level default to maintainer at SQL levelFabio Papa2019-07-191-3/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - Migration updates existing groups to "owner", then sets default to "maintainer" so that new groups will default to that - Update spec examples
| * | | | | Make maintainers the default setting for creating subgroupsFabio Papa2019-07-191-0/+8
| | | | | |
| * | | | | Remove an example that is no longer necessaryFabio Papa2019-07-191-9/+0
| | | | | |
| * | | | | Style rules; Revert some examplesFabio Papa2019-07-191-1/+2
| | | | | |
| * | | | | Add examples specing the setting to choose who can create subgroupsFabio Papa2019-07-191-0/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This setting is at the group level only. The default is specified to be maintainers and owners. **Specs only**, all failing.
View Lorry Controller Status