what makes it different than ordinary webhook ?
That's possibly what was implemented now.
More details :
GitLab 10.6 released with CI/CD for GitHub
11–20 of 107 posts
Re: GitLab 10.6 released with CI/CD for GitHub
#12Please fix this to point to the original article, not this blogspam. https://about.gitlab.com/features/github/
I'm not sure if you noticed but this "blogspam" is literally a release note, as says in the title " GitLab 10.6 released", support for GitHub is one of many features.
Re: GitLab 10.6 released with CI/CD for GitHub
#13Finally! I'm running a custom GitLab instance, and I have most of my projects in there, but I have to have some of my projects on GitHub, and having the same CI workflow available for them is going to be amazing.
It seems this feature is only available in the Premium plan, if you're hosting your own instance. It's free if you're using GitLab.com with a public GitHub repository. https://about.gitlab.com/features/github/ -- "Large Enterprises"
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.
Re: GitLab 10.6 released with CI/CD for GitHub
#14Please fix this to point to the original article, not this blogspam. https://about.gitlab.com/features/github/
I'm not sure if you noticed but this "blogspam" is literally a release note, as says in the title " GitLab 10.6 released", support for GitHub is one of many features.
[deleted]
Re: GitLab 10.6 released with CI/CD for GitHub
#15Please fix this to point to the original article, not this blogspam. https://about.gitlab.com/features/github/
I'm not sure if you noticed but this "blogspam" is literally a release note, as says in the title " GitLab 10.6 released", support for GitHub is one of many features.
[deleted]
Re: GitLab 10.6 released with CI/CD for GitHub
#16Gitlab's CI/CD is amazing. Of all the systems I've seen, it's the easiest to (a) deploy your own runners easily, and (b) mix private and public runners (i.e. the equivalent of using a free plan on Travis, with the benefit that for heavy-duty jobs you can run your own machines). That and first-class support for docker (no more being at the whims of what Travis chooses to deploy in their images), make it a really great system.
But we had been on Github, and that turned into something of a pain.
First we tried mirroring Github to Gitlab. This worked, but (a) it added a minute or two of latency to starting jobs in the CI, (b) since it went through one account, all the build emails went to a single person, and (c) the mirroring happened on our own infrastructure, which turned out not to be so reliable. So we got tired of this approach.
Eventually we decided to move development to Gitlab, but we didn't want to move our users, so we left all the user-facing elements on Github (issues, PRs, etc.). This also kind of works but has its own set of issues.
Things might have been different if we'd started on Gitlab from the very beginning, but as things are, I think having the repository on Github and the CI on Gitlab would be the best of both worlds for us.
Re: GitLab 10.6 released with CI/CD for GitHub
#17Please fix this to point to the original article, not this blogspam. https://about.gitlab.com/features/github/
I'm not sure if you noticed but this "blogspam" is literally a release note, as says in the title " GitLab 10.6 released", support for GitHub is one of many features.
You're commenting on the changed link. The original was techcrunch blogspam.
Re: GitLab 10.6 released with CI/CD for GitHub
#18I'm curious for the people that use GitLab CI/CD, what's the pro / cons vs Jenkins and the like?
Re: GitLab 10.6 released with CI/CD for GitHub
#19This is great, although I'll probably stick with Travis & Appveyor for my open source project since Gitlab.com currently only has Linux runners.
All three currently have two big flaws IMO though:
1. They all use YAML which is an awful, unintuitive format.
2. The only way to test a configuration is to commit it and push it. Why is there no way to paste a config file in their website and run that?
Hopefully one day we'll get a CI system that supports Windows, Linux and OSX and has a sane config format, and free minutes for open source projects. A man can dream!
Re: GitLab 10.6 released with CI/CD for GitHub
#20This makes a lot of sense to me. Gives Github users a taste of Gitlab's CI capabilities.
Note that today you can use the public hosted GL service and mirror a GH repo, and trigger GL CI when new commits arrive.
But this sounds even smoother still.