4
msdsk
2y

I love that I need to fucking babysit the fucking CI pipeline because, half of the times, it just RANDOMLY FAILS and I need to hit that fucking retry button like a 19th century kid respooling a loom.

Comments
  • 0
    why not just fix it 😐
  • 0
    Same here.
    Azure devops?
  • 0
    Don't pretty much all ci providers have an automatic retry option?
  • 0
    "You cannot disable the E2E tests".

    Lol. You don't know my powers. XD
    I disabled the E2E tests. Suddenly everything worked like a charm.

    Small story of how I fixed a build pipeline for good. There was a lot of rage to deal with afterwards, but I was just too tired of that bukkake mess they called E2E pipeline...

    (It was a selenium protractor angular thingamabob... If I had to do a metaphor, I'd describe it as an elderly dementia patient with a defilibrator suffering from dementia... If that thing worked it was a miracle).

    Document failures.

    If the same part fails, rip it out, let the madness begin and just say: This fucked up piece of garbage costs us money, either rewrite or it will stay off.
  • 0
    Custom build pipeline, custom versioning system. Component version is kept in two places, one of them gets updated one of them doesn't. DevOps team: "yeah we know it happens, its the developer jobs to make sure it was updated in both places".
Add Comment