A simple utility that allows local runs of tests to be reported to branches as evidence that the tests do in fact pass.
This was built beacuse I get really tired of waiting for tests to get triggered, build, upload, and then set the status. Normally by the time I have pushed a branch, I have already ran the tests to see that they work.
Because this is designed to be run on the same server, it can take advantage of caching results of tests, builds, etc. it should be faster then starting from scratch each time.
prof # runs in CI/CD mode. watches local branches for changes and runs makefile targets
prof {branch|tag|commit} # runs a single build and uploads the results.
prof --target 'build' # override the target used to build
prof --origin 'git@github.com:dbarney/professor.git' # pull changes from this remote and don't try and use the current folder as a source for changes.
prof --auto-publish # don't wait for a remote to be updated, after the build works, upload the result
prof --build 'remote/origin/*' # build refs matching this pattern
# how about how to run it on a different server?
prof --auto-publish --origin 'git@github.com:dbarney/professor.git' --build 'remote/origin/*' --poll 5m
# what about a team/individual server?
prof --auto-publish --origin 'git@github.com:dbarney/professor.git' --build 'remote/origin/{team}/{user}/*' --poll 5m
GITHUB_TOKEN - a token with gist and repo permissions
GITHUB_USER - the user associated with the token.
A lot of other settings currently aren't exposed and are set by reading the git config, and by setting fairly sane defaults. That being said, if need be in the future this can be changed with a simple PR to make them more configurable.
Need to add webhook support so that polling isn't needed. Need to add tag fetching support.
# maybe this is how it should be run. no auto stuff, just designed to
# be run from a hook of some sort.
# it is up to the user where and when it runs.
prof sha1234asdf make build