Live data from Hacker News

GitLab 13.0

about.gitlab.com

31–40 of 87 posts

Re: GitLab 13.0

#34

Exporting environment variables via artifacts sounds like a strange decision, but I guess its one way to do it. After years of waiting for jobs to communicate other then relying on file artifacts this is somewhat disappointing. I would like to see parent/child pipelines recive some love as currently it does work but quirks are all around. For example, its not easy (or sometimes even possible) to pass pipeline variabl…

They still haven't fixed process killing (that is, not sending SIGKILL immediately but sending SIGTERM so that child processes get cleaned up and the runner doesn't get stuck waiting for child processes to exit that don't know they should exit).

For being THE feature that made gitlab big the whole CI area seems to be getting away from them

Re: GitLab 13.0

#35
post #28

Exporting environment variables via artifacts sounds like a strange decision, but I guess its one way to do it. After years of waiting for jobs to communicate other then relying on file artifacts this is somewhat disappointing. I would like to see parent/child pipelines recive some love as currently it does work but quirks are all around. For example, its not easy (or sometimes even possible) to pass pipeline variabl…

The caching is so broken it's barely usable. You can't easily exclude files. The cache can't be updated incrementally. It's often slower than downloading all dependencies on every build.

Instead of caching node_modules, cache node_modules.tar.szt

Then wrap your job in a untar/tar:

    tar --use-compress-program zstd -xf node_modules.tar.zst || true
    YOUR NORMAL JOB
    tar --use-compress-program zstd -cf node_modules.tar.zst node_modules
(and you can delete things you don't need if you want)

Re: GitLab 13.0

#39
post #15

Does gitlab offer a stripped down version with only vanila 'git' ?

You only need an SSH server for that.

You can combine ssh with multiple users to provide repo-level permissions (not branch level). You use standard linux permissions to enable deploy keys. You would also use git-shell on the read only ssh accounts for the deploy-keys. Without writing a new shell you wouldn't be able to do branch level protection.

Re: GitLab 13.0

#40
post #5

I really hope some of the the project management tools and scanning features will trickle down to the cheaper/free tiers some time. I can understand that not everything has to be free but the current feature split of project management and scanning features among the tiers feels a bit haphazard with some crucial things at the highest prices, making it hard to justify the in-between tiers and impossible to buy the hig…

Putting Epic and Issue tools to the highest pricing is terrible for lots of people. We forced to pay features that we will never use.

I wish they add some kind of addon system for these features.

Post reply on HN