GitLab 10.6 released with CI/CD for GitHub

Post by kuschku » Thu, Mar 22, 2018, 6:59 PM UTC

williamchia wrote: post #41

kuschku wrote: post #13

Earlier quoted context omitted.

Oh fuck that. I’m a student using this to host open source projects, I’m not going to pay more for GitLab than I pay for all my servers and software combined. I’ll just hack it in there myself then, like I had to put some of the other "premium" features in myself. Long-term it looks like I’ll have to migrate to something else then.

Hi Kuschku - I think this is misunderstanding, we are offering GitLab CI/CD for free for GitHub.com projects. It'll be free for private repos for a year, and it will be free for public repos forever. See the "Open source projects" and "Anyone using GitHub.com" sections: https://about.gitlab.com/features/github/

Post by eslaught » Thu, Mar 22, 2018, 7:02 PM UTC

williamchia wrote: post #46

eslaught wrote: post #33

Earlier quoted context omitted.

Edit2: This is wrong, see replies below. An update, having now tried this on a toy Gitlab/Github instance. It looks like this still relies on Gitlab's support for mirroring an external repo, which relies on polling. This is less than awesome, because it means we're back into the (many) minutes latency range from pushing changes to seeing them appear in the mirrored repo (and therefore CI). When I did this before, we…

Hi Eslaught - So the new CI/CD for GitHub feature should be solving the pain points of the old manual mirroring process. When you set up a project and Oauth to GitHub it should automatically implement 3 components: - Bidirectional Mirroring https://gitlab.com/gitlab-org/gitlab-ee/issues/3745 - push webhook to GitLab to trigger CI/CD immediately once a code is committed (e.g. "push mirroring") https://gitlab.com/gitla…

Post by boleary-gl » Thu, Mar 22, 2018, 7:18 PM UTC

diggan wrote: post #22

Thaxll wrote: post #18

I'm curious for the people that use GitLab CI/CD, what's the pro / cons vs Jenkins and the like?

A short while ago (eh, just noticed this was over a year ago...) I did a comparison between different testing solutions for all projects within the IPFS organization. Remember this was a year ago, so many things have changed but we ended up going with Jenkins and I'm now migrating projects from free usage of Travis/CircleCI to Jenkins. - Brief explanation: https://github.com/ipfs/infrastructure/issues/100#issuecomme.…

Post by chinhodado » Thu, Mar 22, 2018, 7:28 PM UTC

victorwu wrote: post #43

chinhodado wrote: post #24

I hate it that Gitlab is focusing too much on all these project-management features, while neglecting the basic code review features such as commenting on a block of code, or making a review session instead of creating individual comments, or the ability to blame previous revisions of a file

Here's an example of a blame on a previous commit of a file. https://gitlab.com/gitlab-org/gitlab-ce/blame/57ce7c655cc58e... Did you have some particular feature request beyond this view?

Post by eslaught » Thu, Mar 22, 2018, 7:43 PM UTC

Snappy wrote: post #49

williamchia wrote: post #46

Earlier quoted context omitted.

Hi Eslaught - So the new CI/CD for GitHub feature should be solving the pain points of the old manual mirroring process. When you set up a project and Oauth to GitHub it should automatically implement 3 components: - Bidirectional Mirroring https://gitlab.com/gitlab-org/gitlab-ee/issues/3745 - push webhook to GitLab to trigger CI/CD immediately once a code is committed (e.g. "push mirroring") https://gitlab.com/gitla…

FWIW, if you created the connection between GitLab and GitHub for your project before 10.6, you'll have to remove the connection and then re-add it to get the push-based mirroring to happen. Otherwise, yes, it will still poll.