Add latest changes from gitlab-org/gitlab@master
This commit is contained in:
GitLab Bot
parent
5bd8b9d24f
commit
61cf5b32c5
2
Gemfile
2
Gemfile
|
|
@ -299,7 +299,7 @@ gem 'gon', '~> 6.4.0'
|
|||
gem 'request_store', '~> 1.5'
|
||||
gem 'base32', '~> 0.3.0'
|
||||
|
||||
gem 'gitlab-license', '~> 2.2.0'
|
||||
gem 'gitlab-license', '~> 2.2.1'
|
||||
|
||||
# Protect against bruteforcing
|
||||
gem 'rack-attack', '~> 6.6.0'
|
||||
|
|
|
|||
|
|
@ -530,7 +530,7 @@ GEM
|
|||
opentracing (~> 0.4)
|
||||
pg_query (~> 2.1)
|
||||
redis (> 3.0.0, < 5.0.0)
|
||||
gitlab-license (2.2.0)
|
||||
gitlab-license (2.2.1)
|
||||
gitlab-license_finder (6.14.2.1)
|
||||
bundler
|
||||
rubyzip (>= 1, < 3)
|
||||
|
|
@ -1575,7 +1575,7 @@ DEPENDENCIES
|
|||
gitlab-experiment (~> 0.7.1)
|
||||
gitlab-fog-azure-rm (~> 1.3.0)
|
||||
gitlab-labkit (~> 0.24.0)
|
||||
gitlab-license (~> 2.2.0)
|
||||
gitlab-license (~> 2.2.1)
|
||||
gitlab-license_finder (~> 6.0)
|
||||
gitlab-mail_room (~> 0.0.9)
|
||||
gitlab-markup (~> 1.8.0)
|
||||
|
|
|
|||
|
|
@ -0,0 +1,17 @@
|
|||
#import "ee_else_ce/runner/graphql/list/list_item.fragment.graphql"
|
||||
#import "~/graphql_shared/fragments/page_info.fragment.graphql"
|
||||
|
||||
fragment GroupRunnerConnection on CiRunnerConnection {
|
||||
edges {
|
||||
webUrl
|
||||
editUrl
|
||||
node {
|
||||
...ListItem
|
||||
projectCount # Used to determine why some project runners can't be deleted
|
||||
}
|
||||
}
|
||||
pageInfo {
|
||||
__typename
|
||||
...PageInfo
|
||||
}
|
||||
}
|
||||
|
|
@ -1,5 +1,4 @@
|
|||
#import "ee_else_ce/runner/graphql/list/list_item.fragment.graphql"
|
||||
#import "~/graphql_shared/fragments/page_info.fragment.graphql"
|
||||
#import "~/runner/graphql/list/group_runner_connection.fragment.graphql"
|
||||
|
||||
query getGroupRunners(
|
||||
$groupFullPath: ID!
|
||||
|
|
@ -27,17 +26,7 @@ query getGroupRunners(
|
|||
search: $search
|
||||
sort: $sort
|
||||
) {
|
||||
edges {
|
||||
webUrl
|
||||
editUrl
|
||||
node {
|
||||
...ListItem
|
||||
projectCount # Used to determine why some project runners can't be deleted
|
||||
}
|
||||
}
|
||||
pageInfo {
|
||||
...PageInfo
|
||||
}
|
||||
...GroupRunnerConnection
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
|||
|
|
@ -3,6 +3,14 @@ import { GlLink } from '@gitlab/ui';
|
|||
import { createAlert } from '~/flash';
|
||||
import { updateHistory } from '~/lib/utils/url_utility';
|
||||
import { fetchPolicies } from '~/lib/graphql';
|
||||
import { upgradeStatusTokenConfig } from 'ee_else_ce/runner/components/search_tokens/upgrade_status_token_config';
|
||||
import {
|
||||
fromUrlQueryToSearch,
|
||||
fromSearchToUrl,
|
||||
fromSearchToVariables,
|
||||
isSearchFiltered,
|
||||
} from 'ee_else_ce/runner/runner_search_utils';
|
||||
import groupRunnersQuery from 'ee_else_ce/runner/graphql/list/group_runners.query.graphql';
|
||||
|
||||
import RegistrationDropdown from '../components/registration/registration_dropdown.vue';
|
||||
import RunnerFilteredSearchBar from '../components/runner_filtered_search_bar.vue';
|
||||
|
|
@ -22,13 +30,6 @@ import {
|
|||
PROJECT_TYPE,
|
||||
I18N_FETCH_ERROR,
|
||||
} from '../constants';
|
||||
import groupRunnersQuery from '../graphql/list/group_runners.query.graphql';
|
||||
import {
|
||||
fromUrlQueryToSearch,
|
||||
fromSearchToUrl,
|
||||
fromSearchToVariables,
|
||||
isSearchFiltered,
|
||||
} from '../runner_search_utils';
|
||||
import { captureException } from '../sentry_utils';
|
||||
|
||||
export default {
|
||||
|
|
@ -123,7 +124,7 @@ export default {
|
|||
return !this.runnersLoading && !this.runners.items.length;
|
||||
},
|
||||
searchTokens() {
|
||||
return [pausedTokenConfig, statusTokenConfig];
|
||||
return [pausedTokenConfig, statusTokenConfig, upgradeStatusTokenConfig];
|
||||
},
|
||||
filteredSearchNamespace() {
|
||||
return `${GROUP_FILTERED_SEARCH_NAMESPACE}/${this.groupFullPath}`;
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@
|
|||
removal_date: "2022-11-22" # (optional - may be required in the future) YYYY-MM-DD format - the date of the milestone release when this feature is planned to be removed
|
||||
breaking_change: false
|
||||
body: | # Do not modify this line, instead modify the lines below.
|
||||
With the general availability of Gitaly Cluster ([introduced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/)), we have deprecated development (bugfixes, performance improvements, etc) for NFS for Git repository storage in GitLab 14.0. We will continue to provide technical support for NFS for Git repositories throughout 14.x, but we will remove all support for NFS on November 22, 2022. This was originally planned for May 22, 2022, but in an effort to allow continued maturity of Gitaly Cluster, we have chosen to extend our deprecation of support date. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for further information.
|
||||
With the general availability of Gitaly Cluster ([introduced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/)), we have deprecated development (bugfixes, performance improvements, etc) for NFS for Git repository storage in GitLab 14.0. We will continue to provide technical support for NFS for Git repositories throughout 14.x, but we will remove all support for NFS on November 22, 2022. This was originally planned for May 22, 2022, but in an effort to allow continued maturity of Gitaly Cluster, we have chosen to extend our deprecation of support date. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support/#gitaly-and-nfs) for further information.
|
||||
|
||||
Gitaly Cluster offers tremendous benefits for our customers such as:
|
||||
|
||||
|
|
|
|||
|
|
@ -135,6 +135,8 @@ For most JSON requests, `POST`, `PUT`, `PATCH`, and `DELETE` are blocked, and th
|
|||
even if they finish running on the GitLab Runner.
|
||||
- Jobs in the `running` state for longer than the project's time limit do not time out.
|
||||
- Pipelines cannot be started, retried or canceled. No new jobs can be created either.
|
||||
- The status of the runners in `/admin/runners` won't be updated.
|
||||
- `gitlab-runner verify` will return the error `ERROR: Verifying runner... is removed`.
|
||||
|
||||
After Maintenance Mode is disabled, new jobs are picked up again. Jobs that were
|
||||
in the `running` state before enabling Maintenance Mode resume and their logs start
|
||||
|
|
|
|||
|
|
@ -65,7 +65,7 @@ Because file system performance may affect the overall performance of GitLab,
|
|||
[we don't recommend using cloud-based file systems for storage](../administration/nfs.md#avoid-using-cloud-based-file-systems).
|
||||
|
||||
NOTE:
|
||||
[NFS for Git repository storage is deprecated](https://about.gitlab.com/releases/2021/06/22/gitlab-14-0-released/#nfs-for-git-repository-storage-deprecated). See our official [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for further information.
|
||||
[NFS for Git repository storage is deprecated](https://about.gitlab.com/releases/2021/06/22/gitlab-14-0-released/#nfs-for-git-repository-storage-deprecated). See our official [Statement of Support](https://about.gitlab.com/support/statement-of-support/#gitaly-and-nfs) for further information.
|
||||
|
||||
### CPU
|
||||
|
||||
|
|
@ -84,7 +84,7 @@ Memory requirements are dependent on the number of users and expected workload.
|
|||
The following is the recommended minimum Memory hardware guidance for a handful of example GitLab user base sizes.
|
||||
|
||||
- **4GB RAM** is the **required** minimum memory size and supports up to 500 users
|
||||
- Our [Memory Team](https://about.gitlab.com/handbook/engineering/development/enablement/memory/) is working to reduce the memory requirement.
|
||||
- Our [Memory Team](https://about.gitlab.com/handbook/engineering/development/enablement/data_stores/memory/) is working to reduce the memory requirement.
|
||||
- 8GB RAM supports up to 1000 users
|
||||
- More users? Consult the [reference architectures page](../administration/reference_architectures/index.md)
|
||||
|
||||
|
|
@ -326,7 +326,7 @@ GitLab supports the following web browsers:
|
|||
|
||||
- [Mozilla Firefox](https://www.mozilla.org/en-US/firefox/new/)
|
||||
- [Google Chrome](https://www.google.com/chrome/)
|
||||
- [Chromium](https://www.chromium.org/getting-involved/dev-channel)
|
||||
- [Chromium](https://www.chromium.org/getting-involved/dev-channel/)
|
||||
- [Apple Safari](https://www.apple.com/safari/)
|
||||
- [Microsoft Edge](https://www.microsoft.com/en-us/edge)
|
||||
|
||||
|
|
|
|||
|
|
@ -57,7 +57,7 @@ each node should have:
|
|||
## Install Elasticsearch
|
||||
|
||||
Elasticsearch is *not* included in the Omnibus packages or when you install from
|
||||
source. You must [install it separately](https://www.elastic.co/guide/en/elasticsearch/reference/7.x/install-elasticsearch.html "Elasticsearch 7.x installation documentation") and ensure you select your version. Detailed information on how to install Elasticsearch is out of the scope of this page.
|
||||
source. You must [install it separately](https://www.elastic.co/guide/en/elasticsearch/reference/7.16/install-elasticsearch.html "Elasticsearch 7.x installation documentation") and ensure you select your version. Detailed information on how to install Elasticsearch is out of the scope of this page.
|
||||
|
||||
You can install Elasticsearch yourself, or use a cloud hosted offering such as [Elasticsearch Service](https://www.elastic.co/elasticsearch/service) (available on AWS, GCP, or Azure) or the [Amazon OpenSearch](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/gsg.html)
|
||||
service.
|
||||
|
|
|
|||
|
|
@ -261,7 +261,7 @@ resynchronize the information:
|
|||
- To complete a *full sync*, press `Shift` and select the sync icon.
|
||||
|
||||
For more information, read
|
||||
[Atlassian's documentation](https://support.atlassian.com/jira-cloud-administration/docs/synchronize-jira-cloud-to-bitbucket/).
|
||||
[Atlassian's documentation](https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-development-tools/).
|
||||
|
||||
### `Sync Failed` error when refreshing repository data
|
||||
|
||||
|
|
|
|||
|
|
@ -19,11 +19,11 @@ each security partner:
|
|||
- [GrammaTech](https://www.grammatech.com/codesonar-gitlab-integration)
|
||||
- [Indeni](https://docs.cloudrail.app/#/integrations/gitlab)
|
||||
- [JScrambler](https://docs.jscrambler.com/code-integrity/documentation/gitlab-ci-integration)
|
||||
- [Mend](https://www.mend.io/gitlab/)
|
||||
- [Semgrep](https://semgrep.dev/for/gitlab)
|
||||
- [StackHawk](https://docs.stackhawk.com/continuous-integration/gitlab.html)
|
||||
- [Tenable](https://docs.tenable.com/tenableio/Content/ContainerSecurity/GetStarted.htm)
|
||||
- [Venafi](https://marketplace.venafi.com/details/gitlab-ci-cd/)
|
||||
- [Veracode](https://community.veracode.com/s/knowledgeitem/gitlab-ci-MCEKSYPRWL35BRTGOVI55SK5RI4A)
|
||||
- [WhiteSource](https://www.whitesourcesoftware.com/gitlab/)
|
||||
|
||||
<!-- vale gitlab.Spelling = YES -->
|
||||
|
|
|
|||
|
|
@ -12,7 +12,7 @@ Twitter OAuth 2.0 support is [not yet supported](https://gitlab.com/gitlab-org/g
|
|||
To enable the Twitter OmniAuth provider you must register your application with
|
||||
Twitter. Twitter generates a client ID and secret key for you to use.
|
||||
|
||||
1. Sign in to [Twitter Application Management](https://apps.twitter.com).
|
||||
1. Sign in to [Twitter Application Management](https://developer.twitter.com/apps).
|
||||
|
||||
1. Select "Create new app".
|
||||
|
||||
|
|
|
|||
|
|
@ -14,8 +14,8 @@ embed Grafana panels using either:
|
|||
|
||||
## Use Grafana-rendered images
|
||||
|
||||
You can embed live [Grafana](https://docs.gitlab.com/omnibus/settings/grafana.html) panels as a
|
||||
[direct linked rendered image](https://grafana.com/docs/grafana/latest/reference/share_panel/#direct-link-rendered-image).
|
||||
You can embed live [Grafana](https://docs.gitlab.com/omnibus/settings/grafana.html) panels as
|
||||
[a direct link](https://grafana.com/docs/grafana/v7.5/sharing/share-panel/#use-direct-link).
|
||||
Your Grafana instance must:
|
||||
|
||||
- Be available to the target user, either as a public dashboard or on the same network.
|
||||
|
|
@ -46,7 +46,7 @@ format. To embed panels from a Grafana instance, the data source must be:
|
|||
|
||||
To set up the Grafana API in Grafana:
|
||||
|
||||
1. In Grafana, [generate an Admin-level API Token](https://grafana.com/docs/grafana/latest/http_api/auth/#create-api-token).
|
||||
1. In Grafana, [generate an Admin-level API Token](https://grafana.com/docs/grafana/next/developers/http_api/auth/#create-api-token).
|
||||
1. In your GitLab project, go to **Settings > Monitor** and expand the **Grafana authentication**
|
||||
section.
|
||||
1. To enable the integration, check the **Active** checkbox.
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ group: Distribution
|
|||
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
|
||||
---
|
||||
|
||||
<!-- any changes made to this page should be reflected in https://about.gitlab.com/support/statement-of-support.html#alpha--beta-features and https://about.gitlab.com/handbook/product/gitlab-the-product/#alpha-beta-ga -->
|
||||
<!-- any changes made to this page should be reflected in https://about.gitlab.com/support/statement-of-support/#alpha-beta-features and https://about.gitlab.com/handbook/product/gitlab-the-product/#alpha-beta-ga -->
|
||||
|
||||
# Support for Alpha, Beta, Limited Availability, and Generally Available Features **(PREMIUM)**
|
||||
|
||||
|
|
|
|||
|
|
@ -266,7 +266,7 @@ To prepare the new server:
|
|||
[SSH host keys](https://superuser.com/questions/532040/copy-ssh-keys-from-one-server-to-another-server/532079#532079)
|
||||
from the old server to avoid man-in-the-middle attack warnings.
|
||||
See [Manually replicate the primary site's SSH host keys](../administration/geo/replication/configuration.md#step-2-manually-replicate-the-primary-sites-ssh-host-keys) for example steps.
|
||||
1. [Install and configure GitLab](https://about.gitlab.com/install) except
|
||||
1. [Install and configure GitLab](https://about.gitlab.com/install/) except
|
||||
[incoming email](../administration/incoming_email.md):
|
||||
1. Install GitLab.
|
||||
1. Configure by copying `/etc/gitlab` files from the old server to the new server, and update as necessary.
|
||||
|
|
|
|||
|
|
@ -32,7 +32,7 @@ Although SPDY is enabled in Omnibus installations, CRIME relies on compression
|
|||
|
||||
## Nessus
|
||||
|
||||
The Nessus scanner, [reports a possible CRIME vulnerability](https://www.tenable.com/plugins/index.php?view=single&id=62565) in GitLab
|
||||
The Nessus scanner, [reports a possible CRIME vulnerability](https://www.tenable.com/plugins/nessus/62565) in GitLab
|
||||
similar to the following format:
|
||||
|
||||
```plaintext
|
||||
|
|
@ -59,7 +59,7 @@ vulnerability.
|
|||
## References
|
||||
|
||||
- NGINX ["Module `ngx_http_spdy_module`"](https://nginx.org/en/docs/http/ngx_http_spdy_module.html)
|
||||
- Tenable Network Security, Inc. ["Transport Layer Security (TLS) Protocol CRIME Vulnerability"](https://www.tenable.com/plugins/index.php?view=single&id=62565)
|
||||
- Tenable Network Security, Inc. ["Transport Layer Security (TLS) Protocol CRIME Vulnerability"](https://www.tenable.com/plugins/nessus/62565)
|
||||
- Wikipedia contributors, ["CRIME"](https://en.wikipedia.org/wiki/CRIME) Wikipedia, The Free Encyclopedia
|
||||
|
||||
<!-- ## Troubleshooting
|
||||
|
|
|
|||
|
|
@ -1991,7 +1991,7 @@ This will result in the rename of the sub-chart: `gitlab/task-runner` to `gitlab
|
|||
|
||||
Planned removal: GitLab <span class="removal-milestone">15.6</span> (2022-11-22)
|
||||
|
||||
With the general availability of Gitaly Cluster ([introduced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/)), we have deprecated development (bugfixes, performance improvements, etc) for NFS for Git repository storage in GitLab 14.0. We will continue to provide technical support for NFS for Git repositories throughout 14.x, but we will remove all support for NFS on November 22, 2022. This was originally planned for May 22, 2022, but in an effort to allow continued maturity of Gitaly Cluster, we have chosen to extend our deprecation of support date. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support.html#gitaly-and-nfs) for further information.
|
||||
With the general availability of Gitaly Cluster ([introduced in GitLab 13.0](https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-released/)), we have deprecated development (bugfixes, performance improvements, etc) for NFS for Git repository storage in GitLab 14.0. We will continue to provide technical support for NFS for Git repositories throughout 14.x, but we will remove all support for NFS on November 22, 2022. This was originally planned for May 22, 2022, but in an effort to allow continued maturity of Gitaly Cluster, we have chosen to extend our deprecation of support date. Please see our official [Statement of Support](https://about.gitlab.com/support/statement-of-support/#gitaly-and-nfs) for further information.
|
||||
|
||||
Gitaly Cluster offers tremendous benefits for our customers such as:
|
||||
|
||||
|
|
|
|||
|
|
@ -446,12 +446,13 @@ To learn what happens when you sort by priority or label priority, see
|
|||
|
||||
## Real-time changes to labels
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/241538) in GitLab 14.10 with a [feature flag](../../administration/feature_flags.md) named `realtime_labels`, disabled by default.
|
||||
> - [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/241538) in GitLab 14.10 with a [feature flag](../../administration/feature_flags.md) named `realtime_labels`, disabled by default.
|
||||
> - [Enabled on GitLab.com](https://gitlab.com/gitlab-org/gitlab/-/issues/357370#note_991987201) in GitLab 15.1.
|
||||
|
||||
FLAG:
|
||||
On self-managed GitLab, by default this feature is not available. To make it available, ask an
|
||||
administrator to [enable the feature flag](../../administration/feature_flags.md) named `realtime_labels`.
|
||||
On GitLab.com, this feature is unavailable.
|
||||
On GitLab.com, this feature is available.
|
||||
|
||||
Changed labels are immediately visible to other users, without refreshing the page, on the following:
|
||||
|
||||
|
|
|
|||
|
|
@ -95,7 +95,7 @@ module QA
|
|||
end
|
||||
|
||||
def disable_initialize_with_readme
|
||||
uncheck_element(:initialize_with_readme_checkbox)
|
||||
uncheck_element(:initialize_with_readme_checkbox, true)
|
||||
end
|
||||
end
|
||||
end
|
||||
|
|
|
|||
|
|
@ -382,9 +382,10 @@ module Trigger
|
|||
private
|
||||
|
||||
def ops_gitlab_client
|
||||
# No access token is needed here - we only use this client to trigger pipelines,
|
||||
# and the trigger token authenticates the request to the pipeline
|
||||
@ops_gitlab_client ||= Gitlab.client(
|
||||
endpoint: 'https://ops.gitlab.net/api/v4',
|
||||
private_token: ENV['GITLABCOM_DATABASE_TESTING_ACCESS_TOKEN']
|
||||
endpoint: 'https://ops.gitlab.net/api/v4'
|
||||
)
|
||||
end
|
||||
|
||||
|
|
|
|||
|
|
@ -13,6 +13,7 @@ import { createAlert } from '~/flash';
|
|||
import { s__ } from '~/locale';
|
||||
import { getIdFromGraphQLId } from '~/graphql_shared/utils';
|
||||
import { updateHistory } from '~/lib/utils/url_utility';
|
||||
import { upgradeStatusTokenConfig } from 'ee_else_ce/runner/components/search_tokens/upgrade_status_token_config';
|
||||
|
||||
import RunnerTypeTabs from '~/runner/components/runner_type_tabs.vue';
|
||||
import RunnerFilteredSearchBar from '~/runner/components/runner_filtered_search_bar.vue';
|
||||
|
|
@ -37,7 +38,7 @@ import {
|
|||
RUNNER_PAGE_SIZE,
|
||||
I18N_EDIT,
|
||||
} from '~/runner/constants';
|
||||
import groupRunnersQuery from '~/runner/graphql/list/group_runners.query.graphql';
|
||||
import groupRunnersQuery from 'ee_else_ce/runner/graphql/list/group_runners.query.graphql';
|
||||
import groupRunnersCountQuery from 'ee_else_ce/runner/graphql/list/group_runners_count.query.graphql';
|
||||
import GroupRunnersApp from '~/runner/group_runners/group_runners_app.vue';
|
||||
import { captureException } from '~/runner/sentry_utils';
|
||||
|
|
@ -196,6 +197,7 @@ describe('GroupRunnersApp', () => {
|
|||
type: PARAM_KEY_STATUS,
|
||||
options: expect.any(Array),
|
||||
}),
|
||||
upgradeStatusTokenConfig,
|
||||
]);
|
||||
});
|
||||
|
||||
|
|
|
|||
|
|
@ -882,7 +882,6 @@ RSpec.describe Trigger do
|
|||
let(:ops_gitlab_client) { double('ops_gitlab_client') }
|
||||
|
||||
let(:downstream_gitlab_client_endpoint) { ops_api_endpoint }
|
||||
let(:downstream_gitlab_client_token) { ops_api_token }
|
||||
let(:downstream_gitlab_client) { ops_gitlab_client }
|
||||
|
||||
let(:ref) { 'master' }
|
||||
|
|
@ -890,7 +889,6 @@ RSpec.describe Trigger do
|
|||
|
||||
let(:env) do
|
||||
super().merge(
|
||||
'GITLABCOM_DATABASE_TESTING_ACCESS_TOKEN' => ops_api_token,
|
||||
'GITLABCOM_DATABASE_TESTING_TRIGGER_TOKEN' => trigger_token
|
||||
)
|
||||
end
|
||||
|
|
@ -902,6 +900,13 @@ RSpec.describe Trigger do
|
|||
private_token: com_api_token
|
||||
)
|
||||
.and_return(com_gitlab_client)
|
||||
|
||||
allow(Gitlab).to receive(:client)
|
||||
.with(
|
||||
endpoint: downstream_gitlab_client_endpoint
|
||||
)
|
||||
.and_return(downstream_gitlab_client)
|
||||
|
||||
allow(com_gitlab_client).to receive(:merge_request_notes)
|
||||
.with(
|
||||
env['CI_PROJECT_PATH'],
|
||||
|
|
|
|||
Loading…
Reference in New Issue