Stages and stepsSource:
tic works in a declarative way, centered around the
This file contains the definition of the steps to be run in each stage:
add_step(), or macros like
Normally, this file is never executed directly.
Running these functions in an interactive session will not carry out
the respective actions.
Instead, a description of the code that would have been run is printed
to the console.
tic.R to configure your CI builds.
vignette("build-lifecycle", package = "tic") for more details.
Path to the stage definition file, default:
TRUEto force loading from file even if a configuration exists. By default an existing configuration is not overwritten by
TRUEto turn off verbose output.
A named list of opaque stage objects with a
and a corresponding
print() method for pretty output.
Use the high-level
add_step() functions to configure,
and the stages functions to run.
Stages and steps defined using tic's DSL are stored in an
internal object in the package.
The stages are accessible through
When running the stages, by default a configuration defined
tic.R file is loaded with
use_tic() for setting up a
For interactive tests, an empty storage can be initialized
This happens automatically the first time
dsl_get() is called
(directly or indirectly).