To increase the bounds between Model experiments and model registry,
and reduce conflicts when migrating model experiments into model
registry later on, we are forcing the creation of a new experiment when
creating a new model, instead of reusing an existing one with the same
in case it exists. The new experiment also clearly states it belongs to
a model in its name.

iAlso updates services to use ServiceResponse, and deletes
FindOrCreateModelService that wasn't being used anywhere.

- Add spec for supports_canceling?
- Fix pipeline feature spec and add an example
- Fix merge train auto merge service spec
- Consider a build retryable if canceling since
users should not need to wait for the after_script
to run to retry
- Fix cancel pipeline service spec
- Fix the cancel redundant pipelines service spec
- Fix create pipeline service spec
- Fix cancel redundant pipelines worker spec
Fix 2 more specs:
- spec/models/environment_spec.rb
- spec/workers/ci/cancel_pipeline_worker_spec.rb

This is a step towards the feature of supporting the GitLab for Slack
app integration to be configured at group and instance-level.

https://gitlab.com/gitlab-org/gitlab/-/issues/391526

This change adds services and controller support for group-level and
instance-level Slack app installation via OAuth with Slack.

The changes are hidden behind a feature flag.

Changelog: fixed

This commit introduces instrumentation for exclusive locks within the
modules `Gitlab::ExclusiveLeaseGuard` and
`Gitlab::ExclusiveLeaseHelpers`, enabling better monitoring and
visibility into lock usage.

When utilizing the `Gitlab::ExclusiveLeaseHelpers#in_lock` method, the
following metrics are now tracked:
- exclusive_lock_count`
- exclusive_lock_wait_duration_s
- exclusive_lock_hold_duration_s

Similarly, when using the
`Gitlab::ExclusiveLeaseHelpers#try_obtain_lease` method, the following
metrics are captured:
- exclusive_lock_count
- exclusive_lock_hold_duration_s

Notably, in the latter method, `exclusive_lock_wait_duration_s` is not
captured as the method returns immediately if the lease is already held,
thus no waiting time is incurred.

Fetch group level work items from WorkItemsFinder
instead of IssuesFinder.

In the EE version there are custom branch rules which need to be treated
differently. The branch rule service classes have a common pattern which
detects which type of branch rule is currently being passed.

This change extracts that logic into the base service and then calls 4
methods

1. `authorized?` -> handle authorization for the service
2. `execute_on_branch_rule` -> logic for `Projects::BranchRule`
3. `execute_on_all_branches_rule` -> logic for `Projects::AllBranchesRule`
4. `execute_on_all_protected_branches_rule` -> logic for `Projects::AllProtectedBranchesRule`

This should simplify the logic for each child service.

- Fixing the wrong usage of
  shared example 'returning an error service response',
  see https://gitlab.com/gitlab-community/gitlab/-/blob/fdf61409f4e8ad44118cd82e987ad76045ef37a6/spec/support/shared_examples/services/service_response_shared_examples.rb#L3
- Currently in the test file `Pypi::CreatePackageService`,
  the assertion is ignored because the param `:message`
  is passed in the wrong way

Changelog: other

- Using the existing shared examples for service response to avoid code duplication

Changelog: other

It was already enabled by default in 16.9.

related to https://gitlab.com/gitlab-org/gitlab/-/issues/434676

Changelog: other

MR: gitlab.com/gitlab-org/gitlab/-/merge_requests/144729

This service handles changes to BranchRule objects.
The EE version returns errors if a custom branch rule is passed.

Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/144630

Before QuickActions::InterpretService would only be
able to handle project level entities. Now that
Issues/WorkItems can exist at the group level,
Issuable related commands need a container group to
scope queries like the one from the LabelFinder

Changelog: added

Changelog: other

https://gitlab.com/gitlab-org/gitlab/-/issues/429557

This reverts merge request !142037

This quick action removes a work item as a child to the current work
item.

Changelog: added

This MR sets up validation for semantic versioning when releasing a new
vesion of the catalog resource.

* Add migration for adding columns to support parsing of SemVer
* Updates the Versions::CreateService to use `release.tag` for
  versioning
* Updates specs that were not using semantic version, thus testing the
  semantic version validation further
* Quarantines an out of date feature spec

Changelog: added

Changelog: other

This commit introduces a FF which will allow us to read
Ci::JobArtifact from our new partitioned table.

This change adds a cron job to periodically rebuild the contributions
materialized view.

Make setting accessible from UI for changing settings

Add specs for the new application setting in API and model

Use the new setting column value in pipeline service rate limiter

Update documentation to reflect the new setting changes

This is behind the feature flag
ci_rate_limit_downstream_pipelines.

The transaction checks can be allowed using
`allowing_attempt_in_transaction` but will eventually need to be
removed for optimal database transaction behaviour.

Changelog: other

- for setting and using current organization throughout the app.
- using middleware will allow us to make available in api,
  controller and graphql layers
- move away from using our own CurrentOrganization module and use
  the rails provided CurrentAttributes which attaches to threads
  the same way and provides some default tooling.
- see https://gitlab.com/gitlab-org/gitlab/-/issues/437541

Add redisHLL unique values reading for RedisHLL metric

Updates the system notes formatting for the color change so we can 
display the previous value.

Changelog: changed
EE: true

Created a new service to handle pruning old ProjectExportService and
its associations efficiently. Specifically, upload files need and
be handled and pruned as well. Before, only associated records were
deleted via an ON DELETE CASCADE clause on their postgres tables.

Utilize support in gitlab-glfm-markdown and remove
reliance on possible insecure regex expressions.

Changelog: added

Changelog: changed

Maxime Orefice 创作于 1 year ago ，Maxime Orefice 提交于 1 year ago

This commit enqueues a job which will create a new constraint this
weekend on ci_job_artifacts. This is a prerequisite in order to
partition this table.

Changelog: other

This change adds a service that can be used for re-building a
materialized view.

Enables creating package files with files that belong to a directory,
saving the directory as a URL encoded version of the file name. Changes
the endpoints from /packages/ml_models/model_name/model_version to
/packages/ml_models/model_version_id to simplify route matching.

Instance setting `math_rendering_limits_enabled` can now
be queried and set on groups as well. It is a cascading
setting, so it can be locked at any level.

Changelog: added

Changelog: added
EE: true