51–60 of 80 posts
Earlier quoted context omitted.
We took external investment so we need to either get acquired or IPO. Since 2015 we're aiming for an IPO in 2020 https://about.gitlab.com/strategy/ and so far we're on track.
Or maybe, you could become profitable organically in the future. Today, might go down as a turning point in your history
I'm impressed how far GitLab has come in a short amount of time. It's a pretty well-designed platform, when it comes down to it. I think the Vue-based user interface and the data model are probably the cornerstones of it, and using Ruby on the backend just helps them iterate quickly. Ruby also seems to be getting more robust [1]. Their CI/CD platform is really a great approach, emphasizing the GitLab Worker as a port…
I recently crossed swords with .gitlab-ci.yml. An obfuscation layer that fights back.
Ditto jenkinsfile and whatever you wanna call GoCD's config.xml.
This silliness reminds me most of all those ETL workflow obfuscation frameworks, like BizTalk and TalenD.
PS- If anyone has the bad judgement to use YAML, it'd be nice if the linter reported something more specific than "syntax error line 1 char 1" for deeply buried typos. I thought XML sucked until I met JSON. I thought JSON sucked until I met YAML. What's next? The resurrection of ASN.1?
PS2- It's not programming if you can't set a break point. The edit, eval, fail, profanity loop for troubleshooting .gitlab-ci.yml is pretty intense.
I've just imported some of my open source projects from GitHub to GitLab, not because I'm in panic mode due to MS, but because i wanted to try out GitLab again already for some time. I've used it once 2-3 years ago for a short time in a self-hosted version in a client project, and was mostly unhappy with it's perfomance. I thought it was mainly because it was running on very slow hardware, but the gitlab.com version…
I'm impressed how far GitLab has come in a short amount of time. It's a pretty well-designed platform, when it comes down to it. I think the Vue-based user interface and the data model are probably the cornerstones of it, and using Ruby on the backend just helps them iterate quickly. Ruby also seems to be getting more robust [1]. Their CI/CD platform is really a great approach, emphasizing the GitLab Worker as a port…
Builds should just be done with shell scripts. I recently crossed swords with .gitlab-ci.yml. An obfuscation layer that fights back. Ditto jenkinsfile and whatever you wanna call GoCD's config.xml. This silliness reminds me most of all those ETL workflow obfuscation frameworks, like BizTalk and TalenD. PS- If anyone has the bad judgement to use YAML, it'd be nice if the linter reported something more specific than "s…
You still need something to describe the order and dependencies of those shell scripts as well as when to run them (branches, tags) and how to handle the artifacts (expiry time, etc). Which should be, much preferably, something not Turing-complete, so you can make an UI for this. Draw the graph, etc etc.
Take those parts out, and almost all what's left in .gitlab-ci.yml is just the `script` key.
You can debug most things locally (without having to do that ugly commit-try-fail-repeat dance) with https://docs.gitlab.com/runner/commands/#gitlab-runner-exec
Earlier quoted context omitted.
What's your measurement for determining whether you are on track to an IPO in 2020?
Companies that IPO generally have a certain amount of annual revenue, a certain sized customer base in particular sectors (e.g. SAAS), and have a certain valuation judged by market capitalization. Companies have to be a certain minimum size and must have a predictable business with stable metrics for public exchanges and markets to be willing to list and purchase shares in the company. This doesn't always require bei…
However I'm already familiar with the topic. I'd just like to hear from Gitlab's CEO what makes him believe he's "on track" to an IPO in 2020. Usually such a display of confidence is backed by some form of evidence. Does Gitlab publish their revenue, or revenue growth, anywhere?
Our team loves Gitlab. We have had a bunch of slow responses today. Also lots of CI/CD glitches yesterday and today... but we recognize this is just due to the exodus so we know it will go back to normal - we're just laughing about it a bit.
...countdown to Apple acquiring GitLab??
I'm impressed how far GitLab has come in a short amount of time. It's a pretty well-designed platform, when it comes down to it. I think the Vue-based user interface and the data model are probably the cornerstones of it, and using Ruby on the backend just helps them iterate quickly. Ruby also seems to be getting more robust [1]. Their CI/CD platform is really a great approach, emphasizing the GitLab Worker as a port…
Builds should just be done with shell scripts. I recently crossed swords with .gitlab-ci.yml. An obfuscation layer that fights back. Ditto jenkinsfile and whatever you wanna call GoCD's config.xml. This silliness reminds me most of all those ETL workflow obfuscation frameworks, like BizTalk and TalenD. PS- If anyone has the bad judgement to use YAML, it'd be nice if the linter reported something more specific than "s…
I personally don't like to have a whole shell script inside .gitlab-ci.yaml file either -- that's why I have a seperate script called setup.bash/build.bash inside a CI folder and juse write `script: ./ci/build.bash` inside gitlab-ci.yaml. But nobody ever told you, you cannot do that. The gitlab-ci.yml is just a configuration file for the build system to tell it what you want your environment(s) to be.
I agree that error reporting for YAML files suck -- but at least they are more consistent and easier to parse then XML files. And they are also way more readable then JSON files -- they have essential features such as long strings, and comments. The only annoying thing with Gitlab CI (and any other CI system) is to make sure it works. It often takes me 10 tries to make sure everything works correctly.
Earlier quoted context omitted.
You're misunderstanding this. They added GitLab and Bitbucket in Xcode 10, but Xcode 9 already had GitHub integration. These two are being added in addition to GitHub.
The timing of the announcement is a little serendipitous though. I don't know if i'd go so far as to call it a tacit endorsement of gitlab by Apple, but it does have an air of opportunism.