4 ms·
Same, my CI has looked like this for years now: ./script/prepare-env ./script/test ./script/build ./script/deploy It's worked in virtually eve
by mikewhy 6y ago
Same, my CI has looked like this for years now:
./script/prepare-env
./script/test
./script/build
./script/deploy
It's worked in virtually every CI system, and locally. Bonus point, it really points out the amount of ceremony some CI platforms require to map simple commands into their pipelines. Looking at you, CircleCI.
- mnahkies 6y agoI found an approach like this was especially nice on teamcity in conjunction with its template feature. Individual apps were still able to have whatever specific thing they needed, but you could globally add a step, eg a security scanning tool or slack notification by modifying the template only rather than 100s of build configuration files as the GitHub / circleci approach seems to encourage. Adding a new pipeline basically just meant naming it and selecting the VCS URL