| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
| |
It consists of two parts:
1. Redirecting users to the configured external storage
1. Allowing the external storage to request the static object(s)
on behalf of the user by means of specific tokens
Part of https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6829
|
| |\
| |
| |
| |
| | |
Add Danger Roulette rules for pipeline files
See merge request gitlab-org/gitlab-ce!32616
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
into 'master'
Resolve "user-content.gitlab-static.net brings back 404 only"
See merge request gitlab-org/gitlab-ce!32703
|
| | |/ |
|
| |/
|
|
|
|
|
| |
Since it is not possible to dynamically detect if a job is automatically
cancellable or not, a this new attribute is necessary. Moreover, it let
the maintainer of the repo to adjust the behaviour of the auto cancellation
feature to match exactly what he needs.
|
| |\
| |
| |
| |
| | |
Extract /internal/allowed API Actor logic out
See merge request gitlab-org/gitlab-ce!31564
|
| | |
| |
| |
| |
| |
| | |
Created new API::Support::GitAccessActor class to
encapsulate some of the more edge logic, making
the /internal/allowed route much cleaner.
|
| | |
| |
| |
| |
| |
| | |
- Move code for creating a new column from old into a function so that
it can be reused.
- Also add comments above the methods.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'66150-remove-dynamically-constructed-feature-flags-starting-with-prometheus_transaction_' into 'master'
Resolve "Remove dynamically constructed feature flags starting with `prometheus_transaction_`"
Closes #66150
See merge request gitlab-org/gitlab-ce!32395
|
| | | |
| | |
| | |
| | | |
Those feature flags were always enabled so we can remove them safely.
|
| |/ / |
|
| |\ \
| | |
| | |
| | |
| | | |
Avoid calling freeze on already frozen strings in lib/gitlab
See merge request gitlab-org/gitlab-ce!32637
|
| | | | |
|
| | | | |
|
| | |/
|/|
| |
| |
| | |
Now, when the dns rebinging setting is disabled, we will
allow urls that are not resolvable.
|
| | |
| |
| |
| |
| |
| | |
- `edge_nodes` needs to get called on the object
- added `include GlobalID::Identification` in a couple places
- renamed `object` to `item` in spec due to conflict
|
| | |
| |
| |
| |
| | |
When using /due quick action with an invalid date a meaninful error
message is shown.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
- Due to https://github.com/exAspArk/batch-loader/pull/32,
we changed BatchLoader.for into BatchLoader::GraphQL.for
- since our results are wrapped in a BatchLoader::GraphQL,
calling `sync` during authorization is required to get real object
- `graphql` now has it's own authorization system. Our
`authorized?` method conflicted and required renaming
|
| | |
| |
| |
| |
| | |
The current state of group issue boards does not show the "Add issues"
button on the UI for users that are reporters of group child projects.
|
| | |
| |
| |
| | |
(cherry picked from commit 0bf7fecdee5a200eeb4f27b4888a57ceee63bde9)
|
| |\ \
| | |
| | |
| | |
| | | |
Persist `needs:` validation as config error
See merge request gitlab-org/gitlab-ce!32648
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
In case when `needs:` is missing, but when requested by service,
we would not save the pipeline with config_error.
This makes it explicit that we want to persist the error
as `config_error` failure reason.
|
| | | |
| | |
| | |
| | | |
Improve diff lines count efficiency
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Extract Workhorse <-> GitLab JWT authentication to make it reusable
See merge request gitlab-org/gitlab-ce!32623
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
Introduce JWTAutheticatable module that can be reused for ai=uthtication
between Pages and GitLab (the same way we use do now for Workhorse).
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/61927.
|
| |/ /
| |
| |
| |
| |
| | |
so that we can use API::Internal namespace.
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/61927.
|
| |\ \
| | |
| | |
| | |
| | | |
Fix performance bar thresholds
See merge request gitlab-org/gitlab-ce!32587
|
| | | |
| | |
| | |
| | |
| | | |
These were written in seconds but are supposed to be in
milliseconds. The total Gitaly time was wrong for the same reason.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Resolve "Typo in RELEASE_ENDPOINT_REQUIREMETS constant"
Closes #66464
See merge request gitlab-org/gitlab-ce!32468
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Improve GC_REPORT_BUCKETS granularity
See merge request gitlab-org/gitlab-ce!32586
|
| | | | | |
|
| |/ / / |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Modified schema via migrations.
Added one-to-one relationship between the two models.
Added changelog file
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Backport retries options for cancel_running
See merge request gitlab-org/gitlab-ce!32525
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Remove all references to Gitlab::CorrelationId
See merge request gitlab-org/gitlab-ce!32228
|
| | | | |
| | | |
| | | |
| | | | |
This class has been replaced with Labkit::Correlation::CorrelationId
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Extends the permission of $CI_REGISTRY_USER to allow them
to delete tags in addition to just pushing.
https://gitlab.com/gitlab-org/gitlab-ce/issues/40096
|
| | | | |
| | | |
| | | | |
This allows overriding `only.refs` to something else if needed.
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Prometheus listen_address can be in formats of :9090 and 0.0.0.0:9090.
But before these can be used to connect a project to Prometheus, they
have to converted into absolute URIs.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Fix permissions check in `RelativeLinkFilter`
See merge request gitlab-org/gitlab-ce!32448
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes RelativeLinkFilter for users that don't have access
to the project's repository
|
| | |_|/ /
|/| | |
| | | |
| | | | |
as requested by the reviewer
|
| | | | |
| | | |
| | | |
| | | | |
Wrong format on MS Teams integration push events with multi line commit messages
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix Peek on Puma
Closes #66528
See merge request gitlab-org/gitlab-ce!32213
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously, we called the `peek_enabled?` method like so:
prepend_before_action :set_peek_request_id, if: :peek_enabled?
Now we don't have a `set_peek_request_id` method, so we don't need that
line. However, the `peek_enabled?` part had a side-effect: it would also
populate the request store cache for whether the performance bar was
enabled for the current request or not.
This commit makes that side-effect explicit, and replaces all uses of
`peek_enabled?` with the more explicit
`Gitlab::PerformanceBar.enabled_for_request?`. There is one spec that
still sets `SafeRequestStore[:peek_enabled]` directly, because it is
contrasting behaviour with and without a request store enabled.
The upshot is:
1. We still set the value in one place. We make it more explicit that
that's what we're doing.
2. Reading that value uses a consistent method so it's easier to find in
future.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Peek's `Peek.request_id` method doesn't work well with a multi-threaded
server and concurrent requests, because requests can 'steal' another
request's ID, or unset it before it was due.
The upstream change resolves this; the commit here is just to ensure
that GitLab works with that upstream change, mostly by not using
`Peek.request_id` any more (as the method doesn't exist).
|
| | | | | | |
|
