Hola Mundo, Hallo Welt! We are incredibly excited to announce the start of our journey to internationalise GitLab and would love your support to make this happen as broadly and quickly as possible.
Starting in 9.2, we have added the framework and infrastructure to translate GitLab into any language. To validate our technology decisions, we've only translated a single page (Cycle Analytics) into Spanish and German. In 9.3 and subsequent releases, we will continue to add more languages and more pages. If you want to help out, please take a look at our contributor Guidelines.
To change your language, visit your Settings page by clicking on yourself in the top right corner.
For most projects, developers want to have their GitLab CI/CD pipelines executed for every new commit, ensuring any changes are built, tested and deployed. In some cases however, a developer needs extra control and would instead like a pipeline to execute on a specific schedule.
Today with GitLab 9.2, pipelines can now be configured to run when and how often you need them to. Generating daily or weekly builds, performing maintenance, or even validating external dependencies can be easily configured to run on your schedule.
This replaces the alpha UI for Scheduled Pipelines Triggers.
We want to make GitLab the best cloud native development tool, so making it easy to get started on Kubernetes is important. With GitLab 9.2, we are proud to announce that we have released official GitLab Helm charts.
Helm is the official Kubernetes package management tool allowing users to easily deploy, upgrade, and configure apps in their clusters. GitLab and Kubernetes go great together with easy autoscaling CI, app autodeployments to your clusters and everything else shown in the Idea to Production video - out of the box, minimal setup!
For most companies, determining the performance impact of a specific merge can be a challenge. Often performance data is contained within a separate tool, which the development team may not even have access to. At GitLab we want to make sure developers get feedback on every change they ship, and we are taking a big step forward today with our Prometheus integration.
With GitLab 9.2, we now automatically display the change in memory consumption after a deploy directly on its merge request. This allows the developer to quickly and easily determine if there are any performance changes and investigate as soon as possible, all within their usual daily workflow. In future releases, we will analyze additional metrics as well. Building responsive and delightful apps is everyone's responsibility!
Since version 9.0, GitLab ships with support for Disaster Recovery in Alpha as part of GitLab Geo. We are committed to making Disaster Recovery better on every release, and GitLab 9.2 is no exception. Today we are improving the UX of the Disaster Recovery feature, with more obvious controls and more reporting on what’s going on during the replication process.
Finally, we had also made improvements to the repositories synchronization mechanism, and now it is smart enough to resync broken repositories due to a failed sync or repositories that have been recently updated on the primary node but have been synced some time ago on the secondaries.
The issue page in GitLab is a key area of collaboration, with you and your team constantly editing content. When viewing an issue page, the title and description now refresh automatically (in response to someone else changing it) to keep up with your workflows. The issue page itself doesn’t reload. So you can simply leave a browser tab open to an issue you are interested in, and you’ll always be seeing the latest information. Even the browser tab title refreshes by itself.
We've also added a system note when an issue description is edited, so you can always scroll through the comment thread and see who made any changes, and when. Even adding comments now feels more responsive. And if you edit an existing comment, that comment will also be automatically refreshed on any other user's screen who happens to have the same issue open.
You can now easily remove filters in the search bar for issues and merge requests with a simple mouse click.
We've also styled the labels within the filter bar to match the colors they have elsewhere.
We are bringing more advanced search capabilities leveraging Elasticsearch integration. Provided you have configured Elasticsearch, you can search for exact phrases using double quotes, search for content ignoring the order of search terms, match partial words, and other syntax. (Note that this applies to the search box in the top right corner throughout GitLab, and not the search bar inside issue lists and merge request lists.)
You can now also search globally across all wikis in your instance, again requiring and powered by Elasticsearch.