13 ms·
Gitlab.com Is Moving to 13.0
- flatiron 6y agoAlready upgraded our gitlab RDS instance to PostgreSQL 11. AWS makes stuff like that very easy. We use the free version of gitlab and find it very capable. That plus Jenkins plus artifactory we have a nice little setup.
- AsyncAwait 6y agoCurious why Jenkins over GitLab's CI/CD?
- ryanmcdonough 6y agoI’d imagine they were already using it with their prior SC setup and didn’t want to move source control and everything else at once.
- flatiron 6y agoYep. We were svn using “beanstalk” when I joined our company and pushed for a git migration. But we already had Jenkins running with tons of stuff set up on cloud bees. Then they kicked us off for some reason (forgot why) so it started our own migration to AWS
- sytse 6y agoIf you are still considering moving CI from Jenkins to GitLab we're publicly testing a Jenkins Wrapper to make it more gradual to move https://gitlab.com/gitlab-org/gitlab/-/issues/215675 https://gitlab.com/gitlab-org/gitlab/-/issues/215675
- cgidriver 6y agoIntegration errors are hard to chase in Gitlab (For example: Something went wrong while creating your Kubernetes cluster Unexpected status; ROLLBACK_FAILED) - this does not give the user any information. Perhaps I could get some help here on this.
- flatiron 6y agoFamiliarity mainly. We have a dual Jenkins setup (one internal one at our clients site) so we have a metric ton of Jenkins stuff from years and years of work. I can also write Jenkins pipelines in my sleep from doing it so often and have probably read about GitLab’s yaml format for a few hours. Maybe one day we think about getting rid of Jenkins but I am quite fond of it.
- unixhero 6y agoIf anything upgrade from Jenkins to a proper workflow manager, such as Apache Airflow! Edit: I realize it might be more suitable for data pipelines than continuous integration.
- orlovs 6y agoWhen you have got a lot of things already ready written
- vdfs 6y agoGithub is great at one thing(so far): the UI never change. We did use Gitlab for sometime but the UI and slowness compared to Github was so noticeable. I wonder if its still the case now?
- axlee 6y agoComing from Bitbucket, Gitlab (self-hosted) felt blazing fast. But to be fair, any single tool feels snappy when stacked against an Atlassian product.
- manaskarekar 6y agoAlso, the UX on bitbucket is very convoluted, to me at least.
- mroche 6y agoMy current team/employer uses a self hosted Atlassian stack... I only use BB to find the repo URL before immediately cloning it. I can find my way around it relatively fine, but wow is it slow to load any kind of information. Not sure how much of that is the server it’s on or the application itself. EDIT: typo closing -> cloning it.
- unixhero 6y agoI have no complaints, it works zippy.
- httpsterio 6y agoThe UI on Github absolutely does change, about once a year they've done some small or even large changes to how Github looks and behaves. For me personally, I spend quite a bit of time looking for the right tab I want to navigate to and while I'm not lost, it takes along time to scan the UI and find what I'm looking for. I've preferd Gitlab's interface for the last few years over github simply because how much faster I can find everything.
- 6y ago
- cgidriver 6y agoCan I request removing default CI/CD/AutoDevOps stuff from projects? Also, perhaps improve AWS EKS integration. Is there a place to get help on gitlab on chat? IRC seems to be pretty slow to get help.
- Operyl 6y ago> As we continue to work towards version control for Snippets, we are making a change to search for Snippets in the UI and API that removes snippet Content from search results. Title and Description will still be accessible via search and API. This makes me a bit sad, but it probably has a valid technical reasoning. I just have to be a bit more descriptive in my descriptions I guess!
- 2bluesc 6y agoI'm excited to have version controlled snippets. I used to use Github Gists just for this feature. Snippets work great for team collab as I can throw up a random snippet and iterate on it now with version control instead of copying or replacing it as the previous design forced me to do.
- pedroms 6y agoYes, there's some reasoning behind the decision to remove snippet Content from search results. You can find the original discussion and decision in this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/199220 https://gitlab.com/gitlab-org/gitlab/-/issues/199220
- efiecho 6y agoI find it very frustrating that Gitlab requires Javascript for simple basic things. You can't view replies to issues or even browse files in a repository. GitHub UX is so much better, but sadly many projects moved to Gitlab because of Microsoft acquiring GitHub.
- cosmojg 6y agoPersonally, I'm hoping more of those folks move over to SourceHut[1]. It doesn't require JavaScript for anything, and it's much faster to boot. [1] https://sourcehut.org/ https://sourcehut.org/
- mcny 6y ago> I find it very frustrating that Gitlab requires Javascript for simple basic things. You can't view replies to issues or even browse files in a repository. GitHub UX is so much better, but sadly many projects moved to Gitlab because of Microsoft acquiring GitHub. How much coverage does the API have? In theory it should be 100% as the website uses (as far as I remember, haven't looked into the source) Vue.js but I'm not sure in practice. If the coverage is 100% or near 100%, you should be able to do many of the things in the terminal or it is possible to have a completely server-side web application (not sure of the exact terminology, I mean like the delightful SourceHut[0] thing). The biggest concern is ongoing maintenance as Gitlab tends to move pretty quickly. [0] https://sourcehut.org/ https://sourcehut.org/
- granzymes 6y agoWhich projects that you follow moved from GitHub to Gitlab? None of the ones I keep an eye on have moved. I don't really see the point. GitHub has only improved since they were acquired.
- efiecho 6y ago> I don't really see the point. GitHub has only improved since they were acquired. Fully agree, but apparently some projects don't like having their infrastructure owned by Micosoft, that would be the only reason for switching in this case.
- sytse 6y agoGitLab 13.0 will release on the 22nd of May, 12 days from now. This blog post is about the upcoming deprecations in that release, not the features. The features that might ship in that release are on https://about.gitlab.com/upcoming-releases/ https://about.gitlab.com/upcoming-releases/ The last GitLab release was 12.10 which was release on April 22 https://about.gitlab.com/releases/2020/04/22/gitlab-12-10-released/ https://about.gitlab.com/releases/2020/04/22/gitlab-12-10-re... with Requirements Management and Autoscaling CI on AWS Fargate
- dnsmichi 6y agoI'd recommend watching the YouTube playlist, this helps a lot to get a grasp onto your very own use cases and possible features to solve them :) https://www.youtube.com/playlist?list=PL05JrBw4t0KqWysAAKFYYIE2Tf9IZB5bv https://www.youtube.com/playlist?list=PL05JrBw4t0KqWysAAKFYY...
- ThePhysicist 6y ago> An offset-based pagination limit of 50,000 is being applied to the /projects API endpoint on GitLab.com. This feels familiar. I once designed an API for retrieving a large number of items (hundreds of thousands to millions) from a Postgres database. I quickly learned that using OFFSET for such queries is an anti-pattern because it forces Postgres to iterate through all items before the specified offset just to retrieve the few items you requested. So allowing unlimited offsets is a great way to grind your database to a halt. I learned that a better way to do this is to use an index-based query instead, which Postgres can deal with much better. For example, you could give your items an auto-incrementing sequence number and tell the API consumer the sequence number of the last item in the result set. For the next request the consumer can use this number to start off where it left. While that restricts the way you can order items it will greatly speed up queries and allow efficient retrieval of a very large number of items without running into the slowdown effect caused by offset-based pagination.
- xwdv 6y agoIn the real world such indexing methods aren’t practical, once you have to do a full text search for example or sort by some attribute the index becomes useless. It’s rare to only want results presented in a certain order IMO.
- cheschire 6y agoYep. This is called seek vs scan. It's a common issue when you start hitting 10's of thousands of records.
- jraph 6y agoI recently hit a reCAPTCHA while trying to edit a ticket on one of my projects hosted on Gitlab.com. Since I block reCAPTCHA, this was silently failing and I had to debug this. This prevented me to edit this ticket. This is bad. I initially chose Gitorious when I needed to share an open source project because it was free software. I've been transfered to Gitlab.com and was ok with this back then. But requiring me to run this piece of non free tracking malware and solve a captcha to manage my free software project, and worse, making me force this upon the contributors of my projects? This is bullshit. I know the Gitlab staff is on HN, so thank you for your amazing software and for the free hosting, but be aware that this is making me move as soon as possible and actively discourage people from using Gitlab.com. ReCAPTCHA is not OK. Never. Cloudflare made the move [1]. Will you? [1] https://blog.cloudflare.com/moving-from-recaptcha-to-hcaptcha/ https://blog.cloudflare.com/moving-from-recaptcha-to-hcaptch...
- dnsmichi 6y agoHi, Developer Evangelist at GitLab here. Sorry that you had a hard time debugging the failure. I had gotten these reCaptcha questions myself recently. In the past months, there were numerous spam waves with flooding the issue tracker. You can see that with the increasingly high issue number, as their IDs have been burnt. I agree that reCaptcha is not the best solution. We have an ongoing discussion which also includes replacing reCaptcha with hCaptcha. While I cannot make a promise, I recommend that you subscribe to the issue. Also, please add your thoughts in there too :) https://gitlab.com/gitlab-org/gitlab/-/issues/21998#note_325800226 https://gitlab.com/gitlab-org/gitlab/-/issues/21998#note_325... Next to having captchas, there are other spam prevention ideas. One of them would be to follow a trust level model such as Discourse, but that needs more long-term planning and a fair model to let existing users becoming trusted. Please see https://gitlab.com/gitlab-org/gitlab/-/issues/14156#note_258252735 https://gitlab.com/gitlab-org/gitlab/-/issues/14156#note_258... for more details. Cheers, Michael
- jraph 6y agoNice! Thanks for your reply. I will take a look. I which good luck to the GitLab team against spam.
- altmind 6y agoas an admin and a user, im totally happy with gitlab. its a easy enough to administer, its reasonably priced even for a small company, and they dont try to push their "cloud offerings".