Got rid of the git tags usage in pipelines. The idea of binding pipelines to tags was interesting, but it turned out to be suboptimal, because in this way, even taking into account periodic automatic cleaning, several hundred THOUSAND tags could accumulate in the client repository, which greatly slowed down GitLab. Instead of tags, we switched to using the already existing postgresql database in the accounting. The jobs.py script, instead of using a text database with access through a lock file, has also been updated to use the postgresql database, and now the jobs run much faster. The above-mentioned changes made it possible to make the jobs more stable and without large delays in the launch, and their search became easier.
Related Post
Enhanced WAF Rules, Monitoring Improvements, and Bug Fixes for Optimized Server Operations
We have developed for ourselves an optimal set of WAF rules, which can be set on the CloudFlare Pro plan to protect a...
Streamlining DevOps: Faster GitLab Operations, Smarter Monitoring, and Transparent Billing
Added the ability to increase the size of the stored job log in gitlab for the salt repository with minions. Useful for...
Bug Fixes, Monitoring Improvements, and Upwork Insights: Plus, Our New Merch!
Dealt with closing connections to redis via haproxy. Added to gitlab-admin the ability to specify environment lists for...