Age | Commit message (Collapse) | Author | |
---|---|---|---|
2022-10-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-07-04 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-04-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-04-01 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-03-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2022-03-11 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-08-24 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-07-16 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-05-12 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-03-10 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2021-03-04 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-11-19 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-11-13 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-11-06 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-07-08 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-06-29 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-04-14 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-04-02 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-04-01 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-02-28 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2020-01-21 | Add latest changes from gitlab-org/gitlab@master | GitLab Bot | |
2019-08-30 | Remove :kubernetes_namespace_per_environment feature flag | Tiger | |
Feature flag has been defaulting to `true` since 12.2 | |||
2019-08-07 | Use separate Kubernetes namespaces per environment | Tiger Watson | |
Kubernetes deployments on new clusters will now have a separate namespace per project environment, instead of sharing a single namespace for the project. Behaviour of existing clusters is unchanged. All new functionality is controlled by the :kubernetes_namespace_per_environment feature flag, which is safe to enable/disable at any time. | |||
2019-07-25 | Add frozen_string_literal to spec/support | Thong Kuah | |
Using the sed script from https://gitlab.com/gitlab-org/gitlab-ce/issues/59758 | |||
2019-04-23 | Upgrade Rails to 5.1.6.1 | Jasper Maes | |
Model.new.attributes now also returns encrypted attributes. | |||
2018-12-15 | Passing the separator argument as a positional parameter is deprecated | Jasper Maes | |
2018-10-22 | Revert "Merge branch 'refactor-cluster-create-service-spec' into 'master'" | Thong Kuah | |
This reverts merge request !22407 | |||
2018-10-17 | Move shared examples into the only file where used | Thong Kuah | |
This will make it easier to perform in place adjustments, etc for future MRs involving group clusters. | |||
2018-10-04 | Remove `rbac_clusters` feature flag | Thong Kuah | |
Now that Auto DevOps can run in a RBAC enabled cluster from https://gitlab.com/gitlab-org/gitlab-ce/issues/51942, we can now remove the FF. As the flag only governed if UI elements would appear or not when creating/adding existing clusters; the effect of removing the FF would be that the checkbox to choose to enable RBAC clusters will now always appear. Remove FF stubs from specs Improve spec context names | |||
2018-09-14 | Address BE review - re-arrange some specs | Thong Kuah | |
2018-09-14 | Add FE option for users to choose to create a fully RBAC-enabled cluster or not. | Thong Kuah | |
This is similar to the option in the Add Existing cluster form | |||
2018-09-14 | Create a GKE cluster with legacy_abac disabled when the `:rbac_clusters` ↵ | Thong Kuah | |
feature flag is enabled Explicitly persist the legacy_abac value of the cluster_provider_gcp so that we can disable abac if the `:rbac_clusters` feature flag is enabled | |||
2018-07-11 | Resolve "Rename the `Master` role to `Maintainer`" Backend | Mark Chao | |
2018-05-13 | Extract shared components from Clusters::CreateService spec | Matija Čupić | |
2018-05-08 | Cleanly handle plural name for ghost user migration | Olivier Gonzalez | |
2017-12-22 | Replace '.team << [user, role]' with 'add_role(user)' in specs | blackst0ne | |
2017-08-03 | Change all `:empty_project` to `:project` | Robert Speicher | |
2017-08-01 | Ensure all project factories use `:repository` trait or `:empty_project` | Robert Speicher | |
2017-07-19 | Use Ghost user when edited_by, merged_by deleted | Jarka Kadlecova | |
2017-06-15 | Rename "Slash commands" to "Quick actions" | Eric Eastwood | |
Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/27070 Deprecate "chat commands" in favor of "slash commands" We looked for things like: - `slash commmand` - `slash_command` - `slash-command` - `SlashCommand` | |||
2017-06-14 | Correct RSpec/SingleLineHook cop offenses | Robert Speicher | |
2017-05-04 | Backport of multiple_assignees_feature [ci skip] | Valery Sizov | |
2017-04-24 | Move records to the ghost user in a transaction. | Timothy Andrew | |
- While deleting a user, some of the user's associated records are moved to the ghost user so they aren't deleted. The user is blocked before these records are moved, to prevent the user from creating new records while the migration is happening, and so preventing a data race. - Previously, if the migration failed, the user would _remain_ blocked, which is not the expected behavior. On the other hand, we can't just stick the block + migration into a transaction, because we want the block to be committed before the migration starts (for the data race reason mentioned above). - One solution (implemented in this commit) is to block the user in a parent transaction, migrate the associated records in a nested sub-transaction, and then unblock the user in the parent transaction if the sub-transaction fails. | |||
2017-04-06 | Implement review comments from @DouweM for !10467. | Timothy Andrew | |
1. Have `MigrateToGhostUser` be a service rather than a mixed-in module, to keep things explicit. Specs testing the behavior of this class are moved into a separate service spec file. 2. Add a `user.reported_abuse_reports` association to make the `migrate_abuse_reports` method more consistent with the other `migrate_` methods. | |||
2017-04-06 | Move a user's award emoji to the ghost user | Timothy Andrew | |
... when the user is destroyed. 1. Normally, for a given awardable and award emoji name, a user is only allowed to create a single award emoji. 2. This validation needs to be removed for ghost users, since: - User A and User B have created award emoji - with the same name and against the same awardable - User A is deleted. Their award emoji is moved to the ghost user - User B is deleted. Their award emoji needs to be moved to the ghost user. However, this breaks the uniqueness validation, since the ghost user is only allowed to have one award emoji of a given name for a given awardable | |||
2017-04-06 | Move a user's notes to the ghost user | Timothy Andrew | |
... when the user is destroyed. | |||
2017-04-06 | Move a user's merge requests to the ghost user. | Timothy Andrew | |
1. When the user is deleted. 2. Refactor out code relating to "migrating records to the ghost user" into a `MigrateToGhostUser` concern, which is tested using a shared example. | |||
2017-04-03 | Don't use FFaker in factories, use sequences instead | Rémy Coutable | |
FFaker can generate data that randomly break our test suite. This simplifies our factories and use sequences which are more predictive. Signed-off-by: Rémy Coutable <remy@rymai.me> | |||
2017-03-28 | Use `:empty_project` where possible in service specs | Robert Speicher | |
2017-02-23 | Enable Style/SpaceInsideBrackets | Douwe Maan | |