3 ms·
> I would respectfully suggest that the author is misusing CI. If you have trouble running your tests locally, you have a problem. I would respectfully suggest
by pyrale 3y ago
> I would respectfully suggest that the author is misusing CI. If you have trouble running your tests locally, you have a problem.
I would respectfully suggest that you misread the author. The issue isn't running tests locally, it's running the CI config locally.
I experienced the same problem with gitlab CI years ago, where, basically, you can lint the file and not much more. Past that, you need to run it through your CI and debug if you get slightly different results compared to running a script locally.
- capableweb 3y agoYeah, it's a horrible experience all around. CircleCI solved this problem like a decade ago, enabling SSH builds so you can troubleshoot straight up in the build itself, and once you've figured it out, just copy-paste the steps to your Makefile/CI config. I don't understand how one could build a CI service so long time after CircleCI launched, and still not have that very same feature (or something similar).