Live data from Hacker News

GitLab 10.6 released with CI/CD for GitHub

about.gitlab.com

81–90 of 107 posts

Re: GitLab 10.6 released with CI/CD for GitHub

#81
post #76
post #18

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

So I use Gitlab CI on my personal projects, and in work I was "the Jenkins guy" on our team for a good while, though I've since changed projects to one using an internal tool so my Jenkins knowledge is ~1yr outdated. Gitlab CI: ========== + No infrastructure required. I like to work on my private projects and not their servers. + Mostly-declarative syntax with a easy way out when required. Jenkins until recently only…

Thanks for reviewing GitLab. We introduced a way to share scripts in the last version as a paid feature https://about.gitlab.com/2018/02/22/gitlab-10-5-released/#in...

Re: GitLab 10.6 released with CI/CD for GitHub

#82

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

Or basic modern web UX. Like using a wide screen effectively.

Under your profile settings/preferences, you have the ability to set your layout to 'fluid' This will allow the application to take up 100% of the width of the screen. If you have more specific UX issues you think we should address, I'd love to hear them!

Re: GitLab 10.6 released with CI/CD for GitHub

#83

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…

I guess I got lost on my initial pass through the UI. I deleted my toy repo and did it over again; it seems to be working now. Latency seems to be in the 20-30 second range for incremental pushes, which is pretty good. Is there a way to do this for existing repos? Or do we have to delete and re-create our production repo to do this?

> Is there a way to do this for existing repos?

You can add a webhook on GitHub and have it point to our Pull Mirroring API [1], followed by manually setting up the integration to send status updates back [2].

We're looking to make this process easier, and have explored ways we might implement this in https://gitlab.com/gitlab-org/gitlab-ee/issues/5220.

[1] https://docs.gitlab.com/ee/api/projects.html#start-the-pull-...

[2] https://docs.gitlab.com/ee/user/project/integrations/github....

Re: GitLab 10.6 released with CI/CD for GitHub

#84
post #77
post #70

Earlier quoted context omitted.

Does this mean that gitlab doesn't generally employ people to simply learn their competitors products, to keep informed of their offerings?

This is a highly unfair criticism, you’re never going to have total feature parity with your competitors, nor is that even a good thing to strive for.

[deleted]

Re: GitLab 10.6 released with CI/CD for GitHub

#85

Is this available for Stash/Bitbucket as well?

Bitbucket Cloud PM here. We'd love to see more usage of Bitbucket (both Cloud and Server) by GitLab users.

As williamchia mentioned above, it's possible to configure GitLab builds for a Bitbucket Cloud or Server repository via webhooks and our build status API today. We're open to helping build better integration, but given the APIs already exist, it would mainly be a project on the GitLab side.

Re: GitLab 10.6 released with CI/CD for GitHub

#86

Earlier quoted context omitted.

So last time I checked (and I sent an email to sales to confirm) CircleCI doesn't have support for a configuration where you want to use both public and private runners. I want to use my own machines to build certain jobs (perhaps because those jobs require heavy computation), but I want to use the free, shared, cloud-based runners for the rest (to increase overall throughput). And I want to do this while keeping the…

We use buildkite at work, and it works well. Buildkite hosts the CI master, and you run the workers on your own infrastructure -- as many as you want. So you don't get the free public agents like you want, but you do get private runners.

My company's also using Buildkite, and I've been hugely impressed with how easy it is to work with, and how flexible it's been for us.

Re: GitLab 10.6 released with CI/CD for GitHub

#87
post #85

Is this available for Stash/Bitbucket as well?

Bitbucket Cloud PM here. We'd love to see more usage of Bitbucket (both Cloud and Server) by GitLab users. As williamchia mentioned above, it's possible to configure GitLab builds for a Bitbucket Cloud or Server repository via webhooks and our build status API today. We're open to helping build better integration, but given the APIs already exist, it would mainly be a project on the GitLab side.

Is there a way to migrate a repo from Bitbucket Server into gitlab preserving pull request history?

Re: GitLab 10.6 released with CI/CD for GitHub

#88
post #77
post #70

Earlier quoted context omitted.

Does this mean that gitlab doesn't generally employ people to simply learn their competitors products, to keep informed of their offerings?

This is a highly unfair criticism, you’re never going to have total feature parity with your competitors, nor is that even a good thing to strive for.

Mine is a perfectly valid criticism. You do nobody any favors by conflating the goal of total feature parity with the general concept of business intelligence, and understanding your direct competitor's key features.

The strawman you float is the complete opposite of what I asked. It simply occurred to me as strange that there are features that meet all of the following requirements:

1. Available on github for quite sometime

2. Long enough in fact to get a dedicated article in their knowledgebase

3. A popular enough feature to possibly gate the entire calculus for users to switch services.

4. Obviously useful feature, as evidenced by the gitlab triage engineer being convinced to add an issue with a single paragraph plea.

5. Gitlab is seemingly unaware of this publicly available information, to the trivially rectified detriment of their own bottom line.

Re: GitLab 10.6 released with CI/CD for GitHub

#89
If any GitLab people are still watching this thread, has there ever been any discussion on offering subscriptions to specific EE features? Instead of a full per user subscription.

I work at a small community college and we have a self hosted instance of GitLab-CE. There's no way we could budget anything for a subscription (as much as I'd love to support GitLab's development.) So, if I could tell my boss that we could get a needed feature for x-dollars/month, that might actually be doable.

I was one of the people asking for the GitHub -> GitLab-CI integration. So I am fairly disappointed it ended up in EE instead of CE.

Re: GitLab 10.6 released with CI/CD for GitHub

#90
post #89

If any GitLab people are still watching this thread, has there ever been any discussion on offering subscriptions to specific EE features? Instead of a full per user subscription. I work at a small community college and we have a self hosted instance of GitLab-CE. There's no way we could budget anything for a subscription (as much as I'd love to support GitLab's development.) So, if I could tell my boss that we could…

I feel your pain but unfortunately free doesn’t pay the bills.

It’s more than fair that CI/CD is a billable feature.

And making a product plugin play as you ask would make supporting it a huge pain in the ass.

Keep in mind Jenkins is still free if needed

Post reply on HN