Difference between revisions of "Stages"
From CCIL
(→See also) |
(→Things to know) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 13: | Line 13: | ||
** There is no restriction on the type of the objects. | ** There is no restriction on the type of the objects. | ||
** '''Can''' be overridden from the command line, using the syntax, described [[How to provide parameter values from the command line?|here]]. | ** '''Can''' be overridden from the command line, using the syntax, described [[How to provide parameter values from the command line?|here]]. | ||
| + | |||
| + | === Parameter expansion === | ||
| + | |||
| + | The parameter expansion allows the implementation of more complex logic in pipelines. | ||
| + | |||
| + | The syntax is: | ||
| + | <code>${NAME}</code> | ||
| + | |||
| + | This string will be replaced by the value of the run-time variable NAME. | ||
| + | |||
| + | You can use also: | ||
| + | <code>${@NAME}</code> | ||
| + | |||
| + | Which will be replaced by the value of the run-time variable, assigned to NAME. | ||
| + | |||
| + | === Pred-defined constants === | ||
| + | |||
| + | TBA | ||
== Lists == | == Lists == | ||
| Line 24: | Line 42: | ||
* [[Pipelines]] | * [[Pipelines]] | ||
* [[Parameter expressions]] | * [[Parameter expressions]] | ||
| + | * [[How to provide parameter values from the command line?]] | ||
Latest revision as of 05:12, 30 April 2021
This page gives a comprehensive list of the stages, predefined in CCIL. One can learn how to create own ones here TBA.
Contents
Things to know
There are 2 kinds of parameters
- Static - They come from the context.properties itself. Although there is some to use dynamic behavior trough the arguments from command line mechanic, their content is generally evaluated when the context is loaded.
- Accessed trough the the confXXX methods from the AbstractStageBase class.
- They all should be convertible to java.lang.String.
- Cannot be overridden from the command line, using the syntax, described here.
- Dynamic - Contained in the RuntimeEnvironment. As the name suggests, the name-value pairs there exist only during the execution of a pipeline.
- There is no restriction on the type of the objects.
- Can be overridden from the command line, using the syntax, described here.
Parameter expansion
The parameter expansion allows the implementation of more complex logic in pipelines.
The syntax is:
${NAME}
This string will be replaced by the value of the run-time variable NAME.
You can use also:
${@NAME}
Which will be replaced by the value of the run-time variable, assigned to NAME.
Pred-defined constants
TBA
Lists
Implementing
TBA
