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

Use ‘Skip’ to produce log entry like in the case an EVL <job> or <workflow> would be successfully finished (in fact marked as ‘SKIP’). This is useful when other jobs or workflows are waiting for such a job/workflow.

Skip

is to be used in EVL workflow structure definition file, i.e. in EWS file.

evl skip

is intended for standalone usage, i.e. to be invoked from command line.

EWS is EVL workflow definition file, for details see man evl-ews(5).

Synopsis

syntax/Skip
Skip
  ( <job>.evl | <workflow>.ewf | <script>.sh )
  [-o|--odate=<odate>] [-p|--project=<project>]

evl skip
  ( <job>.evl | <workflow>.ewf | <script>.sh )
  [-o|--odate=<odate>] [-p|--project=<project>]
  [-v|--verbose]

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

Options

-o, --odate=<odate>

run evl workflow with specified <odate>, environment variable ‘EVL_ODATE’ is 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 ‘$ODATE’ (in EWS file):
    Skip some_job.evl