GitLab 8.0 released with new looks and integrated CI

Easily the biggest change for GitLab to date. CI is now built-in and it's all easier on the eyes.

We also removed the satellites, on which we used to do certain git operations. This frees up space, but also makes merges must more stable and faster.

Let us know if you have any questions or comments.

This looks awesome! I've been playing with it today and have setup a docker instance for doing Android builds on the same (Linux) machine that I've installed Gitlab on. I'm having trouble setting up Xcode/iOS builds on a Mac Mini over ssh and I don't see any specific documentation on that. Is that something you can point me to?

With this release is it necessary to migrate to the built in CI or can we still point at a different gitlab-CI server? We have gitlab running privately in a VPC on AWS but have gitlab-CI running locally (dedicated local server for the manager and runners) so, essentially, merging the two isn't going to be trivial.

Congratulations GitLab team. I've been really thrilled to see the project evolve and I'm super excited to see this update. And I don't even use GitLab :)

@jobvo I remember leaving extremely lengthy UX and feature feedback here on HN a few weeks back - Email followup never happened. I hope you guys considered working on mailing list support in the style of a Google Groups / Discourse UI. It'd go really well with the Mattermost integration (which I'm also really excited to see).

Thanks!

I do still owe you a folllowup! Wanted to push this out first before weaving in new suggestions and feedback. My apologies.

You can now reply to notifications, which already gives you some of that functionality. We're interested in expanding this.

We'll add a feature that allows you to email GitLab to create a new issue in a future release. Shouldn't be far off, now that we laid the groundwork for receiving email.

I really wish Gitlab could create two entities. Gitlab.org and Gitlab.com

Much like how Wordpress is run. Gitlab.com's profits and revenue will be used to fund the continue development of Gitlab.org

For now the Gitlab.org part ( Or the open source development of Gitlab ) is fine. But Gitlab.com seems like a after thought. It should runs like Github, where you actually paid for Storage, Bandwidth etc for a price. Rather then the current price model which is for support only. This makes me feel Gitlab.com is more like a showcase of Gitlab, rather then a properly run services.

Some will bound to come to me, why dont you buy a VPS and set it yourself? Because i dont want the hassle. Should some day Gitlab close or company policy changes i will know there is always a open sources version where you can host it back on site.

It will also means those communities, or organization who refuse to host their code on Github due to lock in reason ( like Ruby ) can switch to Gitlab without ( ideally speaking ) the same hesitation.

Thanks for your suggestion.

I can assure you that our GitLab.com SaaS service is not an afterthought. It is growing so fast that we do have trouble keeping up with that, but we're hiring more people and things are looking up.

BTW We actually used .org and .com in the past for the community and the for-profit sites. We combined everything on .com because that removed a lot of duplication in announcements, information and many other things.

I think I like the menu UI improvements in the screenshots. Those tiny symbols were a major pain for any new user, and it's good to see words next to them now.

But is it possible yet to make the project files show up in the default view for projects? Many user interactions with a project don't go beyond browsing the files, and I wish I could enable GH-style default views.

The text was always there, but is collapsed by choice and on small screens.

It's either Activity or Readme now. I don't think it'd be very hard to add Files to that and don't have major problems with it.

Consider sending a MR or creating an issue [0] to discuss this further.

0: https://gitlab.com/gitlab-org/gitlab-ce/issues

Looks good!

One question though, clicking on any of the files on https://gitlab.com/gitlab-org/gitlab-ce/tree/master/config takes at least 10s to open, is it because the site is being hammered right now?

Yes. We went from 3 to 50 c4.4xlarge nodes in the past few months and are working hard to keep up with the demand of the growth.

I've been following gitlab for some time now. Both as a product and a company. Not only is it an amazing product, but from everything I've read they've made a really interesting culture. Would actually love to work for the company. Congrats to the team on shipping this. I'll be giving it a whirl soon :)

Thanks, that's nice to hear. Love to hear your feedback.

This is where I shamelessly tell you that we're hiring for almost any position.

Have you looked at other products?

The killer feature (for me) would be if GitLab supported the GitHub API (even if just a subset).

In what way?

The messaging integration certainly looks really good, we're trying out Let's Chat, but development is kinda slow (and we don't have the time to contribute). How does GitLab CI compare to Jenkins? Will I be able to substitute it for simple and complex projects?

Is there a slender version of GitLab for small computers like the RaspberryPi? All of the dependencies kinda hog/slow it down, and I don't really need realtime performance. I've grown fond of the interface (at work), and would like to use it for my hobby projects.

GitLab CI should be able to replace Jenkins. Obviously, it doesn't have the maturity of Jenkins or the plugin ecosystem, but it's flexible runner system, easy configuration with .gitlab-ci.yml and integration with GitLab make it quite powerful.

You can already have multiple, parallel builds, builds on success/failure, trigger builds and thus create pipelines. We don't support build artifacts yet, but you can circumvent this by using something like S3 for output. We'll add this in the future as well.

GitLab should run just fine on Raspberry Pi 2. Do you have any data on slow down?

We switched to building with Gitlab-CI and haven't looked back. A big bonus over Jenkins is the lack of Java.

The Mattermost preview screenshot is an odd choice - have a read of the conversation.

Mattermost team here. Sorry if the screenshot is confusing.

The text of the screenshot was actually written in Slack, and the goal of the screenshot was to demonstrate the Slack Import feature to GitLab Mattermost.

On the GitLab Mattermost page (https://gitlab.com/gitlab-org/gitlab-mattermost) there was a subtitle describing this, but we could have made it more clear in the screenshot itself.

Got it from the Mattermost Beta1 announcement. Think it's inappropriate?

Wow, this looks really nice! Are there any plans to expand the CI? The markup looks mostly job oriented, so I think most of the semantics would seem to need to be captured in scripts. For example, building across multiple operating systems. Unless I'm mistaken, I'd have to have the hosts available via SSH, probably copy a script(s), and then call it, etc...

You can already define multiple jobs in .gitlab-ci.yml and use labels to assign them to runners (#debian, #osx etc.). We use GitLab CI to build our Omnibus packages and that is a multiple operating system affair (including Raspbian for the Raspberry Pi 2).

Nice!

At work we use self-hosted GitLab for everything.

Now I need a private repo (personal project) to deploy on my VPS, any opinions about GitLab vs Bitbucket for this use case? Speed, stability? I'm probably going to use Fabric this time.

Gitlab or Bitbucket aren't going to handle deploys for you.

You need gitlab-ci with the continuous deployment option.

For others: Fabric is a python project similar to Capistrano.

Why Fabric over GitLab?

Wow nice release, it's come miles since I used it years ago, very cool! The only thing I'm missing at this point to make it perfect is a more advanced issue tracker (coming from Phabricator)

We're working on it, among other things.

Concrete suggestions more than welcome on feedback.gitlab.com or here.

Congrats on the release! It looks amazing! We've been using GitLab for a little while now and love all the updates that have been coming out recently.

Doing the upgrade now though and have run into an issue with the rake command backup:show_secrets. ("Don't know how to build task...") Any ideas?

See https://gitlab.com/gitlab-org/gitlab-ce/issues/2660

Documentation seems to be ahead of current GitLab release. This failing task will be included in a following patch release, very soon.

Thanks! That's nice to hear.

Can you create an issue with some more information (such as: what command did you run, what was the exact output, etc)?

If you're a subscriber, please email support :)

Looks good! One small typo: On the Pricing page https://about.gitlab.com/pricing/, instead of " Next-business day support" it should be "Next business day support".

Thanks cevn, fixed with https://gitlab.com/gitlab-com/www-gitlab-com/commit/e23e5280...

Updating broke my ci builds, :(

edit: following advice in this issue worked for me - https://gitlab.com/gitlab-org/omnibus-gitlab/issues/804

It doesn't look like there is any way to have per-receive hooks anymore: https://gitlab.com/gitlab-org/gitlab-ee/issues/26

Any chance of getting packages for Ubuntu 15.04?

There appears to be an open issue at https://gitlab.com/gitlab-org/gitlab-ce/issues/2160

Latest build should work, see https://gitlab.com/gitlab-org/gitlab-ce/issues/2160

131 comments