Already bumped our postgres RDS to 11 for this. Upgrade time! [edit] Upgrade went well
Is PG 11 required for this new release? Does PG 10 work?
GitLab 13.0
21–30 of 87 posts
Re: GitLab 13.0
#22I 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…
I hope the full Jira integration comes down to a level that would at least compare with BitBucket pricing. Right now it's more than double. My company would switch if the cost was the same or close, but I can't justify paying double even with all the extra features in gitlab.
Its not likely. They are insistent on the pricing model, even if it does not make sense. See my post above.
Re: GitLab 13.0
#23Does gitlab offer a stripped down version with only vanila 'git' ?
GitLab Developer Evangelist here.
You can install GitLab and only _use_ it for 'git' (source control management). But the install is the same - GitLab is a single application
Re: GitLab 13.0
#24Hi! There are a lot of new features with this update, so here are a few highlights: -improved version of Gitaly service called Gitaly Cluster for high availability git storage [1] -simplified deployment of GitLab to Amazon ECS [2] -added epic hierarchy on roadmaps (+ other improvements to our epic and milestone features) [3] [1] https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-rel... [2] https://about.gitlab.…
-Reduced memory consumption of GitLab with Puma [1] Puma reduces the memory footprint of GitLab by about 40% compared to Unicorn. Considering one of the most frequent complains about Gitlab is memory usage. 40% is huge. [1] https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-rel...
It is! We're super excited about it. We've been running it on GitLab.com for some time now, and it's been great to see.
Re: GitLab 13.0
#25What keeps me from using gitlab.com is that they flat out reject a signup with an email from my email provider. Anybody else having that problem? I wonder if they have a whitelist and only accept users who use the big boys like gmail etc. Or if they for some reason have totally legit email providers on their blacklist.
GitLab Developer Evangelist here.
It could be that there is a legit email provider that got on the banned list inadvertently. Would you mind sharing the provider?
If you want to not do it in public you can DM me at olearycrew on Twitter or email boleary [at] gitlab.com
Re: GitLab 13.0
#26Exporting 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 variables from parent to child, pipline UI behaves differently when being part of relation (and many times unusuable or shows a wrong thing), not being able to repeat manual jobs with the same var initially passed, not even being able to run it again with any other var unless you delete all previous executions, strange limitations on masked secret vars, $ in your password will get evaluated as variable etc ...
Seems like an afterthought, rather then a carefully designed feature set. Too organic for my taste (I guess Conway's law is full blown there).
While Gitlab CI is getting better (or more capable, rather then better) then before in every release, it does seem bloated, overly complex, full of surprises, not reproducible locally, very slow (caching is ridiculous feature that makes job often run longer then without it) and with strange design that doesn't let me view my build log full screen or collect entire pipeline output easily.
Generally, Windows is also lagging behind (I can't use pwsh as runner shell today after 4 years in existence?). The worst recent offender: you display 'fail' on every job in color: "WARNING: Failed to load system CertPool: crypto/x509: system root pool is not available on Windows". This trips everybody that job has failed when it didn't.
I think Gitlab guys need to start taking CI/CD/runner more seriously or at least bring some fresh mind to it. After all, this is one of the major reasons for many people to use it.
Re: GitLab 13.0
#27What keeps me from using gitlab.com is that they flat out reject a signup with an email from my email provider. Anybody else having that problem? I wonder if they have a whitelist and only accept users who use the big boys like gmail etc. Or if they for some reason have totally legit email providers on their blacklist.
GitLab Developer Evangelist here. It could be that there is a legit email provider that got on the banned list inadvertently. Would you mind sharing the provider? If you want to not do it in public you can DM me at olearycrew on Twitter or email boleary [at] gitlab.com
Hi! Yandex. Am I really the first to tell you? Yandex has a 30% market share in Russia.
Re: GitLab 13.0
#28Exporting 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.
Re: GitLab 13.0
#29Exporting 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…
Announced today as part of our 13.0 Release is the ability to pass variables/data between jobs without using artifacts - https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-rel....
For a list of planned follow-up issues as we iterating on the parent-child pipeline MVC, please check out our epic for this feature: https://gitlab.com/groups/gitlab-org/-/epics/2750. We welcome your comments and up-votes on the issues that matter most to you.
EDIT: Sorry; misread your first sentence; seems you saw the announcement that there is an alternative to passing variable via artifacts. Please consider opening an issue (https://gitlab.com/gitlab-org/gitlab/-/issues/new) to let us know how you would like jobs to communication.
Re: GitLab 13.0
#30Hi! There are a lot of new features with this update, so here are a few highlights: -improved version of Gitaly service called Gitaly Cluster for high availability git storage [1] -simplified deployment of GitLab to Amazon ECS [2] -added epic hierarchy on roadmaps (+ other improvements to our epic and milestone features) [3] [1] https://about.gitlab.com/releases/2020/05/22/gitlab-13-0-rel... [2] https://about.gitlab.…
oops misspoke and now I can't edit, I meant deployment of applications to AWS (hopefully you knew what I meant!)