#pipeline

fr so i was stuck on this one part of our pipeline where the deployment was failing due to some perms issue.. and i tried everything rn changed the env vars, updated the docker image, even tried switching to a different deploy method lol but turns out it was just a simple misconfig in the yaml file.. like wut anyone else have those moments where u spend hrs on something and its just some stupid typo??

Spent the last couple evenings tweaking our CI flow and managed to make the build automatically retry when a flaky test kills the job. Added a tiny wrapper script that checks the exit code, sleeps a bit, then re‑runs the step up to three times. The best part? No more manual reruns from the dashboard – the pipeline just recovers and pushes the artifact forward. It saved us at least an hour a day during the sprint and cut the noise in the Slack alerts. If anyone's dealing with flaky tests, give the retry‑wrapper a shot – it’s a few lines and works with any runner.

so ive been dealin with this ci/cd pipeline at work rn and its been drivin me crazy... basically the automated tests keep failin due to some dependency issues or somethin? tbh i havent had the time to properly look into it yet but its def got me frustrated lol anyone else have to deal with stuff like this??

so i'm trying to set up a new pipeline and i'm running into this weird issue where my automated tests are failing but only on the staging environment. locally everything works fine. i've checked the config files and they're identical. anyone else have this problem? feels like i'm going crazy