(since EVL 2.0)
Use ‘skip’ to produce log entry like in the case an EVL task (i.e. job, workflow or script, or waiting for a file) would be successfully finished (in fact marked as ‘SKIP’). This is useful when other jobs or workflows are waiting for such EVL task.
It is actually an alias to ‘evl set skip’ commands.
evl skip <state> ( <run_id>... | <task_name>... [-o|--odate=<odate>] ) [-p|--project=<project>] [-v|--verbose] evl skip ( --help | --usage | --version )
- -o, --odate=<odate>
to specify particular Order Date, environment variable ‘EVL_ODATE’ is then ignored
- -p, --project=<project_dir>
specify project folder if not the current working one
print this help and exit
print short usage information and exit
- -v, --verbose
print to stderr info/debug messages of the component
print version and exit
- Mark ‘some_job.evl’ as successfully finished with current date as Order Date:
evl skip some_job.evl --odate today