|
|
|
|
|
|
by deckard1
1550 days ago
|
|
|
thanks for the downvotes. > it's because you chose to do it to yourself. I didn't choose shit. My company did. Why are you putting this on me? > Both my personal projects and my $dayjob repositories have every test Congrats on not actually using GitHub actions? I guess? So many people here sucking Microsoft cock. And there is yet another incident today! What's that make, three days in a row now? Four, if we're actually counting. They aren't even hitting 2 nines uptime. Two. Fucking. Nines. Going on many years now. But apparently that is just fine because everyone is running self-hosted infra in parallel to their cloud shit. |
|
|
>But apparently that is just fine because everyone is running self-hosted infra in parallel to their cloud shit.
In your haste to complain about downvotes and accuse other people of "sucking Microsoft cock", you forgot to actually read the comment you replied to.
Things in the comment you replied to:
1. An assertion that one can write their CI in a script that is not tied to one CI vendor, so that it's easy to run the same steps as what the CI does locally or in another CI. ie, no lock-in to the current CI.
Things not in the comment you replied to:
1. An assertion that I run self-hosted CI in addition to GitHub Actions.
2. An assertion that GitHub has good uptime.