3 ms·
"CI/CD" tends to be associated with "building/deploying the software from a fresh environment". e.g. Aim to reduce mistakes of "I forgot to check these importan
by rgoulter 4y ago
"CI/CD" tends to be associated with "building/deploying the software from a fresh environment". e.g. Aim to reduce mistakes of "I forgot to check these important files into the code repository".
Some CI/CD services like GitHub Actions or TravisCI will take a configuration file which declares the CI/CD steps to run. These services will run the build on some machine; but the point of "self hosting is good" is that you'll be able to run the CI/CD build with a more powerful host, and complete the CI/CD build quicker compared to the 'managed' cloud builders.
- lanstin 4y agoEven locally,I’m will have my active dev directory, and a just git directory where I git clean -d -f -x ; git pull ; make periodically to protect against such distressingly common errors. Doesn’t address local tools dependencies, but those tend to be less (tho golangci-lint is like ten minutes of downloads for the over 100 deps (and due to or terrifically slow MITMed network proxies) I finally just made all the build tooling a published base image for the actual builds).