Age | Commit message (Collapse) | Author |
|
This factors out the IO into its own testable module.
The advantage of this is that we can easily instantiate versions of the
plugin that have different team sources, without extensive mocking.
This proved to be necessary to test an update to the `roulette.json`
production in the handbook.
|
|
Avoid storing backtraces from Bitbucket Cloud imports in the database
See merge request gitlab-org/gitlab-ce!29862
|
|
Make HTML and text emails for new issues uniform and add the mail to mailer previews
Closes #58065
See merge request gitlab-org/gitlab-ce!29886
|
|
Renders pre-release tag for pre-releases
See merge request gitlab-org/gitlab-ce!29797
|
|
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
|
|
Add ability to reorder issues
See merge request gitlab-org/gitlab-ce!29012
|
|
Adds enum certificate_source to pages_domains table
with default manually_uploaded
Mark certificates as 'gitlab_provided'
if the were obtained through Let's Encrypt
Mark certificates as 'user_provided' if they were uploaded through
controller or api
Only show private key in domain edit form if it is 'user_provided'
Only show LetsEncrypt option if is enabled by application settings
(and feature flag)
Refactor and fix some specs to match new logic
Don't show Let's Encrypt certificates as well
|
|
to support manual sorting on the frontend
|
|
The various LDAP check Rake tasks have long supported a SANITIZE
environment variable. When present, identifiable information is
obscured such as user names and project/group names. Until now,
the LDAP check did not honor this. Now it will only say how many
users were found. This should at least give the indication that
the LDAP configuration found something, but will not leak what
it is. Resolves #56131
|
|
Uniform new_issue_email html and text emails
Uniform note_email html and text emails
Uniform new_merge_request_email html and text emails
|
|
Backport and Docs for Paginate license management and add license search
See merge request gitlab-org/gitlab-ce!27602
|
|
Add test for checking output
|
|
When a release is a pre release, we render
an orange badge with `pre-release` label
|
|
Resolve "Race condition in fetching Kubernetes token causes missing `$KUBECONFIG`"
Closes #63507
See merge request gitlab-org/gitlab-ce!29922
|
|
Do not rewrite relative links for system notes
Closes #63162
See merge request gitlab-org/gitlab-ce!29825
|
|
Since Kubernetes is creating the Secret and token asynchronously it is
necessary that we implement some delay or retrying logic to avoid a race
condition where we fetch a Secret before the token is even set. There
does not appear to be any way for us to force it to be set with any
synchronous API call so retrying seems to be the only option.
|
|
Remove Kubernetes service from deployment platform
See merge request gitlab-org/gitlab-ce!29786
|
|
Project-level clusters that made use of this legacy
behaviour have been migrated to unmanaged clusters,
so we are now free to remove this fallback.
|
|
|
|
This will no longer be used for deployments, as all
service templates have been migrated to clusters.
|
|
Migrate managed clusters that aren't using managed features to unmanaged
Closes #62772
See merge request gitlab-org/gitlab-ce!29251
|
|
Migrate clusters with no token to unmanaged
Closes #62772
See merge request gitlab-org/gitlab-ce!29648
|
|
The merge request widget has a section that includes which issues may be
closed or mentioned based on the merge request description. The problem
is that rendering and redacting Markdown can be expensive, especially
since the browser polls for the data every 10 seconds.
Since these links don't change much and are just nice to have, we only
load them on first page load. The frontend will use the existing data if
the data doesn't appear on subsequent requests.
This saves about 30% of the rendering time of this endpoint, which adds
up to significant savings considering that
`MergeRequestsController#show.json` is called over a million times a day
on GitLab.com.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63546
|
|
There are clusters that have Kubernetes namespaces
stored which are missing a service account token.
These namespaces are unable to be used for deployments,
so marking the clusters as unmanaged will allow the
platform credentials to be used instead.
|
|
Add Gitaly data to the usage ping
See merge request gitlab-org/gitlab-ce!29893
|
|
Use next_instance_of instead of any_instance_of
See merge request gitlab-org/gitlab-ce!29905
|
|
Backport changes made by EE to various YAML configuration files
See merge request gitlab-org/gitlab-ce!29606
|
|
For prepended classes, we need to use `expect_next_instance_of`
instead of RSpecs `any_instance_of` variants.
|
|
|
|
into 'master'
Errors in application settings panel shows wrong panel
See merge request gitlab-org/gitlab-ce!25434
|
|
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.
|
|
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
|
|
Render last commit widget with Vue
Closes #62766
See merge request gitlab-org/gitlab-ce!29419
|
|
To make this happen, we need to conditionally add the group_saml
strategy when running tests, but only on EE. This requires some changes
to Gitlab.ee? so that it can be used before/without loading the Rails
environment. We also have to change how we require a few files, so this
can run outside of Rails.
|
|
'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
|
|
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`.
|
|
|
|
First pass at license pagination
* Paginate license management client side
* Refactor license list into seperate component
Add string filtering to license names
* Add search input to query on license name
Add add license button
* Refactor add license button to be a slot
Clean up styles and button state logic
* Clean up alignment
* Disable button when dorpdown is open
Remove client side alphabetical sorting
* Let the databse return order by date
Refactor list to use row slot
Further abstract pagination list compnent
Finish refactor of paginated list
* Refactor component into generic paginated list component
* Add additional style tweaks + responsive classes
Run prettier
Update license_management_spec
Run Prettier
Add unit tests for paginated list component
* Refactor template to be valid html (li in ul)
* Add jest unit tests
Add additional unit tests
* Add unit tests around pagination and search states
Add unit tests for filter props
Pretty print, lint, and add changelog
Update po files
Regernate pot file
Backport EE changes
* Update paginated list component
* Update specs and snapshot
Add POT file
Update default copy for pagianted list
* update copy for empty and empty search result states
Update pot file
Backport changes from EE merge request
* Paginaed list component and specs
Backport EE changes
Update paginated list snapshot
Update license management docs and images
Backport paginated-list component from EE
Link to gitlab-ui artifacts job
Match gitlab ui build to EE
Update pot file
Backport Paginated list changes
Set gitlab-ui to temp artifact
Add changelog
|
|
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.
|
|
Fix N+1 problem in `JobsController#index`
See merge request gitlab-org/gitlab-ce!29839
|
|
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
|
|
This backports to CE changes to allow the EE model
DesignManagement::Repository to override the #attributes_at method to
provide its own git attributes.
The #attributes_at method was freely available, as it's never called by
anything in the app. It looks like the code that called it got
refactored out of existence in ca66a04f. It was still being called in a
spec
https://gitlab.com/gitlab-org/gitlab-ce/blob/85b29c1c2fa3b94d7371cf454c485457a0756cb1/spec/services/files/create_service_spec.rb#L40
which I've left because with the change in Lfs::FileTransformer in fact
is now again the perfect test!
See EE MR
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/14017
And these comment threads
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894#note_178002089
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894#note_178049984
|
|
Updating multiple application settings panels through
a single action causes the incorrect action to be shown
when there are errors. Instead, make each panel action
handle both updating and display.
|
|
Use NotesFinder to get Noteable
See merge request gitlab-org/gitlab-ce!28205
|
|
Use @vue/test-utils for tooltip_on_truncate_spec
See merge request gitlab-org/gitlab-ce!29249
|
|
Added forked projects API call function
See merge request gitlab-org/gitlab-ce!29841
|
|
|
|
'63406-selecting-a-line-in-ci-job-trace-using-triple-click-selects-the-previous-line-also'
# Conflicts:
# spec/lib/gitlab/ci/ansi2html_spec.rb
|