search

RangeShifter / RangeShifter_batch

RangeShifter batch version with new structure using subtree for RS core files
GNU General Public License v3.0
0 stars 0 forks source link

Deploy Continuous Integration via GitHub Action #9

Closed TheoPannetier closed 1 year ago

TheoPannetier commented 1 year ago

A first step would be to simply have a triggered build on every push. If the program builds successfully, we are happy.

Eventually, we will want to have unit tests being run as part of the build, and probably systemic tests running the built program on predetermined input.

TheoPannetier commented 1 year ago

Well I ended up going a bit further than what this issue encompassed. As of https://github.com/RangeShifter/RangeShifter_batch_dev/commit/0d68beb7eb6e66f6fd77deff3a03b6058d362c5f RangeShifter is built, run, and minimally tested (compare that simulation output in Debug mode matches a set of pre-set Output from a previous run with same RNG).

TheoPannetier commented 1 year ago

This is a good point to stop for now :)