Add latest changes from gitlab-org/gitlab@master
This commit is contained in:
GitLab Bot
parent
10b5e85b50
commit
ac1b601e58
|
|
@ -27,11 +27,13 @@
|
|||
- echo "${CI_ENVIRONMENT_URL}"
|
||||
- cd qa
|
||||
script:
|
||||
- |
|
||||
bin/test "${QA_SCENARIO}" "${CI_ENVIRONMENT_URL}" \
|
||||
-- \
|
||||
--color --format documentation \
|
||||
--format RspecJunitFormatter --out tmp/rspec.xml
|
||||
- qa_run_status=0
|
||||
- bin/test "${QA_SCENARIO}" "${CI_ENVIRONMENT_URL}" -- --color --format documentation --format RspecJunitFormatter --out tmp/rspec.xml || qa_run_status=$?
|
||||
- if [ ${qa_run_status} -ne 0 ]; then
|
||||
release_sha=$(echo "${CI_MERGE_REQUEST_SOURCE_BRANCH_SHA:-${CI_COMMIT_SHA}}" | cut -c1-11);
|
||||
echo "Errors can be found at https://sentry.gitlab.net/gitlab/gitlab-review-apps/releases/${release_sha}/all-events/.";
|
||||
fi
|
||||
- exit ${qa_run_status}
|
||||
artifacts:
|
||||
paths:
|
||||
- qa/tmp
|
||||
|
|
|
|||
|
|
@ -22,7 +22,7 @@ Parameters:
|
|||
| `id` | integer/string| yes | The ID or [URL-encoded path of the project](index.md#namespaced-path-encoding) owned by the authenticated user|
|
||||
| `order_by` | string | no | Return tags ordered by `name` or `updated` fields. Default is `updated` |
|
||||
| `sort` | string | no | Return tags sorted in `asc` or `desc` order. Default is `desc` |
|
||||
| `search` | string | no | Return list of tags matching the search criteria. You can use `^term` and `term$` to find tags that begin and end with `term` respectively. |
|
||||
| `search` | string | no | Return list of tags matching the search criteria. You can use `^term` and `term$` to find tags that begin and end with `term` respectively. No other regular expressions are supported. |
|
||||
|
||||
```json
|
||||
[
|
||||
|
|
|
|||
|
|
@ -55,6 +55,98 @@ import issueExtension from '~/vue_merge_request_widget/extensions/issues';
|
|||
registerExtension(issueExtension);
|
||||
```
|
||||
|
||||
## Polling
|
||||
|
||||
To enable polling for an extension, an options flag needs to be present in the extension.
|
||||
For example:
|
||||
|
||||
```javascript
|
||||
export default {
|
||||
//...
|
||||
enablePolling: true
|
||||
};
|
||||
```
|
||||
|
||||
This flag tells the base component that we should poll the `fetchCollapsedData()`
|
||||
defined in the extension. Polling stops if the response has data or if an error is present.
|
||||
|
||||
When writing the logic for `fetchCollapsedData()`, a complete Axios response must be returned
|
||||
from the method, due to the polling utility needing data like polling headers.
|
||||
Otherwise, polling does not work correctly.
|
||||
|
||||
```javascript
|
||||
export default {
|
||||
//...
|
||||
enablePolling: true
|
||||
methods: {
|
||||
fetchCollapsedData() {
|
||||
return axios.get(this.reportPath)
|
||||
},
|
||||
},
|
||||
};
|
||||
```
|
||||
|
||||
Most of the time the data returned from the extension's endpoint is not in the format
|
||||
the UI needs. We must format the data before setting the collapsed data in the base component.
|
||||
|
||||
If the computed property `summary` can rely on `collapsedData`, you can format the data
|
||||
when `fetchFullData` is invoked:
|
||||
|
||||
```javascript
|
||||
export default {
|
||||
//...
|
||||
enablePolling: true
|
||||
methods: {
|
||||
fetchCollapsedData() {
|
||||
return axios.get(this.reportPath)
|
||||
},
|
||||
fetchFullData() {
|
||||
return Promise.resolve(this.prepareReports());
|
||||
},
|
||||
// custom method
|
||||
prepareReports() {
|
||||
// unpack values from collapsedData
|
||||
const { new_errors, existing_errors, resolved_errors } = this.collapsedData;
|
||||
|
||||
// perform data formatting
|
||||
|
||||
return [...newErrors, ...existingErrors, ...resolvedErrors]
|
||||
}
|
||||
},
|
||||
};
|
||||
```
|
||||
|
||||
If the extension relies on `collapsedData` being formatted before invoking `fetchFullData()`,
|
||||
then `fetchCollapsedData()` must return the Axios response as well as the formatted data:
|
||||
|
||||
```javascript
|
||||
export default {
|
||||
//...
|
||||
enablePolling: true
|
||||
methods: {
|
||||
fetchCollapsedData() {
|
||||
return axios.get(this.reportPath).then(res => {
|
||||
const formattedData = this.prepareReports(res.data)
|
||||
|
||||
return {
|
||||
...res,
|
||||
data: formattedData,
|
||||
}
|
||||
})
|
||||
},
|
||||
// custom method
|
||||
prepareReports() {
|
||||
// unpack values from collapsedData
|
||||
const { new_errors, existing_errors, resolved_errors } = this.collapsedData;
|
||||
|
||||
// perform data formatting
|
||||
|
||||
return [...newErrors, ...existingErrors, ...resolvedErrors]
|
||||
}
|
||||
},
|
||||
};
|
||||
```
|
||||
|
||||
## Fetching errors
|
||||
|
||||
If `fetchCollapsedData()` or `fetchFullData()` methods throw an error:
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ type: reference, howto
|
|||
|
||||
# Browser Performance Testing **(PREMIUM)**
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/3507) in [GitLab Premium](https://about.gitlab.com/pricing/) 10.3.
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/3507) in GitLab 10.3.
|
||||
|
||||
If your application offers a web interface and you're using
|
||||
[GitLab CI/CD](../../../ci/index.md), you can quickly determine the rendering performance
|
||||
|
|
|
|||
|
|
@ -7,7 +7,7 @@ type: reference, howto
|
|||
|
||||
# Load Performance Testing **(PREMIUM)**
|
||||
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/10683) in [GitLab Premium](https://about.gitlab.com/pricing/) 13.2.
|
||||
> [Introduced](https://gitlab.com/gitlab-org/gitlab/-/issues/10683) in GitLab 13.2.
|
||||
|
||||
With Load Performance Testing, you can test the impact of any pending code changes
|
||||
to your application's backend in [GitLab CI/CD](../../../ci/index.md).
|
||||
|
|
|
|||
|
|
@ -11,21 +11,21 @@ description: "Test your code and display reports in merge requests"
|
|||
GitLab has the ability to test the changes included in a feature branch and display reports
|
||||
or link to useful information directly from merge requests:
|
||||
|
||||
| Feature | Description |
|
||||
|--------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| [Accessibility Testing](accessibility_testing.md) | Automatically report A11y violations for changed pages in merge requests. |
|
||||
| [Browser Performance Testing](browser_performance_testing.md) **(PREMIUM)** | Quickly determine the browser performance impact of pending code changes. |
|
||||
| [Load Performance Testing](load_performance_testing.md) **(PREMIUM)** | Quickly determine the server performance impact of pending code changes. |
|
||||
| [Code Quality](code_quality.md) | Analyze your source code quality using the [Code Climate](https://codeclimate.com/) analyzer and show the Code Climate report right in the merge request widget area. |
|
||||
| [Display arbitrary job artifacts](../../../ci/yaml/index.md#artifactsexpose_as) | Configure CI pipelines with the `artifacts:expose_as` parameter to directly link to selected [artifacts](../../../ci/pipelines/job_artifacts.md) in merge requests. |
|
||||
| [GitLab CI/CD](../../../ci/index.md) | Build, test, and deploy your code in a per-branch basis with built-in CI/CD. |
|
||||
| [Unit test reports](../../../ci/unit_test_reports.md) | Configure your CI jobs to use Unit test reports, and let GitLab display a report on the merge request so that it's easier and faster to identify the failure without having to check the entire job log. |
|
||||
| [License Compliance](../../compliance/license_compliance/index.md) **(ULTIMATE)** | Manage the licenses of your dependencies. |
|
||||
| [Metrics Reports](../../../ci/metrics_reports.md) **(PREMIUM)** | Display the Metrics Report on the merge request so that it's fast and easy to identify changes to important metrics. |
|
||||
| [Multi-Project pipelines](../../../ci/pipelines/multi_project_pipelines.md) **(PREMIUM)** | When you set up GitLab CI/CD across multiple projects, you can visualize the entire pipeline, including all cross-project interdependencies. |
|
||||
| [Pipelines for merge requests](../../../ci/pipelines/merge_request_pipelines.md) | Customize a specific pipeline structure for merge requests in order to speed the cycle up by running only important jobs. |
|
||||
| [Pipeline Graphs](../../../ci/pipelines/index.md#visualize-pipelines) | View the status of pipelines within the merge request, including the deployment process. |
|
||||
| [Test Coverage visualization](test_coverage_visualization.md) | See test coverage results for merge requests, within the file diff. |
|
||||
| Feature | Description |
|
||||
|----------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
||||
| [Accessibility Testing](accessibility_testing.md) | Automatically report A11y violations for changed pages in merge requests. |
|
||||
| [Browser Performance Testing](browser_performance_testing.md) | Quickly determine the browser performance impact of pending code changes. |
|
||||
| [Load Performance Testing](load_performance_testing.md) | Quickly determine the server performance impact of pending code changes. |
|
||||
| [Code Quality](code_quality.md) | Analyze your source code quality using the [Code Climate](https://codeclimate.com/) analyzer and show the Code Climate report right in the merge request widget area. |
|
||||
| [Display arbitrary job artifacts](../../../ci/yaml/index.md#artifactsexpose_as) | Configure CI pipelines with the `artifacts:expose_as` parameter to directly link to selected [artifacts](../../../ci/pipelines/job_artifacts.md) in merge requests. |
|
||||
| [GitLab CI/CD](../../../ci/index.md) | Build, test, and deploy your code in a per-branch basis with built-in CI/CD. |
|
||||
| [Unit test reports](../../../ci/unit_test_reports.md) | Configure your CI jobs to use Unit test reports, and let GitLab display a report on the merge request so that it's easier and faster to identify the failure without having to check the entire job log. |
|
||||
| [License Compliance](../../compliance/license_compliance/index.md) | Manage the licenses of your dependencies. |
|
||||
| [Metrics Reports](../../../ci/metrics_reports.md) | Display the Metrics Report on the merge request so that it's fast and easy to identify changes to important metrics. |
|
||||
| [Multi-Project pipelines](../../../ci/pipelines/multi_project_pipelines.md) | When you set up GitLab CI/CD across multiple projects, you can visualize the entire pipeline, including all cross-project interdependencies. |
|
||||
| [Pipelines for merge requests](../../../ci/pipelines/merge_request_pipelines.md) | Customize a specific pipeline structure for merge requests in order to speed the cycle up by running only important jobs. |
|
||||
| [Pipeline Graphs](../../../ci/pipelines/index.md#visualize-pipelines) | View the status of pipelines within the merge request, including the deployment process. |
|
||||
| [Test Coverage visualization](test_coverage_visualization.md) | See test coverage results for merge requests, within the file diff. |
|
||||
|
||||
## Security Reports **(ULTIMATE)**
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue