Xcode 10 is now integrated with GitLab (opens in new tab)

One of my favorite features from GitLab is, without having to install any other tool, I can get a link from the response to create my MR. Such a simple feature, yet so convenient.

But how do you tell a spell script to be a multi staged build? You can't just write `set OS=macos` and suddenly your OS changes from debian to macos. The best you could do is to ssh into that machine but how do you tell your build system to provision a machine with such parameters? You would essential have to build a new build system just for that. Or you could just use a config file -- whether you call it config.ini, .gitlab-ci.yaml, or build.json should not matter. Furthermore, how would you execute a bash script on Windows? You would have to at least tell it to enable Linux Subsystem and make sure it is a Pro version.

I personally don't like to have a whole shell script inside .gitlab-ci.yaml file either -- that's why I have a seperate script called setup.bash/build.bash inside a CI folder and juse write `script: ./ci/build.bash` inside gitlab-ci.yaml. But nobody ever told you, you cannot do that. The gitlab-ci.yml is just a configuration file for the build system to tell it what you want your environment(s) to be.

I agree that error reporting for YAML files suck -- but at least they are more consistent and easier to parse then XML files. And they are also way more readable then JSON files -- they have essential features such as long strings, and comments. The only annoying thing with Gitlab CI (and any other CI system) is to make sure it works. It often takes me 10 tries to make sure everything works correctly.

> Builds should just be done with shell scripts

You still need something to describe the order and dependencies of those shell scripts as well as when to run them (branches, tags) and how to handle the artifacts (expiry time, etc). Which should be, much preferably, something not Turing-complete, so you can make an UI for this. Draw the graph, etc etc.

Take those parts out, and almost all what's left in .gitlab-ci.yml is just the `script` key.

You can debug most things locally (without having to do that ugly commit-try-fail-repeat dance) with https://docs.gitlab.com/runner/commands/#gitlab-runner-exec

Sorry, but you really aren't, quite yet. I'm trying to import a very small repo from github (literally 1 branch and 2 files with hardly any revisions and no issues) and it's still sitting there showing "Starting...". I had tried to mass import a lot and after 11+ hours of "Starting..." I decided to remove them and just try one at a time. Still no luck after almost 20 minutes.

You can also run Gitlab yourself. I understand for various reasons it's an attractive option.

Huh.

Does Google also have an issue tracker?

Yes

It supports GitHub, BitBucket and GitLab.

It’s not very useful though. It just lets you clone repos without using a shell. Kind of pointless.

What's your measurement for determining whether you are on track to an IPO in 2020?

Or maybe, you could become profitable organically in the future. Today, might go down as a turning point in your history

The timing of the announcement is a little serendipitous though.

I don't know if i'd go so far as to call it a tacit endorsement of gitlab by Apple, but it does have an air of opportunism.

Really? Not sure you've been paying attention. That may have been true in the past and I'm not saying Apple isn't OSS friendly, but the sheer amount of Microsoft code on Github would beg to differ.