days
-3
-9
hours
-1
-3
minutes
-3
-9
seconds
-4
-2
search
Godsent?

GitLab 9.2 brings Multiple Assignees For Issues and more

Gabriela Motroc
GitLab 9.2

© Shutterstock / Illin Denis

GitLab 9.2 brings Multiple Assignees For Issues to streamline collaboration and allow the shared responsibilities to be clearly displayed. Let’s have a look at all that GitLab 9.2 has to offer.

GitLab aims to “allow everyone to contribute whether their teams are large or small, remote or in a single room.” Sometimes, it might happen that multiple people (such as a front-end developer, back-end developer, UX designer, QA tester, and product manager) must work on the same issue together.

This is where GitLab 9.2 comes into play: thanks to the newly introduced Multiple Assignees for Issues, these shared responsibilities are clearly displayed. “All assignees are shown across our workflows and receive notifications as they would before, simplifying communication and ownership,” according to the blog post announcing 9.2.

Furthermore, Cycle Analytics is now available in Spanish and German. Plus, developers can now configure pipelines to run on a specific schedule automating repetitive tasks like the creation of nightly builds, maintenance, or validation of external dependencies.

Multiple Assignees for Issues

As of now, you can assign as many users as you want to a given issue. Every one of the assignees is a first class citizen and receives the same notifications as before. Multiple assignees can now be seen in the issue list and on issue boards, and they will be able to track their association with the issue in their dashboard.

Just a heads up: As part of this change, the assignee_id parameter in the issues API has been deprecated so the assignee_ids should be used instead. Also, the assignee object in the JSON response has been deprecated, so the assignees array should be used instead.

GitLab 9.2: Multiple Assignees for Issues

Read more about Multiple Assignees for Issues here.

Pipeline schedules

According to the blog post, developers generally want “to have their GitLab CI/CD pipelines executed for every new commit, ensuring any changes are built, tested and deployed.” However, these are some cases in which they “need extra control and would instead like a pipeline to execute on a specific schedule.”

As of now, pipelines can now be configured to run when and how often you need them to. As a result, generating daily or weekly builds, performing maintenance, or validating external dependencies can be easily configured to run on your schedule.

Warning: This replaces the alpha UI for Scheduled Pipelines Triggers.

Official GitLab installation on Kubernetes

The GitLab team also released official GitLab Helm (official Kubernetes package management tool) charts.

It appears that GitLab and Kubernetes go together like mac and cheese. If you are not convinced that the benefits of this duo are for you, check out the Idea to Production video.

 

Check out all that GitLab 9.2 has to offer here

Author
Gabriela Motroc
Gabriela Motroc is editor of JAXenter.com and JAX Magazine. Before working at Software & Support Media Group, she studied International Communication Management at the Hague University of Applied Sciences.

Leave a Reply

Be the First to Comment!

avatar
400
  Subscribe  
Notify of