| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |\
| |
| |
| |
| |
| |
| |
| |
| | |
'58941-use-gitlab-serverless-with-existing-knative-installation' into 'master'
Resolve "Use GitLab serverless with existing Knative installation"
Closes #58941
See merge request gitlab-org/gitlab-ce!27173
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Remove Kn services cache from Clusters::Application::Knative
Knative function can exist even if user did not installed Knative via
GitLab managed apps.
-> Move responsibility of finding services into the Cluster
-> Responsability is inside Clusters::Cluster::KnativeServiceFinder
-> Projects::Serverless::FunctionsFinder now calls depends solely on a
cluster to find the Kn services.
-> Detect Knative by resource presence instead of service presence
-> Mock knative_installed response temporarily for frontend to develop
Display loader while `installed === 'checking'`
Added frontend work to determine if Knative is installed
Memoize with_reactive_cache(*args, &block) to avoid race conditions
When calling with_reactive_cache more than once, it's possible that the
second call will already have the value populated. Therefore, in cases
where we need the sequential calls to have consistent results, we'd fall
under a race condition.
Check knative installation via Knative resource presence
Only load pods if Knative is discovered
Always return a response in FunctionsController#index
- Always indicate if Knative is installed, not installed or checking
- Always indicate the partial response for functions. Final response is
guaranteed when knative_installed is either true | false.
Adds specs for Clusters::Cluster#knative_services_finder
Fix method name when calling on specs
Add an explicit check for functions
Added an explicit check to see if there are any functions available
Fix Serverless feature spec
- we don't find knative installation via database anymore,
rather via Knative resource
Display error message for request timeouts
Display an error message if the request times out
Adds feature specs for when functions exist
Remove a test purposed hardcoded flag
Add ability to partially load functions
Added the ability to partially load functions on the frontend
Add frontend unit tests
Added tests for the new frontend additions
Generate new translations
Generated new frontend translations
Address review comments
Cleaned up the frontend unit test.
Added computed prop for `isInstalled`.
Move string to constant
Simplify nil to array conversion
Put knative_installed states in a frozen hash for better read
Pluralize list of Knative states
Quey services and pods filtering name
This way we don't need to filter the namespace in memory.
Also, the data we get from the network is much smaller.
Simplify cache_key and fix bug
- Simplifies the cache_key by removing namespace duplicate
- Fixes a bug with reactive_cache memoization
|
| | |
| |
| |
| |
| |
| |
| | |
- Renames attributes from stat to project_statistiscs_name and attribute
to statistic_attribute
- Reordes methods on UpdateProjectStatistics concern
- Removes unused module from Ci::Build
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Gitlab::HTTP now resolves the hostname only once, verifies the IP is not
blocked, and then uses the same IP to perform the actual request, while
passing the original hostname in the `Host` header and SSL SNI field.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Upgrade Gitaly to v1.43.0
See merge request gitlab-org/gitlab-ce!28867
|
| | | |/
| |/|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
It used to be the case that GitLab created symlinks for each repository
to one copy of the Git hooks, so these ran when required. This changed
to set the hooks dynamically on Gitaly when invoking Git.
The side effect is that we didn't need all these symlinks anymore, which
Gitaly doesn't create anymore either. Now that means that the tests in
GitLab-Rails should test for it either.
Related: https://gitlab.com/gitlab-org/gitaly/issues/1392#note_175619926
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
- Select notification email by walking up group/subgroup path
- Add settings UI to set group email notification address
- Add tests
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Remove migration generating lets encrypt key
Don't generate private_key if database is readonly
For reference:
This reverts commit 988a7f70489b99383b95e9f271a2caf6bb5b3a44.
This reverts commit 21acbe531592d55caf0e5b8716a3b551dafd6233.
|
| |/
|
|
|
|
|
|
|
| |
Enabling GraphQL batch requests allows for multiple queries
to be sent in 1 request reducing the amount of requests
we send to the server.
Responses come come back in the same order as the queries were
provided.
|
| |
|
|
|
| |
This reverts commit 744f1f2e7037f5c70c3168d9e2e89b1c327465d2, reversing
changes made to c4d930e5f54e7da07c80cc028dfc0f5c08719146.
|
| |\
| |
| |
| |
| | |
Bump shoulda-matchers to 4.0.1
See merge request gitlab-org/gitlab-ce!28443
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This removes the warning when using Ruby 2.6:
BigDecimal.new is deprecated; use BigDecimal() method instead.
This also adds Rails 5 support, which eliminates the need for the monkey
patch to handle
https://github.com/thoughtbot/shoulda-matchers/issues/913.
|
| | |
| |
| | |
This reverts merge request !27514
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'61935-remove-code-left-over-from-when-clusters-were-always-project-specific' into 'master'
remove `Clusters::Platforms::Kubernetes#actual_namespace`
Closes #61935
See merge request gitlab-org/gitlab-ce!28391
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When Kubernetes clusters were originally built they could only
exist at the project level, and so there was logic included
that assumed there would only ever be a single Kubernetes
namespace per cluster. We now support clusters at the group
and instance level, which allows multiple namespaces.
This change consolidates various project-specific fallbacks to
generate namespaces, and hands all responsibility to the
Clusters::KubernetesNamespace model. There is now no concept of
a single namespace for a Clusters::Platforms::Kubernetes; to
retrieve a namespace a project must now be supplied in all cases.
This simplifies upcoming work to use a separate Kubernetes
namespace per project environment (instead of a namespace
per project).
|
| |\ \ \
| |_|/
|/| |
| | |
| | | |
Reorganize test jobs by level
See merge request gitlab-org/gitlab-ce!27514
|
| | | |
| | |
| | |
| | | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Move some project routes under /-/ scope
See merge request gitlab-org/gitlab-ce!28435
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
For settings, branches and tags
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |_|/
|/| | |
|
| | |/
|/| |
|
| |\ \
| | |
| | |
| | |
| | | |
CE backport for "Use gitlab-elasticsearch-indexer in tests"
See merge request gitlab-org/gitlab-ce!28369
|
| | |/ |
|
| |\ \
| |/
|/|
| |
| | |
Add issues_statistics api endpoints
See merge request gitlab-org/gitlab-ce!27366
|
| | |
| |
| |
| |
| |
| |
| | |
* Cleaned issues and issues_statistics docs
* Renamed param with_labels_data to with_labels_details
* Added spec for N+1 check when retrieving labels from issue
* Refactoed CheckAssigneesCount validation class
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
Remove label_name and milestone_title params support
Add mutually_exclusive validation for author_id and author_username
Add mutually_exclusive validation for assignee_id and assignee_username
Add validation to allow single value for asignee_username on CE
Add separate issue_stats_params helper for statistics params and
reuse in issues_params.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When issues_controller endpoint was used for search, the parameters
passed to the controller were slightly different then the ones
passed to API. Because the searchbar UI is reused in different
places and builds the parameters passed to request in same way
we need to account for old parameter names.
Add issues_statistics api endpoints
Adds issue_statistics api endpoints for issue lists and returns
counts of issues for all, closed and opened states.
Expose more label attributes based on a param
When requesting issues list through API expose more attributes
for labels, like color, description if with_labels_data param is
being passed, avoiding this way to change response schema for users
that already use API.
https://gitlab.com/gitlab-org/gitlab-ce/issues/57402
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
| |
Part of adding Let's Encrypt certificates for pages domains
Add acme-client gem
Client is being initialized by private key stored in secrets.yml
Let's Encrypt account is being created lazily.
If it's already created, Acme::Client just gets account_kid by
calling new_account method
Make Let's Encrypt client an instance
Wrap order and challenge classes
|
| |\
| |
| |
| |
| | |
Fix hiding of quick action prompt in specs
See merge request gitlab-org/gitlab-ce!28285
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
Avoid counting on Rails eager loading the GraphQL types, but preload
them before the specs.
This would avoid loading the schema in 2 separate threads
concurrently (1 inside the specs, 1 inside the test-server that will
receive requests). Loading the schema in parallel like that could
cause duplicate definition errors.
|
| |\
| |
| |
| |
| | |
Simplify frontend test fixtures
See merge request gitlab-org/gitlab-ce!27531
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This helper is right on the limit of the number of calls being made.
When the request store is enabled, and Sidekiq is running in inline
mode, just a couple of additional actions result in it being pushed
over the line.
The operation is entirely artificial, since in reality we'd perform
these requests in multiple separate processes, so just whitelist it
for now.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
58404 - setup max depth for graphql
Closes #58404
See merge request gitlab-org/gitlab-ce!25737
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
58404 - add change log
58404 - add spec
58404 - add more spec to test depth 2
58404 - fix spec
58404 - fix rubocop
58404 - refactor the code by Bob's advice
58404 - revert changes of all_graphql_fields_for
58404 - change text only
58404 - fix rspec according to gitlab's standard
58404 - revert previous spec
58404 - fix rubocop
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
Adds header column to variables list
Closes #46806
See merge request gitlab-org/gitlab-ce!28060
|
| | | |
| | |
| | |
| | |
| | | |
For the variables list in CI/CD settings
this commits adds an header row with titles
|
| |\ \ \
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Try to reduce testing viewport
Closes #58882
See merge request gitlab-org/gitlab-ce!27385
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| | |
Hoping that we don't hit into
Selenium::WebDriver::Error::NoSuchDriverError:
invalid session id
Again.
|
| |\ \
| | |
| | |
| | |
| | | |
Generate EE-specific JavaScript fixtures into ee/ directory (CE-backport)
See merge request gitlab-org/gitlab-ce!28032
|
| | | |
| | |
| | |
| | | |
(cherry picked from commit d4ce3c720ecb52f2a9153133bbd47fa358c5d7b6)
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow replying to an individual note in the API
Closes #61392
See merge request gitlab-org/gitlab-ce!28120
|
| | | |/
| |/|
| | |
| | |
| | |
| | | |
If you can do this in the UI, you should be able to do it in the API. If
a discussion is not a single note discussion, or it is replyable, you
can reply to it.
|
| |\ \ \
| |/ /
|/| |
| | |
| | | |
Add close_select2 method to select2_helper
See merge request gitlab-org/gitlab-ce!27981
|
| | | |
| | |
| | |
| | |
| | |
| | | |
**Why?**
This is needed to create a feature test for:
https://gitlab.com/gitlab-org/gitlab-ee/issues/11194
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add env_var and file as supported types for CI variables. Variables of
type file expose to users existing gitlab-runner behaviour - save
variable value into a temp file and set the path to this file in an ENV
var named after the variable key.
Resolves https://gitlab.com/gitlab-org/gitlab-ce/issues/46806.
|
