|
|
|
|
|
by cljacoby
845 days ago
|
|
Despite being framed as something for legacy C/C++ codebases, this is pretty good advice for setting up testing and CI automation around any project. I recently started on a new Rust project, and despite not having to worry about things like sanitizers as much, I followed a similar approach of getting it to compile locally, getting it compile in a docker container, setup automated CI/CD against all PRs. Although I would order the steps as 1, 3, 4, 2. Don't get out the chainsaw until you have CI/CD tests evaluating your code changes as you go. |
|