Carlos' research group at MPI recently transitioned from an independent build process they were using for their R packages to a new and pretty slick continuous integration tool called Travis-CI. Our current build function is really nice---kudos to Grey---but I think this tool is worth looking into and wouldn't be too hard to implement.
Some key advantages are:
Checks performance of package on "clean" system (good for use-friendliness)
provides transparency into the build process, i.e. all users can see the build reports (like our current "israd.build"-built log file)
automatically runs the build process when commit changes are detected in the repository
@ShaneStoner and I are planning to look into it, with the help of some of Carlos' group members.
jb388
commented
4 years ago
Carlos' research group at MPI recently transitioned from an independent build process they were using for their R packages to a new and pretty slick continuous integration tool called Travis-CI. Our current build function is really nice---kudos to Grey---but I think this tool is worth looking into and wouldn't be too hard to implement.
Some key advantages are:
@ShaneStoner and I are planning to look into it, with the help of some of Carlos' group members.
Comments, questions or thoughts?