GitLab 11.3 arrived: Built-in Maven repositories & many more improvements for Java developers
Java, Java news all around! GitLab 11.3 is here and it brings some major improvements for Java developers, including built-in Maven repositories, Code Owners, and epic forecasting. Let’s dig in!
It has definitely been a Java month all around and GitLab couldn’t be missing from the party!
Getting things done is still GitLab’s main principle, and the latest Gitlab release 11.3 comes with built-in Maven repositories and a bunch of other features that will make coding for Java developers more efficient than ever.
Let’s take a closer look at what’s in the new Gitlab release.
Maven repository – GitLab 11.3 offers Maven repositories built directly into GitLab. Developers of lower-level services can now publish their packaged libraries to their project’s Maven repository. They can then share a simple XML snippet with other teams looking to utilize that library, and Maven and GitLab will do the rest.
Interactive web terminals for Shell and Kubernetes Runners – Ability to connect to a running or completed job and manually run commands to better understand what’s happening in the system.
Improve includes in
.gitlab-ci.yml for reusing scripts – Flexible, powerful approach for code reuse in templates using YAML
SEE ALSO: How well do you know your GitLab trivia?
Include private contributions in user contribution graph – Contributions to private projects are now displayed in the contribution graph and contributions of this day if you enable this setting for your profile.
Redesigned project overview – Updated the UI of the project overview page to allow for a better experience when exploring projects.
Protected Environments – Operators obtain full control around which person, group, or account is allowed to deploy to a given environment, allowing further protection and safety of sensitive environments.
Code Owners – Support for assigning code owners to files to indicate the team members responsible for code in your project. Code owners are assigned using a file named
CODEOWNERS, a format similar to
[gitattributes](https://git-scm.com/docs/gitattributes), and are listed below the commit details when viewing a file in GitLab.
Epic forecasting with integrated milestone dates – Switch from the fixed value for either of the dates, to a dynamic value called
All about the little things
Among these big changes are a few minor tweaks that will make your experience smoother and better. Since the list is pretty long, we are taking only but a quick look at these improvements in Gitlab 11.3. Make sure you check out the official release notes for further details.
- New epic event as custom notification
- Quick action to add issue to epic (from issues)
- Allow self-approval of merge requests
- Display repository languages on project overview
- Custom file templates for self-managed instances
- Define project name when creating a new project
- File templates in the Web IDE
- Store Wiki uploads in the Wiki repository
- Filter webhook push events by branch
- SAST support for Groovy
- Alerts for library metrics
- Auto DevOps enabled by default
- Geo improvements
- Automatically disable Auto DevOps for project upon first pipeline failure
- Gitaly v1.0
- GitLab Runner 11.3
- List of open source software components used by GitLab now available online
- Omnibus improvements
- Performance improvements
In order to upgrade to GitLab 11.3 from the latest 11.2 version, no downtime is required. To upgrade without downtime, you should consult the documentation on downtimeless upgrades.
On other news, with GitLab 11.4, that’s due on October 22, 2018, support for Docker versions before 1.12 (API version 1.24) will be deprecated in line with Docker’s latest version recommendation guidance. Beyond the 11.4 release these older versions will no longer be officially supported and could stop working at any time.