search

Ivan-Johnson / LifeLogServer

A DIY life tracking app
0 stars 0 forks source link

Setup a continuous integration server #24

Open Ivan-Johnson opened 4 years ago

Ivan-Johnson commented 4 years ago

A continuous integration server is needed so that the GitHub page can show a live view of build/test stats.

I'm inclined to self-host a Jenkins repo.

Ivan-Johnson commented 4 years ago

Note that #27 should be complete before starting work on this.

Ivan-Johnson commented 4 years ago

https://github.com/Ivan-Johnson/LifeLogServer/commit/c7ebcff3adb36da57ae92e336e8b4b60a4c2a5a1 adds a git hook which should ~prevent accidental commits of failing tests. That should be sufficient for continuous integration which is a big part of this issue, but a more complex setup is still needed so that GitHub can show the results.

Might it be possible for the hooks to output the necessary graphics and then include those from the readme? To minimize the issue of --no-verify allowing the information to be out of date, there could be additional text files storing the current package version & most recent tested version and both could be included in the readme. I don't bump the version number with every commit so it would still be ambiguous, but at least it prevents it from going wildly out of date... This approach is much less complex in that it all runs locally and I wouldn't have to worry about setting up my server to host/redirect to graphics.