GITLAB CI 2.0 and other news

Hi everyone!

Today we released new version of GitLab CI.

The most significant change is replacing library for background jobs. So now instead resque we use sidekiq.

Running builds:

Earlier you have one resque worker which run one build at time. Even if you has 3 projects – only one is running at same time.

With migration to sidekiq we changed logic a bit. So now application can run one build per project simultaneously.

If you have more then one projects running with GitLab CI – it will save you a lot of time.

Scheduled builds:

Now scheduled builds are triggered by cron task. This task starts every hour and check for scheduled builds.

Links:

Update from 1.x to 2.0

Setup GitLab CI

Other news:

GitLab v4.1 will be released at Jan 22th.

We replaced resque with sidekiq in GitLab too. Now push events are processed much faster. Also we added a Public Area, fixed a lot of bugs and improved perfomance of application. See CHANGELOG for full list of changes.

According to gitlab_meta gem amount of GitLab v4.0 installations reached 9k. It a really good news for us. Thank you for using our software.

GITLAB 4.0 released

Hi everyone!

Finally we released GITLAB v4.0.0!

There are a lot of changes so we introduce you to the important one

Application behaviour changes:

• New projects will be namespaced (ex. gitlab/vagrant )
• Every group got own directory in gitolite
• All projects of group will be moved under group directory ( git remote should be updated )
• Projects w/o groups will stay with same remote
• User got username ( For existsing users it will be generated based on email )
• User create project under his username ( ex. randx/my-project )
• User can change username. All projects under his username will be moved
• Group got owner
• Owner can create projects within group
• Owner can access every project within a group
• Admin can transfer any project from one namespace(group, user, global) to another
• Group or user is a namespace for project. Owner of namespace is an owner of project

Other changes

• Better PostgreSQL support
• Added email notificatino on project move
• Fixed email notification on issue close/reopen
• Reorganized settings
• Fixed commits compare
• Update the UI to allow downloading Patch or Diff for Commit, MR
• Milestones can be closed now. Milestone stays open unless you close it
• Show comment events on dashboard
• Quick add team members via group#people page
• UI improvements
• In admin area projects, users and groups sorted alphabetically
• Issue management page on dashboard improved
• Better integration with GitLab CI ( requires GitLab CI v1.1.1 )

What we removed in 4.0:

• gitolite 2 support
• SQLite support (I like it but this database got locked when several users use gitlab at once)
• API v2 support (its simply incompatible with namespaced projects)

What should be updated during migration:

• gitlab.yml config
• gitolite post-receive hooks
• permissions on /home/git/repositories/
• python2 symlink

Screenshots:

Dashboard: Merge Request with CI status Files browsing Issues

How to reinstall gitolite with new version

• Reinstall gitolite

How to migrate from sqlite

• Follow this guide

How to install GitLab v4.0.0

• Complete Installation guide (Recommended)
• One-script installer for ubuntu 12.04 x64

How to update a GitLab to v4.0.0

• Update guide for v3.1
• Update guide for v3.0

Some details of upcoming GitLab 4.0 and release date

Release schedule:

• Dec 21..22 – we test 4.0 release candidate
• Dec 22..23 – we will merge master into stable
• Dec 23 – Installation docs is ready. 4.0 is ready for fresh install
• Dec 24 – Updating docs. You will be able to migrate your GitLab instances to 4.0

Important changes:

• New projects will be namespaced (ex. gitlab/vagrant )
• Every group got own directory in gitolite
• All projects of group will be moved under group directory ( git remote should be updated )
• Projects w/o groups will stay with same remote
• User got username ( For existsing users it will be generated based on email )
• User create project under his username ( ex. randx/my-project )
• User can change username. All projects under his username will be moved
• Group got owner
• Owner can create projects within group
• Owner can access every project within a group
• Admin can transfer any project from one namespace(group, user, global) to another
• Group or user is a namespace for project. Owner of namespace is an owner of project

Migration notes:

• Required: replace gitolite hooks
• Required: activate namspaces
• Required: update permissions on /home/git/repositories/
• Strongly recommended: replace gitlab.yml with new one

Today’s releases: GitLab 3.1 and GitLab CI v1.0.1

Hi everyone!

Today is 22th and it means we have released a new version of GitLab today.

Also as a bonus we pushed a v1.0.1 version of GitLab CI

Few screens:

Event Filter GitLab CI intergration for Merge Requests Better image compare diff

Links

CHANGELOG

Update from 3.0

How to Install

Continuous integration server from GitLab

Hi everyone!

Today I’d like to share a new software crafted by me and Valeriy Sizov.

Its more than year since we released first version of GitLab. And we dont want to stop on it.

We wish to have a continuous integration server closely integrated with GitLab.

And today we announced another FOSS software for developers. Its GitLab CI.

Source Code

GitLab CI is based on Ruby on Rails and Resque/Redis and

GitLab CI supports only git SCM.

GitLab CI requires present of GitLab instance with web hooks setup to make builds automatically

How it works:

1. First of all you need to setup GitLab CI on VPS or any linux server
2. Then you clone projects you want to test and setup test environment
3. Next step is just add projects to GitLab CI via web UI
4. Add just copy HTTP POST url provided by GitLab CI to your GitLab web hooks
5. When you push code to GitLab web hook will trigger CI to make a build

Source Code