This[1] is for us a showstopper atm, so we are sticking to go.cd, although Jenkins seems to be improving a lot lately.
If you don't have a docker heavy type of dev workflow, I think it is a great alternative. Totally worth checking it out.
GitLab Runner (the 'slave' that runs your code), is just a Go binary, so it runs on anything you can run a Go binary on, which is pretty close to all major platforms.
Read more on Runner here: http://docs.gitlab.com/ce/ci/runners/README.html
And congrats to the Jenkins team! This looks amazing. A majority of our customers uses Jenkins. I'm sure they'll be excited to update.
After a little while you'll realise you want something a bit different, at which point the docker-image resource that's supported by the Concourse team makes it embarrassingly easy. You just tell Concourse "yo, push to this image" and it does the rest.
I wished for a better Jenkins UI for so long I had given up hope. GitLab CI looked enticing, but after putting so much work into building a workflow that doesn't pollute my repos with environment specific data i'm right back at Jenkins.
Thanks for this, this will make it so much clearer to our POs where we stand without spending forever trying to push that info into Jira.