You are right. Small teams absolutely do not need to execute code remotely, especially if the cost is having an always on job server. My team writes test outpu

You are right. Small teams absolutely do not need to execute code remotely, especially if the cost is having an always on job server. My team writes test output to our knowledge base: bugout trap --title "$REPO_NAME tests: $(date -u +%Y%m%d-%H%M)" --tags $REPO_NAME,test,zomglings,$(git rev-parse HEAD) -- ./test.sh This runs test.sh and reports stdout and stderr to our team knowledge base with tags that we can use to find information later on. For example, to find all failed tests for a given repo, we would perform a search query that looked like this: "#<repo> #test !#exit:0". The knowledge base (and the link to the knowledge base entry) serve as proof of tests. We also use this to keep track of production database migrations.