diff options
Diffstat (limited to 'data/whats_new/202011230001_13_06.yml')
| -rw-r--r-- | data/whats_new/202011230001_13_06.yml | 40 |
1 files changed, 20 insertions, 20 deletions
diff --git a/data/whats_new/202011230001_13_06.yml b/data/whats_new/202011230001_13_06.yml index 1e47bcca0ec..effaa243812 100644 --- a/data/whats_new/202011230001_13_06.yml +++ b/data/whats_new/202011230001_13_06.yml @@ -1,6 +1,6 @@ --- -- title: Auto Deploy to EC2 - body: | +- name: Auto Deploy to EC2 + description: | Auto DevOps has been expanded to support deployments to Amazon Web Services. You can now deploy to AWS Cloud Compute (EC2) and take advantage of Auto DevOps, even without Kubernetes. To enable this workflow, you must enable Auto DevOps and define the AWS-typed environment variables `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, and `AWS_DEFAULT_REGION`. This allows you to provision your own infrastructure by leveraging the [AWS CloudFormation API](https://aws.amazon.com/cloudformation/). @@ -9,26 +9,26 @@ stage: Release self-managed: true gitlab-com: true - packages: [Free, Premium, Ultimate] - url: https://docs.gitlab.com/ee/ci/cloud_deployment/#custom-build-job-for-auto-devops + available_in: [Free, Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/ci/cloud_deployment/#custom-build-job-for-auto-devops image_url: https://img.youtube.com/vi/4B-qSwKnacA/hqdefault.jpg published_at: 2020-11-22 release: 13.6 -- title: Display Code Quality severity ratings - body: | +- name: Display Code Quality severity ratings + description: | The Code Quality feature in GitLab is great at showing what quality violations exist in a project or are changing in the merge request. However, understanding which of those violations is the most important is not clear in the GitLab interface today. With the Full Code Quality Report and merge request widget, now you can see the severity rating. This makes it easy for you to understand which code quality violations are most important to resolve before merging and reduces the technical debt in your project. stage: Verify self-managed: true gitlab-com: true - packages: [Free, Premium, Ultimate] - url: https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html#code-quality-widget + available_in: [Free, Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/user/project/merge_requests/code_quality.html#code-quality-widget image_url: https://about.gitlab.com/images/13_6/code_quality_severity.png published_at: 2020-11-22 release: 13.6 -- title: Display code coverage data for selected projects - body: | +- name: Display code coverage data for selected projects + description: | In 13.4, we released the first iteration of [Code Coverage data for Groups](https://about.gitlab.com/releases/2020/09/22/gitlab-13-4-released/#code-coverage-data-for-all-projects-in-a-group) that enables you to compare the coverage of multiple projects and download the data in a single file from a single screen. However, to analyze the data, you had to open the file to check it manually, and probably imported it into a spreadsheet for further analysis. @@ -39,13 +39,13 @@ stage: Verify self-managed: true gitlab-com: true - packages: [Premium, Ultimate] - url: https://docs.gitlab.com/ee/user/group/repositories_analytics/index.html#latest-project-test-coverage-list + available_in: [Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/user/group/repositories_analytics/index.html#latest-project-test-coverage-list image_url: https://about.gitlab.com/images/13_6/display_selected_coverage_projects_example.png published_at: 2020-11-22 release: 13.6 -- title: Group-level management of project integrations - body: | +- name: Group-level management of project integrations + description: | In GitLab 13.3, we added the ability to [enable an integration across an entire instance](https://about.gitlab.com/releases/2020/08/22/gitlab-13-3-released/#instance-level-project-integration-management-for-external-services). With GitLab 13.6, that feature is being expanded to allow integrations to be managed at the group level as well! Group owners can now add an integration to a group, and that integration will be inherited by all projects under that group. This has the potential for saving massive amounts of time, as many organizations have specific integrations that they want rolled out to every project they create. @@ -58,13 +58,13 @@ stage: Create self-managed: true gitlab-com: true - packages: [Free, Premium, Ultimate] - url: https://docs.gitlab.com/ee/user/admin_area/settings/project_integration_management.html + available_in: [Free, Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/user/admin_area/settings/project_integration_management.html image_url: https://about.gitlab.com/images/13_6/project-integration-inheriting-settings.png published_at: 2020-11-22 release: 13.6 -- title: Milestone Burnup Charts and historically accurate reporting - body: | +- name: Milestone Burnup Charts and historically accurate reporting + description: | A milestone or iteration burndown chart helps track completion progress of total scope, but it doesn't provide insight into how the scope changed during the course of the timebox. Neither has it previously retained historical accuracy regarding how much of the initial committed scope of the milestone or iteration was actually completed. To solve these problems and help teams have better insights into scope creep, milestones and iterations now show a burnup chart that tracks the daily total count and weight of issues added to and completed within a given timebox. @@ -75,8 +75,8 @@ stage: Plan self-managed: true gitlab-com: true - packages: [Premium, Ultimate] - url: https://docs.gitlab.com/ee/user/project/milestones/burndown_and_burnup_charts.html#burnup-charts + available_in: [Premium, Ultimate] + documentation_link: https://docs.gitlab.com/ee/user/project/milestones/burndown_and_burnup_charts.html#burnup-charts image_url: https://about.gitlab.com/images/13_6/burnup-chart.png published_at: 2020-11-22 release: 13.6 |