| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
Rake task to cleanup expired ActiveSession lookup keys
See merge request gitlab-org/gitlab-ce!30668
|
| |
| |
| |
| |
| |
| |
| | |
In some cases ActiveSession.cleanup was not called after authentication,
so for some user ActiveSession lookup keys grew without ever cleaning
up. This Rake task manually iterates over the lookup keys and removes
ones without existing ActiveSession.
|
|\ \
| | |
| | |
| | |
| | | |
Multiple pipeline support for Build status
See merge request gitlab-org/gitlab-ce!30828
|
| | |
| | |
| | |
| | |
| | | |
Adds specs for testing the new behavior of specifying a pipeline when
POSTing a status.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This allows user to specify the pipeline ID
when several pipelines has been triggered
on the same branch and commit.
Signed-off-by: Gaetan Semet <gaetan.semet@renault.com>
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
'master'
Add better error message to MembersMapper#ensure_default_member!
See merge request gitlab-org/gitlab-ce!30838
|
| | | | |
|
| |/ /
| | |
| | |
| | | |
More details in: https://gitlab.com/gitlab-org/gitlab-ce/issues/64377
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Support remove source branch on merge w/ push options
See merge request gitlab-org/gitlab-ce!30728
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
MergeRequests::PushOptionsHandlerService has been updated to allow
creating and updating merge requests with the
`remove_source_branch` set using git push options.
To create a new merge request and set it to remove the source branch
when it is merged:
git push -u origin -o merge_request.create \
-o merge_request.remove_source_branch
To update an existing merge request and set it to remove the source
branch when it is merged:
git push -u origin -o merge_request.remove_source_branch
Issue https://gitlab.com/gitlab-org/gitlab-ce/issues/64320
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It seems that we missed the backward compatibility support
for profiles in the existing folder.
This commit also fixes some specs to be idempotent
and work in a temporary directory which not always
seems to be the case.
This commit also brings the profile_spec.rb which seems
to be missing.
|
| | |
| | |
| | |
| | |
| | | |
This will make it easier to parse this in production and adds the
`correlation_id` if available.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Add a group setting to allow Maintainers to create sub-groups
See merge request gitlab-org/gitlab-ce!29718
|
| | | | |
|
| | | | |
|
| |_|/
|/| |
| | |
| | |
| | |
| | | |
PATs are accepted using the OAuth2 compliant header
"Authorization: Bearer {token}" in order to allow for
OAuth requests while 2FA is enabled.
|
|/ /
| |
| |
| |
| |
| |
| | |
This adds a counter to count page creation, which is reflected in the
usage-data we collect.
The number created is stored in Redis, avoiding DB access.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Fix Gitaly auto-detection caching
Closes #64802
See merge request gitlab-org/gitlab-ce!30954
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If `GitalyClient#can_use_disk?` returned `false`, it was never cached
properly and led to excessive number of Gitaly calls. Instead of using
`cached_value.present?`, we need to check `cached_value.nil?`.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64802
|
| | |
| | |
| | |
| | | |
See https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/6069
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Get rid of `worker_label` in RubySampler
See merge request gitlab-org/gitlab-ce!30942
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We have Prometheus::PidProvider which sets correct worker id for a
process, so such implementation of `worker_label` in the sampler is
obsolete.
|
| |/ /
|/| | |
|
|\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Resolve "Export frontend fixtures as pipeline artifact"
Closes #64722 and #59166
See merge request gitlab-org/gitlab-ce!30917
|
| | |
| | |
| | |
| | |
| | | |
Moves every fixture source file from
spec/javascripts to spec/frontend
|
| | |
| | |
| | |
| | |
| | |
| | | |
Introduces frontend:fixtures rake task to replace
karma:fixtures and update documentation and CI scripts
to match
|
| | |
| | |
| | |
| | |
| | |
| | | |
* Remove `controller` and `action` labels from duration histogram.
* Create a new simple counter for `controller` and `action`.
* Adjust histogram buckets to observe smaller response times.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The actions tracked in the web IDE are:
- creation of commits
- creation of merge requests
- projects loaded
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Use predictable environment slugs
See merge request gitlab-org/gitlab-ce!30551
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | | |
If an environment slug is predictable given only the environment
name, we can use the environment slug earlier in the CI variable
evaluation process as we don't have to wait for the environment
record itself to be persisted.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
With https://gitlab.com/gitlab-org/gitlab-ee/issues/12388 change going
live there is potential risk of breaking imports of 'Internal' projects.
This change makes sure if 'Internal' visibility level is restricted
all 'Internal' projects will be marked as 'Private'
See: https://gitlab.com/gitlab-org/gitlab-ce/issues/64311
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Adds chaos endpoints to Sidekiq
Closes #64663
See merge request gitlab-org/gitlab-ce!30814
|
| | |
| | |
| | |
| | |
| | | |
This allows the chaos endpoints to be invoked in Sidekiq so that this
environment can be tested for resilience.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This improves the `add_timestamps_with_timezone` helper by allowing the
column names to be configured. This has the advantage that unnecessary
columns can be avoided, saving space.
A helper for removing the columns is also provided, to be used in the
`down` method of migrations.
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Add Rugged calls and duration to API and Rails logs
Closes #64676
See merge request gitlab-org/gitlab-ce!30871
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This adds `rugged_duration_ms` and `rugged_calls` fields to
`api_json.log` and `production_json.log`. This will make it easier to
identify performance issues caused by excessive I/O.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64676
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Add profile mode to extend request profiling
See merge request gitlab-org/gitlab-ce!30126
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Extend the support for "X-Profile-Token: <token>" to have an additional
header that defines type of profile we are looking for, like:
X-Profile-Mode: execution
X-Profile-Mode: memory
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Use relative worker identifier for metrics (instead of Process.pid) and
identify when Unicorn/Puma/Sidekiq is used.
Previously, it was assumed that all metrics are gathered from Unicorn
due to hardcoded implementation which was incorrect.
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix inconsistency in Redis performance bar stats
Closes #64707
See merge request gitlab-org/gitlab-ce!30866
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
peek-redis resets its counters at the start of an ActionController
notification (`start_processing.action_controller`), which causes it to
miss some Redis queries that precede it, such as the database load
balancer and Rack Attack queries. This produces inconsistencies in the
performance bar between the number of calls and their durations with the
actual calls in the detailed view.
We fix this by getting rid of peek-redis in favor of consolidating all
logic into the `RedisDetailed` view, which tracks Redis queries using
`RequestStore`. This has the nice property of removing thread-specific
counters as well.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/64707
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
API: Allow changing only ci_default_git_depth
See merge request gitlab-org/gitlab-ce!30888
|
| | |/ / /
| |/| | | |
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Use correct parent when committing in WebIDE
See merge request gitlab-org/gitlab-ce!29598
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
When passing start_branch on committing from the WebIDE, it's possible
that the branch has changed since editing started, which results in the
change being applied on top of the latest commit in the branch and
overwriting the new changes.
By passing the start_sha instead we can make sure that the change is
applied on top of the commit which the user started editing from.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Deploy serverless apps with `gitlabktl`
Closes #64494
See merge request gitlab-org/gitlab-ce!30740
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
Adjust cycle analytics to group level
See merge request gitlab-org/gitlab-ce!30391
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Change small things for better readability
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Make specs more readable
|