4 ms·
It's git, so everyone has a copy of the repo. You can continue collaborating with send-email or some random SSH server. That's the beauty of a DSCM.
by panzi 3y ago
It's git, so everyone has a copy of the repo. You can continue collaborating with send-email or some random SSH server. That's the beauty of a DSCM.
- dnsmichi 3y agoGitLab team member here. If you plan on a GitLab mirror, including the Git repository and groups/projects, the direct transfer migration can be helpful https://about.gitlab.com/blog/2023/01/18/try-out-new-way-to-migrate-projects/ https://about.gitlab.com/blog/2023/01/18/try-out-new-way-to-... GitLab Geo can be an alternative for larger, high-availability setup requirements. https://docs.gitlab.com/ee/administration/reference_architectures/#high-availability-ha https://docs.gitlab.com/ee/administration/reference_architec...
- theta_d 3y agoYeah, but they also use the Pipeline features to build and deploy changes.
- hakre 3y agoBut they are clever, you can have the runner local. (They start to ruin that, but lets say, the idea is still visible.)
- mdaniel 3y agoOnly for `script: "echo hello world"` style jobs; anything more real makes `gitlab-runner exec` a total farce
- slowmovintarget 3y agoIf by local you mean local to a cloud instance that runs automated builds on every merge for specific branches, then yes. Granted, those build instance pull from the central git repo, and are triggered from GitLab... so also, no.
- hakre 3y agolocal like in tree.
- IshKebab 3y agoYeah you can't really. It doesn't support a ton of syntax and features. And they also said they were going to remove that ability too. Tbf to them after the inevitable response they did say they will come up with a proper solution, though that was some time ago. Obviously the real solution is to use Bazel and not to use Gitlab CI as a crap build system.
- dijit 3y agoBazel seems like a good idea but it's far too immature to actually work in the FOSS world, almost none of the external _rules are google quality, and it damn near requires a PhD to set up properly. I spent a good few months learning it and it's not the tool I would reach for in almost any circumstance unfortunately. Docs are also lacking, which is certainly not a problem with GitlabCI
- IshKebab 3y agoYeah it's definitely not simple, but I have repeatedly worked for companies that get stuck on all the problems that Bazel solves. I'm like "we should use Bazel, it solves this issue properly", and they're just like "nah... so anyway this is a big problem, how do we solve it??!". It would be nice if it had better integration with existing package managers like pip, cargo, npm and so on though. Vendoring your dependencies is fine for a big project like Chrome or Android or your company monorepo; it's a bit annoying for a small CLI tool or whatever. Another option is something like Landlock Make, but I haven't tried it.
- hakre 3y agoYeah, why not? But often GNU Make is fine for incremental builds.
- slowmovintarget 3y agoThis. Merge to master -> deploy to staging -> test runs -> push button enables for go-to-prod.
- fragmede 3y agoYou could, but in all honesty, most programmers (myself included) aren't as brilliant as Linus Torvalds, and, while I could stand up a git mirror in my sleep (because it's trivial - you should be able to as well), the finer points of coordinating work via a git mirror, when https://xkcd.com/1597/ https://xkcd.com/1597/ is the level of understand most people have with git, seems to say it's not going to work. Add on the fact that the git repository is the least bit of functionality (eg PRs and pipelines), and being down is a serious barrier to progress. http://Xkcd.com/303 http://Xkcd.com/303 but for GitHub is down.
- panzi 3y agoYeah, I didn't think of testing and deployment pipelines. Where I work we use GitHub actions for testing, but not for deployment. And our projects are small enough that I can easily run the tests in docker on my development PC.
- pjot 3y agoAgree - also sending a patch via email is definitely possible, but not at all practical. I’m not sure if I’ve ever come across anyone who’s gitops workflows include email
- theamk 3y agoyou don't need to send patches via email, you can push them over ssh pretty easily For example on my team we have a few devs who push patches from laptop directly to their work desktop, as a part of day-to-day synchronization. No central ssh server involved.
- BlacCnOuNj0FG5 3y agoYou've never come across the Linux kernel? The Linux kernels process isn't practical? Okay, that's an interesting point of view.