GitLab is Version Control on your Server. It's like GitHub but Open Source.
Today we announce the release of a new version of GitLab Community Edition (CE) and GitLab Enterprise Edition (EE), and GitLab Continuous Integration (CI) with new features, usability and performance improvements, and bug fixes.
Also we are happy to announce our new free Continuous Integration (CI) service: ci.gitlab.com.
GitLab 7.7
The biggest new features in GitLab Community Edition are the GitHub importer and OAuth support. In addition to the updates from Community Edition, GitLab Enterprise Edition has gained some performance improvements and the ability to change the header logo.
This month's Most Valuable Person (MVP) is Ciro Santilli for sending over 200 merge requests to improve the GitLab code base. Thanks Ciro!
Redesigned navigation
This had been on our minds for a while but we finally decided to redesign the GitLab navigation! We worked closely with our awesome community and hope you love it.
Check it out:
Have a look at the article we wrote about the redesign to get a better understanding of why we did it.
GitHub importer
You can now super quickly import your GitHub projects, issues and all! A single click is all it takes:
Find the importer when creating a new project.
Mention notification level
Getting too much email? Just select the 'Mention' notification level and you will only receive notification emails when people mention you.
OAuth!
Services like Facebook, Twitter, and Google allow you to sign in using their credentials in 3rd party applications, implemented through OAuth.
From now on, GitLab is also an OAuth resource server. This means that you can create 3rd party applications and use your GitLab credentials for authentication!
We can't wait to hear what you'll use it for.
Configure GitLab on the fly through the UI
Finally GitLab admins can change the application settings on the fly without any downtime through our new settings page:
When you start GitLab 7.7 the first time it will import your settings from gitlab.yml. After this initial import the settings in gitlab.yml are ignored.
In the future we'll add more settings to this page, making configuring GitLab even easier.
Don't want to run your own? Use GitLab.com!
You'd rather live in the cloud? Use GitLab.com! It's a completely free GitLab instance hosted and managed by us. It offers (private) repositories, issue tracking, wiki’s and continuous integration. Free!
You don’t have to install anything, just sign up for a free account.
GitLab CI 5.4
On top of all the new feature for GitLab, we're releasing a bunch more for GitLab CI. These features will make testing your code more powerful and more flexible.
OAuth authorization
With GitLab as OAuth resource server, you can now easily link GitLab CI to your GitLab instance, so you don't need to authenticate when switching to CI anymore. Of course, this also works if you've set up LDAP / AD with GitLab.
You can even use this if you authenticated with GitLab through another OAuth provider, such as Twitter or GitHub. This means that it's now much faster and easier to use CI.
Runners for everyone!
Want to add a Runner that runs your tests and scripts to a project? Now you don't need to be an admin to do this anymore. Just install the GitLab Runner package on any machine and use the project token to register the Runner in your instance.
If only we'd be offering some credits to give this a try…(hint: Keep reading!)
Labels for Runners and jobs
Now that you can easily add a group of Runners to your CI instance, we thought it would be very cool to be able to easily run different environments per job.
Now you can add labels to jobs. Only a Runner with that (those) label(s) will pick up up the matching jobs. This way you can run different environments per job, easily.
Project jobs:
Project runners:
Omnibus packages for GitLab Runner
We now offer Omnibus packages for GitLab Runner. No need to download and compile Ruby anymore each time you set up a runner!
The installation instructions for the Runner packages only cover Ubuntu 12.04 and 14.04 at the moment. To be continued!
Continuous Integration (CI) for free
We are happy to offer free CI for private repositories if you bring your own Runner!
Simply add your projects from GitLab.com on ci.gitlab.com and configure the builds script(s). You can use the parallel build feature of GitLab CI and we'll store the build logs and configuration for you.
To run your tests you need to install GitLab Runner on one or more of your instances. Don't have any instances yet? No problem:
In total, we're giving away up to $520,000.- in cloud hosting for people to host their Runner! This is a collaboration with Google Compute Engine and Digital Ocean, we're very grateful for their offer. Did you know they both also offer one-click-installs of GitLab? To claim your credit please see the instructions below.
The credit is a limited time offering but the free CI for private projects on ci.gitlab.com is permanent.
Claim Google Cloud Platform credit
Google Cloud Platform offers $500 in credit for the first 1000 users. To get started, follow the three steps below:
- Go to http://cloud.google.com/startercredit
- Click Apply Now
- Complete the form with code: gitlab
With Cloud Platform you can access application, compute, storage and big data services. You’re now building on the same infrastructure that powers Google.
Claim Digital Ocean credit
DigitalOcean offers $40 in credit for the first 500 users. This is valid only for new DigitalOcean accounts, not for existing users. The offer is valid for two weeks and you can claim up to one promo per person. You need to set up a project on GitLab.com and add it to ci.gitlab.com before you can claim it.
To claim it please fill out this form with your name, email or handle and project url. Once submitted, the GitLab team will email you your unique promo code. If you have any questions about this promotion, please contact the GitLab support team via support.gitlab.com.
Custom header logo (EE only)
For GitLab Enterprise Edition Drew Blessing contributed customer header logo support. There also were fixes for the preview and performance improvements for selectboxes.
Open sign-up by default
From this version on user self-signup is enabled by default. You can still disable this behaviour in the new applications settings page.
Other changes
This release has more improvements, please check out the Changelog to see the all named changes.
Upgrade barometer
There are migrations in this update but they do not take considerable time and should be quick.
If you don't want users to sign up themselves and you have not set this up in gitlab.yml you must ensure this behaviour stays the same. You can do it by adding it to gitlab.rb (Omnibus package) or gitlab.yml (source installation) or the easiest way is to use the new application settings page to do this.
After you upgraded and tested GitLab consider removing the settings that are now in the application settings page from gitlab.rb (Omnibus packages) or gitlab.yml (source installation) to prevent confusion.
Installation
If you are setting up a new GitLab installation please see the installing GitLab page.
Updating
Upgrade instructions for omnibus-gitlab packages can be found in the omnibus-gitlab repository.
If you installed GitLab from source and you have version 6.4.2 or higher you can use the upgrade script. You have to update GitLab Shell to 2.4.1 manually, see point 3 of the upgrade guide.
If you still want to do it manually - see the Update Guide.
Enterprise Edition
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 you to our upgrade and installation services.
We want to hear from you
Enjoyed reading this blog post or have questions or feedback? Share your thoughts by creating a new topic in the GitLab community forum.
Share your feedback