WHY THE FUCK ARE WE ONLY KEEPING THE LAST 10 BUILD ARTIFACTS IN ARTIFACTORY?!

THAT IS LITERALLY THE OPPOSITE OF HOW YOU'RE SUPPOSED TO USE IT

NOW I CAN'T ROLL BACK PROD CHANGES TO A WORKING VERSION BECAUSE IT LITERALLY DOESN'T EXIST ANYMORE

FUCK YOU, IT'S YOUR FIRE NOW

Do you work at Facebook by any chance?

@electrineer perfect Q for every incoming rant, untill that shit's fixed x)

@electrineer Nope. Place I work for is far more incompetent.

Something going wrong with FB (ya know, moreso that usual)? I deleted my account long ago.

@obsecurity fb, ig and wa all have problems with pictures and other files

Status 503 to be exact

@obsecurity quick question, how on earth did you publish 10 consecutive failing builds?

@Commodore
- No automatic CI/CD
- Hardly any test coverage that doesn't get even get run as part of a build
- Sloppy code that gets approved and merged into trunk almost immediately before it can be reviewed
- Our pre-production environment is almost completely different than live production, so results can't be reproduced accurately

Just to name a few

That sounds like a nightmare.

My company has something similar to this in a repo that is built into a docker container. It's just absolute toxic poison. It's an R container that has over 200 packages in it but because of the way R package versions are handled (very lazily) we can't guarantee if a build with zero changes will be the same as the one before.

If anybody ever makes a change and needs to rebuild, who knows what will break. 6 day outage before for adding a 0 to a configuration value.

@obsecurity that makes a lot more sense, thanks!

@Commodore Something I was wondering too!