GitLab acquires Peach Tech and Fuzzit • Hacker News Board

Re: GitLab acquires Peach Tech and Fuzzit

#51

Post by ojosilva » Sat, Jun 13, 2020, 12:53 AM UTC

sytse wrote: post #43

ojosilva wrote: post #25

Gitlab looks more and more like SAP these days. That's not necessarily a bad thing, enterprises out there choose all-in-one solutions because they need tech that covers the most ground with the easiest budget allocation, POC efforts from internal buyers and streamlined consulting at the post-sale effort. But once in, Gitlab, differently from SAP or Salesforce, is customized from around instead of from within. Meaning…

Thanks for your thoughtful comment. “building a solid platform for dev and ops taking code to production” => great, that is a big focus for us! We already have invested a lot to make this easier, including environments, feature flags, and more. Our direction is on https://about.gitlab.com/direction/ops/#release What is the top feature you would like to see?

Hi Sid, there are 2 users already making their points on this thread on the precise core issue I've raised: they have to automate around Gitlab instead of from within. This is what real platforms are about, they give users the tools to customize and make the platform behave the way their org needs it.

The great late Robert Stroud, ex Forrester analyst, was very adamant on how a DevOps platform should focus on weaving the so-called value chain, not replacing it.

Re: GitLab acquires Peach Tech and Fuzzit

#52

Post by majkinetor » Sat, Jun 13, 2020, 8:21 PM UTC

mokha wrote: post #47

majkinetor wrote: post #44

Earlier quoted context omitted.

1. running CI locally 2. issue relations in core 3. getting a repository file via curl easily (yeah, seriously)

1. It does take some effort to get the gitlab-runner to run locally but it is possible to use the shell runner. This does require that you connect the gitlab-runner to an instance of GitLab. If I understand correctly, I think you're asking for the ability to take a `.gitlab-ci.yml` file and run the job(s) locally from your shell without requiring it go through the gitlab-runner and connecting to a GitLab instance. Pl…

1. a lot of effort and I never want to repeat that, ever

2. issue relations is when you connect issues to other issues (for example, Redmine has both sub-issues and related issues)

3. Can you try that when repo is authorized and let me know how it went ?

Re: GitLab acquires Peach Tech and Fuzzit

#53

Post by mokha » Mon, Jun 15, 2020, 3:20 PM UTC

majkinetor wrote: post #52

mokha wrote: post #47

Earlier quoted context omitted.

1. It does take some effort to get the gitlab-runner to run locally but it is possible to use the shell runner. This does require that you connect the gitlab-runner to an instance of GitLab. If I understand correctly, I think you're asking for the ability to take a `.gitlab-ci.yml` file and run the job(s) locally from your shell without requiring it go through the gitlab-runner and connecting to a GitLab instance. Pl…

1. a lot of effort and I never want to repeat that, ever 2. issue relations is when you connect issues to other issues (for example, Redmine has both sub-issues and related issues) 3. Can you try that when repo is authorized and let me know how it went ?

1. Yes, I agree. This is something that I personally would like to improved. 2. Oh, I see. I don't have much experience with this one. 3. Got ya. So cURLing a raw file from a private repo. How would you like that to work?

Re: GitLab acquires Peach Tech and Fuzzit

#54

Post by majkinetor » Mon, Jun 15, 2020, 8:14 PM UTC

mokha wrote: post #53

majkinetor wrote: post #52

Earlier quoted context omitted.

1. a lot of effort and I never want to repeat that, ever 2. issue relations is when you connect issues to other issues (for example, Redmine has both sub-issues and related issues) 3. Can you try that when repo is authorized and let me know how it went ?

1. Yes, I agree. This is something that I personally would like to improved. 2. Oh, I see. I don't have much experience with this one. 3. Got ya. So cURLing a raw file from a private repo. How would you like that to work?

3. I have a link to a file already (in a browser URL bar), let me use it with token or something easy (for example the way most RSS with auth are constructed so that you don't need to set up credentials when 'subscribing') instead of looking for project IDs and constructing path that GitLab can swallow as a query parameter, fighting all kind of nonsence in the process.

FYI, nobody I know did that in a minute (and minute is much for such task) and everybody was like _fuck this shit, I'll just clone entire repo to use a single file_, 15 minutes later.

Re: GitLab acquires Peach Tech and Fuzzit

#55

Post by JetSpiegel » Thu, Jun 25, 2020, 12:01 AM UTC

majkinetor wrote: post #44

sytse wrote: post #42

Earlier quoted context omitted.

What are the top 3 basic and important things that GitLab could add?

1. running CI locally 2. issue relations in core 3. getting a repository file via curl easily (yeah, seriously)

3.1. Get a sane link to a build artifact (something like latest `master`). This can be worked around if you just publish them on Gitlab Pages, a nice solution now that they even have authentication.