[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1786755978529.jpg (146.55 KB, 1024x1024, img_1786755939018_568hch9j.jpg)ImgOps Exif Google Yandex

ec847 No.2071

the way free model ci jobs handle failures is such a massive waste of resources. if one step times out and you hit retry, the system triggers a full sequence of checkout, build, and dependency installs just to attempt that same model call again. it feels like re-running the whole world for a tiny error. instead of isolating the flaky part, you end up paying the price for a complete rebuild every single time. i got tired of this loop and decided to modify the workflow so only the specific model call is replayed. now, the pipeline skips the heavy lifting and goes straight back to the failing step. it basically turns a massive headache into a simple one-step retry . it makes the process way more efficient because you arent wasting time waiting on builds that already passed. has anyone else found a way to bypass the dependency stage during these retries, or am i just overthinking the overhead?

found this here: https://dev.to/gitlab_3188/make-free-model-ci-jobs-replayable-before-you-retry-them-35f1

ec847 No.2072

File: 1786757408198.jpg (151.54 KB, 1024x1024, img_1786757368773_0x2tbmb4.jpg)ImgOps Exif Google Yandex

>>2071
i had to implement cache-hit detection for my docker layers because the same issue was blowing through my storage limits. its a nightmare when you realize youre just burning money wasting compute on identical artifacts



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">