It looks like all the steps here are covered https://docs.ropensci.org/tic/articles/build-lifecycle.html in googleCloudRunner::cr_buildstep() functions but it doesn't have the CI stages (before_install etc.) unless I ID the step which is ok I guess, I would need to do some after_failure bash hacking.
It seems the strategy is to install then execute tic code on all the buildsteps during the build so tic controls execution - this keeps the UX consistent between all the CI providers but does reduce readability of the generated yaml and also restricts each buildstep to what R code environment can call.
Whereas googleCloudRunner is generating the yaml file that has docker containers for each buildstep, so each execution environment can use different languages, sharing a common workspace.
Raised https://github.com/ropensci/tic/issues/248
It looks like all the steps here are covered https://docs.ropensci.org/tic/articles/build-lifecycle.html in
googleCloudRunner::cr_buildstep()functions but it doesn't have the CI stages (before_installetc.) unless I ID the step which is ok I guess, I would need to do someafter_failurebash hacking.It seems the strategy is to install then execute tic code on all the buildsteps during the build so tic controls execution - this keeps the UX consistent between all the CI providers but does reduce readability of the generated yaml and also restricts each buildstep to what R code environment can call.
Whereas googleCloudRunner is generating the yaml file that has docker containers for each buildstep, so each execution environment can use different languages, sharing a common workspace.