GitLab is open source software to collaborate on code. Today we announce the release of a new version of GitLab Community Edition (CE) and GitLab Enterprise Edition (EE), with new features, usability and performance improvements, and bug fixes. In addition we are releasing GitLab CI 5.2.
GitLab Community Edition 7.5 brings custom git hooks, various performance improvements, API extensions and better GitLab CI support.
In addition to the updates from Community Edition, GitLab Enterprise Edition has gained automatic daily LDAP sync and git hooks to restrict commit authors.
This month's Most Valuable Person (MVP) is Martijn van Bemmel. Martijn is a very productive designer, having created the cool graphics for GitLab 7.0, the MVP Badge, the Golden Gear medal and the various graphics on our site. We really appreciate his enthusiastic contributions, Thanks Martijn!
GitLab now supports custom Git Hooks! This means that you can run anything you want on pre/post-receive and update actions. Please see our documentation for more information.
This has been a much requested feature and has been contributed by Drew Blessing and Jose Kahan.
Thanks Drew and Jose!
The API has been extended and improved in several points:
Thanks to the contribution of Drew Blessing, GitLab now integrates with Atlassian Bamboo CI.
We've added some cool new Git Hooks:
GitLab Enterprise Edition will now automatically sync all LDAP members on a daily basis. You can configure the time that it happens.
LDAP group synchronization in GitLab Enterprise Edition works by GitLab periodically updating the group memberships of active GitLab users. If a GitLab user becomes inactive however, their group memberships in GitLab can start to lag behind the LDAP server group memberships. Starting with GitLab 7.5 Enterprise Edition, GitLab will also update the LDAP group memberships of inactive users, by doing a daily LDAP check for all GitLab users.
Example: John Doe leaves the company and is removed from the LDAP server. At this point he can no longer log in to GitLab 7.4 EE. But because he is no longer active on the GitLab EE server (he cannot log in!), his LDAP group memberships in GitLab no longer get updated, and he stays listed as a group member on the GitLab server.
Now with GitLab 7.5 Enterprise Edition, within 24 hours of John being removed from the LDAP server, his user will also stop being listed as a member of any GitLab groups.
This release has more improvements, please check out the Changelog to see the all named changes.
Upgrading GitLab from 7.4 to 7.5 is an easy upgrade.
If you are using GitLab CI 5.1 or earlier then you need to upgrade your GitLab CI installation to 5.2 at the same time as you upgrade GitLab to 7.5. GitLab 7.5 is incompatible with GitLab CI 5.1 and earlier.
We're proud to release GitLab CI 5.2 together with GitLab 7.5.
GitLab CI 5.2 requires GitLab 7.5.
You can now run parallel builds on GitLab CI. For instance, if you have two or more test suites, you are able to run them at the same time. This can significantly reduce buildtime and therefore speed up your CI process.
If you are setting up a new GitLab installation please see the installing GitLab page.
To run your tests, you need to setup one or more GitLab CI Runners. Runners are quick and easy to setup, please see the runner repository.
Upgrade instructions for omnibus-gitlab packages can be found in the omnibus-gitlab repository.
If you still want to do it manually - see the Update Guide.
Use the omnibus package which includes the latest GitLab CI version or see the update guide.
The mentioned EE only features and things like LDAP group support can be found in GitLab Enterprise Edition. For a complete overview please have a look at the feature list of GitLab EE.
Access to GitLab Enterprise Edition is included with a subscription. No time to upgrade GitLab yourself? A subscription also entitles to our upgrade and installation services.