Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Moving to GitLab

mail.haskell.org

Post reply on HN
Print view View original

51–60 of 61 posts

Re: Moving to GitLab

#51

Post by rleigh »

wodenokoto wrote: post #25
sytelus wrote: post #20

TLDR; Why GitLab instead of GitHub? From their discussion group thread: - Good multi-platform hosted CI or at least workable integration with other (existing) CI solutions - Hosted review tool that we don't have to maintain ourselves (though a little bit less good than Phabricator, allegedly) - familiar GitHub-like workflow with no requirement to install extra software locally - Reuse of GitHub credentials - Realisti…

What is wrong with Travis compared to GL's default CI?

Travis is limited. Stuff like this https://gitlab.com/codelibre/ome-model/pipelines/37267293 is several steps beyond the capabilities of Travis.

This is using platforms not supported by Travis, plus custom Docker images. And integrates with other GitLab pipelines, deploys to sonatype nexus, and stores artifacts for later use.

Even if you're not using the advanced features, it's still vastly better than Travis. The Travis stock images are so out of date it's not funny.

Re: Moving to GitLab

#52

Post by [deleted] »

barneygale wrote: post #35
lugg wrote: post #32

Earlier quoted context omitted.

You don't like my casual use of the word cancer? Fine. Personally I feel like cancer was a relatively good approximation for the cancerous like changes you need to make to established industry workflows once you begin to use phabricator. Would you have preferred I used the word infection? Virus? Aids? Which one of those metaphors crosses the "sense writing" line for you? Why does cancer?

Describing software as "cancer" is something I'd expect to see on 4chan or reddit, not HN. It's hyperbole and your explanation ("relatively good approximation for the cancerous like changes [to] workflows") shows as much.

[deleted]

Re: Moving to GitLab

#53

Post by http-teapot »

jhasse wrote: post #44
wodenokoto wrote: post #25

Earlier quoted context omitted.

What is wrong with Travis compared to GL's default CI?

Does Travis have native Docker support? Last time I checked you had to manually run docker and add "sudo: true" to your .travis.yml.

I am not exactly sure of your use case but we build our Docker images in Travis without problems. https://docs.travis-ci.com/user/docker/

Re: Moving to GitLab

#55

Post by jhasse »

http-teapot wrote: post #53
jhasse wrote: post #44

Earlier quoted context omitted.

Does Travis have native Docker support? Last time I checked you had to manually run docker and add "sudo: true" to your .travis.yml.

I am not exactly sure of your use case but we build our Docker images in Travis without problems. https://docs.travis-ci.com/user/docker/

I want to run my build/test commands in a Docker image.

Re: Moving to GitLab

#56

Post by xte »

u801e wrote: post #49
avar wrote: post #48

Earlier quoted context omitted.

> I simply don't see how it requires significant expertise or a week to set up[...] I don't just mean the setup required to send a one-off patch. Obviously setting up some random E-Mail client with IMAP is easy. But the sort of setup required to get anything like feature parity with common operations in GitHub's or GitLab's interface. E.g. when you open a Pull/Merge request on those sites. It's easy to apply & downlo…

> when you open a Pull/Merge request on those sites. It's easy to apply & download the patch series locally to test it. For E-Mail client integration you need something that'll "git am" a range of messages. That's a good point. Like git-am is the inverse of git-format-patch. Unfortunately, no program has been written as the corresponding inverse of git-send-email. If a program like that existed, then one could get fe…

Hem, notmuch/mu4e offer easy magit integration so you can see, test, patch etc straight from a mail messages... That's the power of a text-centric UI vs a graphical-centric UI.

Re: Moving to GitLab

#58

Post by jamietanna »

jimktrains2 wrote: post #41
zuron7 wrote: post #29

Earlier quoted context omitted.

Afaik, The Pro version is open source as well, it's just not usable without a key.

That's not really possible, and I'm not sure what you mean.

A better distinction here in naming would be to call GitLab EE "Source Available" rather than "Open Source"

Re: Moving to GitLab

#59

Post by brodock »

unixhero wrote: post #17
xte wrote: post #15

A small note: what's the difference between GitLab, GitHub etc? Are they companies with a substantially identical target: making money? Does they offer storage on their own server (or even worse others servers in a chain)? So why the hell instead of moving from a company to another ANY FOSS dev do not came back to classic ML (mirrored offline in personal maildir) and use hosting, multiple if possible, only as a mean…

Gitlab also runs locally.

We also provide an Export tarball with everything inside you project, including the repo, issues, merge request content, etc.

We do not lock you up in a walled garden.

It's also easy to import the whole project/group from one instance to another.

Re: Moving to GitLab

#60

Post by u801e »

xte wrote: post #56
u801e wrote: post #49

Earlier quoted context omitted.

> when you open a Pull/Merge request on those sites. It's easy to apply & download the patch series locally to test it. For E-Mail client integration you need something that'll "git am" a range of messages. That's a good point. Like git-am is the inverse of git-format-patch. Unfortunately, no program has been written as the corresponding inverse of git-send-email. If a program like that existed, then one could get fe…

Hem, notmuch/mu4e offer easy magit integration so you can see, test, patch etc straight from a mail messages... That's the power of a text-centric UI vs a graphical-centric UI.

I'll try it out. vim is my main editor, so it will be a bit of a learning curve to get used to emacs :)

As an aside, I have tried out gnus for reading the git mailing list via gmane, but I found it very slow in threading messages (when compared to Thunderbird). I don't know if notmuch/mu4e has the same issue though.

Post reply on HN