You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This idea builds on #79, it needs the ability to provide boolean expressions using the template expression substitution {{...}} syntax.
When writing a job template, you're defining an interface with parameters to control what should happen when the job runs. There are some parts of a job that would be useful to control this way, that currently you can't:
Control whether a particular job or step environment runs or not. Same as for controlling the step, but for environment onEnter/onExit.
Control whether specific host requirements are active or not. You could implement a job template that supports either CPU-only or GPU-accelerated modes, and select which host requirements to use based on a parameter.
For each case, we could add a new field "enableIf" that contains an expression evaluating to either true or false. An example step could look like:
...
parameterDefinitions:
- name: ShouldEncodeVideotype: BOOL
...
- name: CreateVideoFromRender# This is a new field. If it evaluates to true, the step runs as part of the job. If it evaluates to false, it does not.enableIf: "{{Param.ShouldEncodeVideo}}"dependencies:
- dependsOn: RenderScenescript:
actions:
onRun:
command: bashargs: [ "{{Task.File.Encode}}"]
...
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This idea builds on #79, it needs the ability to provide boolean expressions using the template expression substitution
{{...}}syntax.When writing a job template, you're defining an interface with parameters to control what should happen when the job runs. There are some parts of a job that would be useful to control this way, that currently you can't:
For each case, we could add a new field "enableIf" that contains an expression evaluating to either true or false. An example step could look like:
Beta Was this translation helpful? Give feedback.
All reactions