DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones AWS Cloud
by AWS Developer Relations
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Partner Zones
AWS Cloud
by AWS Developer Relations
Building Scalable Real-Time Apps with AstraDB and Vaadin
Register Now

Trending

  • How to LINQ Between Java and SQL With JPAStreamer
  • 13 Impressive Ways To Improve the Developer’s Experience by Using AI
  • Tactics and Strategies on Software Development: How To Reach Successful Software [Video]
  • Exploring the Capabilities of eBPF

Trending

  • How to LINQ Between Java and SQL With JPAStreamer
  • 13 Impressive Ways To Improve the Developer’s Experience by Using AI
  • Tactics and Strategies on Software Development: How To Reach Successful Software [Video]
  • Exploring the Capabilities of eBPF
  1. DZone
  2. Testing, Deployment, and Maintenance
  3. Deployment
  4. GitLab Release 9.1: Three Big Additions

GitLab Release 9.1: Three Big Additions

With the April release of GitLab 9.1, users of the service can now benefit from canary deployments, service desk functionality, and burn-down charts.

John Vester user avatar by
John Vester
CORE ·
May. 05, 17 · News
Like (4)
Save
Tweet
Share
64.66K Views

Join the DZone community and get the full member experience.

Join For Free

The team at GitLab has been busy since I last spoke to Job van der Voort during a DZone interview I participated in just a few weeks ago regarding GitLab 9.0.  In a very short time, the following items have been included in the 9.1 release:

  • Canary deployments.

  • Service desk functionality.

  • Burn-down charts.

Canary Deployments

For those who are not familiar with the concept of canary deployments, think about the idea of rolling out a new set of features to a limited audience - with the ability to roll back to the prior release, if anything unexpected happens. Taking this approach allows the features to be utilized, but not at the price of impacting the entire user base. This concept is referred to as canary deployments.

Canary deployments are now part of GitLab with release 9.1.  The screenshot below provides an illustration of five (first on left side, with yellow indicator) canary deployments.

Image title

To get started quickly, GitLab recommends using the Autodeploy template, as referenced in the Canary deployments section.

Service Desk Functionality

Another welcome feature with GitLab 9.1 is the ability to expose an email address, which will automatically generate a confidential issue when email is sent to the unique address. See the screenshot below for an example:

Image title

Sending an email to the smcgivern@example.com with a subject of "I need some help, please" and a body of "Hi, I'm having some issues with your product. Can you help please?" will generate the issue shown in the screen shot above.

The service desk functionality can be enabled from your project's settings.  Upon being enabled, a unique email address will be provided.

Burn-Down Charts

The last item I wanted to focus on with the GitLab 9.1 update is the inclusion of burn-down charts in the issue section of the GitLab service. For teams tracking issues for a release cycle, having a burn-down chart can provide a visual that teams can reference in keeping pace with their planned workload.

A screenshot of the burn-down charts is shown below:

Image title


I continue to be impressed with the features and functionality the team at GitLab has revealed lately and am looking forward to future additions that Job referenced during our interview in April.

Have a really great day!

GitLab Release (agency)

Opinions expressed by DZone contributors are their own.

Trending

  • How to LINQ Between Java and SQL With JPAStreamer
  • 13 Impressive Ways To Improve the Developer’s Experience by Using AI
  • Tactics and Strategies on Software Development: How To Reach Successful Software [Video]
  • Exploring the Capabilities of eBPF

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com

Let's be friends: