| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| |
| |
| | |
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.
|
| |\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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
|
| | | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This commits adds support for metrics dashboards
for embedding. If the flag 'embedded' is provided
to the environments/id/metrics_dashboard endpoint,
the response will be suitable for embedding in
issues or other content.
This is a precursor for support for embedding
metrics in GFM.
|
| |\ \ \ \ \ \
| |/ / / / /
|/| | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
'master'
Gitlab::JsonCache#parse_value ensure string
Closes #63510
See merge request gitlab-org/gitlab-ce!29885
|
| | | |/ / /
| |/| | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Remove import columns from projects table
See merge request gitlab-org/gitlab-ce!29863
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
In https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21497, we
migrated all project import data into a separate table,
`project_import_data`. In addition, we also added:
```
ignore_column :import_status, :import_jid, :import_error
```
In https://gitlab.com/gitlab-com/gl-infra/production/issues/908, we
observed some of these `import_error` columns consumed megabytes of
error backtraces and caused slow loading of projects whenever a `SELECT
* from projects` query loaded the row into memory.
Since we have long migrated away from these columns, we can now drop
these columns entirely.
|
| |/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This adds a `markdown_field` to our types.
Using this helper will render a model's markdown field using the
existing `MarkupHelper` with the context of the GraphQL query
available to the helper.
Having the context available to the helper is needed for redacting
links to resources that the current user is not allowed to see.
Because rendering the HTML can cause queries, the complexity of a
these fields is raised by 5 above the default.
The markdown field helper can be used as follows:
```
markdown_field :note_html, null: false
```
This would generate a field that will render the markdown field `note`
of the model. This could be overridden by adding the `method:`
argument. Passing a symbol for the method name:
```
markdown_field :body_html, null: false, method: :note
```
It will have this description by default:
> The GitLab Flavored Markdown rendering of `note`
This could be overridden by passing a `description:` argument.
The type of a `markdown_field` is always `GraphQL::STRING_TYPE`.
|
| |\ \ \ \
| |_|_|/
|/| | |
| | | |
| | | |
| | | |
| | | | |
Adds missing class in collapsible sections
Closes #63417
See merge request gitlab-org/gitlab-ce!29804
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Will apply identation from
CSS to collapsible sections
|
| | |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit adds
- feature specs
- to test the ability of a user with "developer" permission
to delete tags in repositories.
- documentation
|
