| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
- instead of using properties
- backward compatibility has to be kept for now
|
| |\
| |
| |
| |
| | |
Add rake task to clean orphan artifact files
See merge request gitlab-org/gitlab-ce!29681
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds the rake task rake
gitlab:cleanup:orphan_job_artifact_files. This rake task cleans all
orphan job artifact files it can find on disk.
It performs a search on the complete folder of all artifacts on
disk. Then it filters out all the job artifact ID for which it could
not find a record with matching ID in the database. For these, the
file is deleted from disk.
|
| |\ \
| | |
| | |
| | |
| | | |
Add clusters association to deployment
See merge request gitlab-org/gitlab-ce!29960
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
All deployments should have already their cluster_id filled in on
creation. Legacy deployments will not be retried as:-
* Ci::Build#retry calls `Ci::RetryBuildService`
* Ci::Pipeline#retry
calls `Ci::RetryPipelineService` which also calls
`Ci::RetryBuildService`
* `Ci::RetryBuildService` will clone a build to retry
It is also impossibly to backfill Deployment#cluster_id from
Project#deployment_platform correctly as clusters could have been
deleted, added or altered in the intervening time.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
into 'master'
Use PROCESS_CPUTIME_ID for cpu time metrics
Closes #63874
See merge request gitlab-org/gitlab-ce!30166
|
| | | | | |
|
| |/ / /
| | |
| | |
| | |
| | |
| | | |
https://community.atlassian.com/t5/Jira-questions/Is-it-quot-JIRA-quot-or-quot-Jira-quot/qaq-p/681163
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
CE port of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14108
See merge request gitlab-org/gitlab-ce!29604
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Support CIDR notation in IP rate limiter
See merge request gitlab-org/gitlab-ce!30146
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This will make it possible to whitelist multiple IP addresses
(e.g. 192.168.0.1/24).
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
Added commit type to tree GraphQL type
See merge request gitlab-org/gitlab-ce!29412
|
| | | |_|/
| |/| | |
|
| |\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | | |
GraphQL mutations for add, remove and toggle emoji
See merge request gitlab-org/gitlab-ce!29919
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Adding new `AddAwardEmoji`, `RemoveAwardEmoji` and `ToggleAwardEmoji`
GraphQL mutations.
Adding new `#authorized_find_with_pre_checks!` and (unused, but for
completeness `#authorized_find_with_post_checks!`) authorization
methods. These allow us to perform an authorized find, and run our own
additional checks before or after the authorization runs.
https://gitlab.com/gitlab-org/gitlab-ce/issues/62826
|
| |/ / / |
|
| |/ /
| |
| |
| |
| |
| | |
Adds permission checks to the metrics_dashboard endpoint. Users
with role of Reporter or above should have access to view the
metrics for a given project.
|
| |\ \
| | |
| | |
| | |
| | | |
Allow caching of negative FindCommit matches
See merge request gitlab-org/gitlab-ce!29952
|
| | |/
| |
| |
| |
| |
| |
| | |
When FindCommit ref caching is enabled, negative matches would
previously not be cached. However, if a source branch is deleted,
there's no need to keep looking up the same commit. This change caches
the result of a nil commit.
|
| |\ \
| |/
|/|
| |
| |
| |
| | |
into 'master'
Sanity check for GraphQL authorized?
See merge request gitlab-org/gitlab-ce!29921
|
| | |
| |
| |
| | |
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/29921#note_184713939
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Raise an exception if a developer calls any of the GraphQL authorization
methods and a `authorize :permission` is missing from a mutation class.
Previously `authorized?` would return `true` in this situation, which
although technically is accurate is not what a developer is intending.
|
| |/ |
|
| |
|
|
|
| |
The setup was wrong, and due to Gitaly being a bit more strict it had to
match up. The test is now accurate and passing again.
|
| |
|
|
|
| |
Also add ::Gitlab::LetsEncrypt.enabled? shortcut
and simplify it a lot
|
| |
|
|
| |
Changes migration and all other places the attribute is used
|
| |\
| |
| |
| |
| | |
Refactor Deployment#cluster to #deployment_platform_cluster
See merge request gitlab-org/gitlab-ce!29961
|
| | |
| |
| |
| |
| | |
We will introduce #cluster at a later stage.
Also deprecate this method
|
| | |
| |
| |
| | |
This reverts merge request !29832
|
| |\ \
| | |
| | |
| | |
| | | |
Build correct basenames for title search results
See merge request gitlab-org/gitlab-ce!29898
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The "basename" here needs to be the full path without the trailing
extension, instead of stripping the leading path as well.
This was previously fixed in 2f36efa0871 inside the view, but the
problematic code was still present in FoundBlob, and the corresponding
spec didn't actually use a child wiki page to properly verify the fix.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
RSpec::Parameterized syntax for CI pipeline build seed specs
See merge request gitlab-org/gitlab-ce!29947
|
| | | | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fix label serialisation in issue and note hooks
Closes #63473
See merge request gitlab-org/gitlab-ce!29850
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We were not calling hook_attrs on the labels correctly. Specs were
passing because the issues under test did not have any labels!
|
| |\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
Enable JIT Kubernetes resource creation for project level clusters
See merge request gitlab-org/gitlab-ce!29515
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously this behaviour was only available to group
and instance-level clusters, as some project clusters
relied on Kubernetes credentials being passed through
to the runner instead of having their resources managed
by GitLab (which is not available when using JIT). These
clusters have been migrated to unmanaged, so resources
can be created on demand for the remaining managed clusters.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
As Auto DevOps deployments both label and annotations, that will be
included in the deploy board so need to warn at all.
|
| | |_|/ /
|/| | | |
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Avoid storing backtraces from Bitbucket Cloud imports in the database
See merge request gitlab-org/gitlab-ce!29862
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
We noticed in
https://gitlab.com/gitlab-com/gl-infra/production/issues/908 some
Bitbucket imports took over a second to load their projects row because
`import_error` was huge due to errors. To prevent this, we now:
1. Clean the backtraces
2. Log the details into importer.log
3. Omit the details from the database
|
| | | | | |
| | | | |
| | | | |
| | | | | |
https://github.com/rouge-ruby/rouge/blob/master/CHANGELOG.md#version-341-2019-06-13
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
'63406-selecting-a-line-in-ci-job-trace-using-triple-click-selects-the-previous-line-also' into 'master'
Fix copying a single line from Firefox
Closes #63406
See merge request gitlab-org/gitlab-ce!29832
|
| | |\ \ \ \ \
| | |/ / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
'63406-selecting-a-line-in-ci-job-trace-using-triple-click-selects-the-previous-line-also'
# Conflicts:
# spec/lib/gitlab/ci/ansi2html_spec.rb
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This change ensures that all open <span> tags are closed before adding a
<br> tag.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Do not rewrite relative links for system notes
Closes #63162
See merge request gitlab-org/gitlab-ce!29825
|
| | | | | | | | |
|
| |\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Add Gitaly data to the usage ping
See merge request gitlab-org/gitlab-ce!29893
|
| | | |_|_|_|_|/
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Gitaly data wasn't available to the team, an this change is a first
iteration towards understanding what data we need and how to interpret
it. Later more values will be added.
For now the most important thing is the filesystem String Array, as that
includes data on ext4 exposure and NFS.
Part of: https://gitlab.com/gitlab-org/gitlab-ce/issues/60602
|
