| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Modified schema via migrations.
Added one-to-one relationship between the two models.
Added changelog file
|
|
|
|
|
|
| |
This change limits the number of emails
for new access requests notifications to
10 most recently active owners/maintainers
|
|
|
|
| |
Also change test URL sequest to .test TLD
|
| |
|
| |
|
|\
| |
| |
| |
| |
| |
| | |
'master'
Allow UsageData.count to use count_by:
See merge request gitlab-org/gitlab-ce!30770
|
| | |
|
|\ \
| | |
| | |
| | |
| | | |
Migrate legacy uploads rake tasks
See merge request gitlab-org/gitlab-ce!29409
|
| | |
| | |
| | |
| | |
| | | |
- move uploads created by AttachmentUploader
- handle also files created for legacy_diff_notes
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add `needs:` CI config option CE
Closes gitlab-ee#12334
See merge request gitlab-org/gitlab-ce!31346
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Ports changes from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/12343
|
| |/ /
|/| |
| | |
| | |
| | |
| | | |
- Adds UI to configure in group and project settings
- Removes notification configuration for users when
disabled at group or project level
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Creating new records has been disabled, and all
existing records been migrated to clusters as of
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28534
|
|\ \ \ \
| |/ / / |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
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.
|
| |\ \ \
| | |/ /
| |/| |
| | | |
| | | | |
Use stubbed key and certificate in Helm factory
See merge request gitlab-org/gitlab-ce!31169
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
We had a number of team members struggle to find invited members of a
group. Searching for the e-mail address did not work because search only
works with members with user accounts.
This commit changes two things:
1. Breaks out the invited members into a separate table.
2. Adds search capability for the invited members.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/61948
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3809
See merge request gitlab-org/gitlab-ce!31375
|
| |/ /
| | |
| | |
| | | |
Introducing Docker Registry replication
|
|/ /
| |
| |
| |
| |
| | |
This implements the support for `needs:` keyword
as part of GitLab CI. That makes some of the jobs
to be run out of order.
|
| |
| |
| |
| |
| | |
- the typo in this factory name was precluding us from properly
creating dynamic code to remove duplciation.
|
| |
| |
| |
| |
| | |
Adds Job specific variables to facilitate specifying variables when
running manual jobs.
|
| |
| |
| |
| |
| | |
Using the sed script from
https://gitlab.com/gitlab-org/gitlab-ce/issues/59758
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
A project can have the same `LfsObject` linked with up to three
`LfsObjectsProject` records. Each of these records would be for a
different repository, recorded in the `repository_type` property. The
different repositories at time of writing are "project", "wiki", and
"design". See https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894
This change exports the list of `repository_type`s as a JSON mapping of
oid => repository_types, which are imported to recreate the correct
`LfsObjectsProject` records.
https://gitlab.com/gitlab-org/gitlab-ee/issues/11090
|
|\ \
| | |
| | |
| | |
| | | |
Adds cluster_for_group factory for convenience
See merge request gitlab-org/gitlab-ce!30826
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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])
```
|
| |
| |
| |
| |
| | |
This validation prevents the domain from being saved from the UI
e.g. when user tries to enable Let's Encrypt integration
|
| |
| |
| |
| |
| |
| | |
- Migration updates existing groups to "owner", then sets default to
"maintainer" so that new groups will default to that
- Update spec examples
|
| |
| |
| |
| |
| |
| |
| | |
This setting is at the group level only. The default is specified to
be maintainers and owners.
**Specs only**, all failing.
|
| |
| |
| |
| |
| |
| | |
- Migration updates existing groups to "owner", then sets default to
"maintainer" so that new groups will default to that
- Update spec examples
|
| |
| |
| |
| |
| |
| |
| | |
This setting is at the group level only. The default is specified to
be maintainers and owners.
**Specs only**, all failing.
|
| |
| |
| |
| |
| |
| | |
- Migration updates existing groups to "owner", then sets default to
"maintainer" so that new groups will default to that
- Update spec examples
|
| |
| |
| |
| |
| |
| |
| | |
This setting is at the group level only. The default is specified to
be maintainers and owners.
**Specs only**, all failing.
|
| |
| |
| |
| |
| |
| | |
- Migration updates existing groups to "owner", then sets default to
"maintainer" so that new groups will default to that
- Update spec examples
|
| |
| |
| |
| |
| |
| |
| | |
This setting is at the group level only. The default is specified to
be maintainers and owners.
**Specs only**, all failing.
|
| |
| |
| |
| |
| |
| | |
- Migration updates existing groups to "owner", then sets default to
"maintainer" so that new groups will default to that
- Update spec examples
|
| |
| |
| |
| |
| |
| |
| | |
This setting is at the group level only. The default is specified to
be maintainers and owners.
**Specs only**, all failing.
|
| |
| |
| |
| |
| |
| | |
- Migration updates existing groups to "owner", then sets default to
"maintainer" so that new groups will default to that
- Update spec examples
|
|/
|
|
|
|
|
| |
This setting is at the group level only. The default is specified to
be maintainers and owners.
**Specs only**, all failing.
|
|
|
|
|
| |
Pages access level currently depends on project visibilty
which is ignored by factory, this commit fixes that
|
|
|
|
|
|
| |
- use predefined factories when creating
projects with services
- remove unnecessary arguments
|
|
|
|
|
|
| |
Partial CE backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10565
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
|
|
|
|
|
| |
- handling properties needs to be skipped when
creating test records in order to test the legacy
data
|
|
|
|
|
|
| |
Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at
|
|\
| |
| |
| |
| |
| |
| | |
Use title and description fields for issue trackers
Closes #63690
See merge request gitlab-org/gitlab-ce!30096
|
| |
| |
| |
| |
| | |
- instead of using properties
- backward compatibility has to be kept for now
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Add two new ActiveRecord models:
- RootNamespaceStoragestatistics will persist root namespace statistics
- NamespaceAggregationSchedule will save information when a new update
to the namespace statistics needs to be scheduled
- Inject into UpdateProjectStatistics concern a new callback that will
call an async job to insert a new row onto NamespaceAggregationSchedule
table
- When a new row is inserted a new job is scheduled. This job will
update call an specific service to update the statistics and after that
it will delete thee aggregated scheduled row
- The RefresherServices makes heavy use of arel to build composable
queries to update Namespace::RootStorageStatistics attributes.
- Add an extra worker to traverse pending rows on
NAmespace::AggregationSchedule table and schedule a worker for each one
of this rows.
- Add an extra worker to traverse pending rows on
NAmespace::AggregationSchedule table and schedule a worker for each one
of this rows
|
|\ \
| |/
|/|
| |
| | |
Tidy spec for API::ProjectClusters
See merge request gitlab-org/gitlab-ce!30154
|