EVL

Table of Contents


Products, services and company names referenced in this document may be either trademarks or registered trademarks of their respective owners.

Copyright © 2017–2020 EVL Tool, s.r.o.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts.

Skip

(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.

Synopsis

syntax/Skip
evl skip
  <state> ( <run_id>... | <task_name>... [-o|--odate=<odate>] )
  [-p|--project=<project>] [-v|--verbose]

evl skip
  ( --help | --usage | --version )

Options

-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

Standard options:

--help

print this help and exit

--usage

print short usage information and exit

-v, --verbose

print to stderr info/debug messages of the component

--version

print version and exit

Examples

  1. Mark ‘some_job.evl’ as successfully finished with current date as Order Date:
    evl skip some_job.evl --odate today