GitLab Runners

[@retropaganda8442]

The answer to our build performance problems was to disable Gitlab's Git handling entirely, use dedicated, always on, persistent runners, write our own custom script code to update a git clone directory that's shared by all builds done by the same machine, and do shared-clones/worktree-checkouts that share the storage with the central git clone. We keep all sources and all built files for every branch for incremental builds and quick merge request code quality reports. It requires quite some filesystem storage on each runner, but on the other hand it solves all performance problems. Any other approach is bound to fail performance-wise and cost much much more.

[@omidzamani]

خیلی عالی بود این توضیحات، ممنونم گیت لب جان .

[@rhysjenkin3320]

Can you add a link to the aws best practice link mentioned 26:00?

[@raghupathym25]

Thanks for the video. How to deploy via cicd if machine is behind the windows bastion host. My aws instance is behind windows bastion. Is this task possible. Currently my cicd is deploying to dev environment(public IP), the requirement is to deploy to prod environment(privateIP)

[@markcuello5]

HELP