| Age | Commit message (Collapse) | Author |
|---|
|
It adds a hash response which includes
the count, success state and the moved
issues itself so the caller has additional
information about the result of the
process.
|
|
[CE] Upgrade to Rails 5.2
See merge request gitlab-org/gitlab-ce!30052
|
|
Regenerate discussion_id for notes that are being copied over to the
epic when issue is promoted to epic.
https://gitlab.com/gitlab-org/gitlab-ee/issues/11445
|
|
Resolve "API support for group-level clusters"
Closes #55623
See merge request gitlab-org/gitlab-ce!30213
|
|
Updates changed method names and fixes spec failures
|
|
To make it possible to index the `from` and `to` fields with
Elasticsearch and other tools, we need the types to be the same.
Currently they are a mix of boolean and string values.
Part of https://gitlab.com/gitlab-org/gitlab-ee/issues/12599
|
|
Add endpoint to move issues in boards
See merge request gitlab-org/gitlab-ce!30216
|
|
Add specs for new endpoint to move multiple issues.
Add changelog entry
Just check the first issue for the ability to move / update
Add specs for exceeding limits and malformed requests
Changed name of shared examples
Change title of changelog entry
Use %i instead of %w
Check permission to update issue on project instead of board
Use admin_issue permission to check for issue move ability
Changed variable name to avoid shadow issue_params method
Rename route to bulk_move
Change route definition
Check permissions for each issue
Combine methods for parameters permit check
Remove extra context
Change description of context
Check param for type Array
Add unit tests to MoveService
Use before_action for permission check
Use set instead of let!
Use let's instead of set
|
|
GitLab uses a kubernetes service account to perform deployments. For
serverless deployments to work as expected with externally created
clusters with their own knative installations (e.g. via Cloud Run), this
account requires additional permissions in the serving.knative.dev API
group.
|
|
The current approach requires catching exceptions to handle these errors
and callers are already handling model validations so it seems more
appropriate. Also it seemed to convoluted to add this logic directly to
the model since the model needs to check too many possible associations
to determine whether or not there are more than one cluster since the
model doesn't know what it's being created on. Additionally we only
wanted to validate during create to avoid the risk of existing models
becoming invalid by many different edge cases.
|
|
Suggests to use a JSON structured log instead
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/54102
|
|
|
|
[CE port] Bypass push rules for merge to ref service
See merge request gitlab-org/gitlab-ce!30426
|
|
Turns out push rules to validate commit message does
not apply in the context of automatic merge to
the refs/merge-requests/:iid/merge. Mainly because
if it fails to merge to it, we currently can't give enough
preemptive feedback to the user and it'll turn the
merge request unmergeable (given we automatically
mark it as unmergeable if we can't merge to the ref).
In general, it's a systematic operation, which already
bypasses user authorization and git hooks.
Therefore, this commit makes it bypass the push rules
at EE as well.
|
|
Task list updates should not mark users action as spam on akismet.
|
|
This is a port MR for CE
Original MR:
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14141
|
|
CE Port: Extend `MergeToRefService` to create merge ref from an arbitrary ref
See merge request gitlab-org/gitlab-ce!30361
|
|
CE Port: Split AutoMergeService interfaces into two `cancel` and `abort`
See merge request gitlab-org/gitlab-ce!30249
|
|
This is to prepare for supporing image type position tracing
|
|
Currently, MergeToRefService is specifically designed for
createing merge commits from source branch and target branch of
merge reqeusts. We extend this behavior to source branch and any
target ref paths.
|
|
Create explicit endpoint - abort.
|
|
Now that KubernetesService can no longer be a DeploymentPlatform we can
remove all kubernetes client code and KubernetesService edge cases.
|
|
Allow asynchronous rebase operations to be monitored
Closes #54117
See merge request gitlab-org/gitlab-ce!29940
|
|
CE Port: Refactor pipeline errors_message
See merge request gitlab-org/gitlab-ce!30116
|
|
This MR introduces tracking of the `rebase_jid` for merge requests. As
with `merge_ongoing?`, `rebase_in_progress?` will now return true if a
rebase is proceeding in sidekiq.
After one release, we should remove the Gitaly-based lookup of rebases.
It is much better to track this kind of thing via the database.
|
|
Fix the system note service
|
|
Use the shared method in Ci::Pipeline
|
|
Limit amount of JUnit tests returned
Closes #64035
See merge request gitlab-org/gitlab-ce!30274
|
|
Currently, we do not cap amount of tests returned to frontend,
thus in some extreme cases we can see a MBs of data stored in Redis.
This adds an upper limit of 100 tests per-suite.
We will continue showing the total counters correctly,
but we will limit amount of tests that will be presented.
|
|
rename `discussion` to `thread`
Closes #55953
See merge request gitlab-org/gitlab-ce!29553
|
|
Deprecate diverging commit count with max parameter
Closes gitaly#1702
See merge request gitlab-org/gitlab-ce!30275
|
|
|
|
Add released_at field to releases API
Add released_at column to releases table
Return releases to the API sorted by released_at
|
|
In 12.0, we turned the feature flag on that effectively turned off the
--max-count flag for the count diverging commits call. Since we have
commit graphs turned on, this did not affect preformance negatively.
Thus, we want to deprecate the call that passes --max-count
|
|
This new attribute is optional and used when set instead of the default
format `gitlab+deploy-token-#{id}`.
Empty usernames will be saved as null in the database.
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/50228.
|
|
- 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
|
|
all threads")
|
|
Support creating an MR/branch on a fork from an issue
See merge request gitlab-org/gitlab-ce!29831
|
|
Add endpoint for fetching diverging commit counts
See merge request gitlab-org/gitlab-ce!29802
|
|
When `confidential_issue_project_id` is set and the issue is
under that project, create the a note about branch creation
in that project. If not, do nothing.
When creating `new_merge_request` system note, set the project
where the MR will be referenced from so it'll be linked to when
the MR is created in another project.
|
|
|
|
Extract diverging_commit_counts into a service class
|
|
|
|
This commit makes it possible for
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14420 to handle
multiple SAML providers.
|
|
Move Multiple Issue Boards for Projects to Core
See merge request gitlab-org/gitlab-ce!29757
|
|
|
|
Refactor code to allow multiple issue boards management for projects
in CE
|
|
When the SQL query cache is active, the SELECT query for finding
projects to apply service templates returns the same values. This causes
an infinite loop because even though bulk INSERT queries are made, the
cached results never reflect that progress. To fix this, we call
`Project.uncached` around the query to ensure new data is retrieved.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63595
|
|
Automatically update MR merge-ref along merge status
See merge request gitlab-org/gitlab-ce!29569
|
|
Enable JIT Kubernetes resource creation for project level clusters
See merge request gitlab-org/gitlab-ce!29515
|
