Open lexman opened 9 years ago
For the moment, tuttle only remembers the logs for the last run.
An option (in the command line ?) would allow preserving the full history.
From this history, projection of execution of each process (and the whole workflow) could be computed, like in Jenkins.
A tuttle invalidate all command could reset the whole process without removing history (better than removing the .tuttle directory
tuttle invalidate all
.tuttle
Implementation would be easyier if workflow's state is in a database. Eg a sqlite database
For the moment, tuttle only remembers the logs for the last run.
An option (in the command line ?) would allow preserving the full history.
From this history, projection of execution of each process (and the whole workflow) could be computed, like in Jenkins.
A
tuttle invalidate allcommand could reset the whole process without removing history (better than removing the.tuttledirectoryImplementation would be easyier if workflow's state is in a database. Eg a sqlite database