Copyright (c) Microsoft Corporation. All rights reserved. Licensed under the MIT License. See License.txt in the project root for license information. Code generated by Microsoft (R) AutoRest Code Generator.
/** * Copyright (c) Microsoft Corporation. All rights reserved. * Licensed under the MIT License. See License.txt in the project root for * license information. * * Code generated by Microsoft (R) AutoRest Code Generator. */
package com.microsoft.azure.management.batch; import java.util.List; import com.fasterxml.jackson.annotation.JsonProperty;
A task which is run when a compute node joins a pool in the Azure Batch service, or when the compute node is rebooted or reimaged. In some cases the start task may be re-run even though the node was not rebooted. Due to this, start tasks should be idempotent and exit gracefully if the setup they're performing has already been done. Special care should be taken to avoid start tasks which create breakaway process or install/launch services from the start task working directory, as this will block Batch from being able to re-run the start task.
/** * A task which is run when a compute node joins a pool in the Azure Batch * service, or when the compute node is rebooted or reimaged. * In some cases the start task may be re-run even though the node was not * rebooted. Due to this, start tasks should be idempotent and exit gracefully * if the setup they're performing has already been done. Special care should * be taken to avoid start tasks which create breakaway process or * install/launch services from the start task working directory, as this will * block Batch from being able to re-run the start task. */
public class StartTask {
The command line of the start task. The command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. Required if any other properties of the startTask are specified.
/** * The command line of the start task. * The command line does not run under a shell, and therefore cannot take * advantage of shell features such as environment variable expansion. If * you want to take advantage of such features, you should invoke the shell * in the command line, for example using "cmd /c MyCommand" in Windows or * "/bin/sh -c MyCommand" in Linux. Required if any other properties of the * startTask are specified. */
@JsonProperty(value = "commandLine") private String commandLine;
A list of files that the Batch service will download to the compute node before running the command line.
/** * A list of files that the Batch service will download to the compute node * before running the command line. */
@JsonProperty(value = "resourceFiles") private List<ResourceFile> resourceFiles;
A list of environment variable settings for the start task.
/** * A list of environment variable settings for the start task. */
@JsonProperty(value = "environmentSettings") private List<EnvironmentSetting> environmentSettings;
The user identity under which the start task runs. If omitted, the task runs as a non-administrative user unique to the task.
/** * The user identity under which the start task runs. * If omitted, the task runs as a non-administrative user unique to the * task. */
@JsonProperty(value = "userIdentity") private UserIdentity userIdentity;
The maximum number of times the task may be retried. The Batch service retries a task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the task. If the maximum retry count is -1, the Batch service retries the task without limit.
/** * The maximum number of times the task may be retried. * The Batch service retries a task if its exit code is nonzero. Note that * this value specifically controls the number of retries. The Batch * service will try the task once, and may then retry up to this limit. For * example, if the maximum retry count is 3, Batch tries the task up to 4 * times (one initial try and 3 retries). If the maximum retry count is 0, * the Batch service does not retry the task. If the maximum retry count is * -1, the Batch service retries the task without limit. */
@JsonProperty(value = "maxTaskRetryCount") private Integer maxTaskRetryCount;
Whether the Batch service should wait for the start task to complete successfully (that is, to exit with exit code 0) before scheduling any tasks on the compute node. If true and the start task fails on a compute node, the Batch service retries the start task up to its maximum retry count (maxTaskRetryCount). If the task has still not completed successfully after all retries, then the Batch service marks the compute node unusable, and will not schedule tasks to it. This condition can be detected via the node state and scheduling error detail. If false, the Batch service will not wait for the start task to complete. In this case, other tasks can start executing on the compute node while the start task is still running; and even if the start task fails, new tasks will continue to be scheduled on the node. The default is true.
/** * Whether the Batch service should wait for the start task to complete * successfully (that is, to exit with exit code 0) before scheduling any * tasks on the compute node. * If true and the start task fails on a compute node, the Batch service * retries the start task up to its maximum retry count * (maxTaskRetryCount). If the task has still not completed successfully * after all retries, then the Batch service marks the compute node * unusable, and will not schedule tasks to it. This condition can be * detected via the node state and scheduling error detail. If false, the * Batch service will not wait for the start task to complete. In this * case, other tasks can start executing on the compute node while the * start task is still running; and even if the start task fails, new tasks * will continue to be scheduled on the node. The default is true. */
@JsonProperty(value = "waitForSuccess") private Boolean waitForSuccess;
The settings for the container under which the start task runs. When this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all task environment variables are mapped into the container, and the task command line is executed in the container.
/** * The settings for the container under which the start task runs. * When this is specified, all directories recursively below the * AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) * are mapped into the container, all task environment variables are mapped * into the container, and the task command line is executed in the * container. */
@JsonProperty(value = "containerSettings") private TaskContainerSettings containerSettings;
Get the command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. Required if any other properties of the startTask are specified.
Returns:the commandLine value
/** * Get the command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. Required if any other properties of the startTask are specified. * * @return the commandLine value */
public String commandLine() { return this.commandLine; }
Set the command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. Required if any other properties of the startTask are specified.
Params:
  • commandLine – the commandLine value to set
Returns:the StartTask object itself.
/** * Set the command line does not run under a shell, and therefore cannot take advantage of shell features such as environment variable expansion. If you want to take advantage of such features, you should invoke the shell in the command line, for example using "cmd /c MyCommand" in Windows or "/bin/sh -c MyCommand" in Linux. Required if any other properties of the startTask are specified. * * @param commandLine the commandLine value to set * @return the StartTask object itself. */
public StartTask withCommandLine(String commandLine) { this.commandLine = commandLine; return this; }
Get the resourceFiles value.
Returns:the resourceFiles value
/** * Get the resourceFiles value. * * @return the resourceFiles value */
public List<ResourceFile> resourceFiles() { return this.resourceFiles; }
Set the resourceFiles value.
Params:
  • resourceFiles – the resourceFiles value to set
Returns:the StartTask object itself.
/** * Set the resourceFiles value. * * @param resourceFiles the resourceFiles value to set * @return the StartTask object itself. */
public StartTask withResourceFiles(List<ResourceFile> resourceFiles) { this.resourceFiles = resourceFiles; return this; }
Get the environmentSettings value.
Returns:the environmentSettings value
/** * Get the environmentSettings value. * * @return the environmentSettings value */
public List<EnvironmentSetting> environmentSettings() { return this.environmentSettings; }
Set the environmentSettings value.
Params:
  • environmentSettings – the environmentSettings value to set
Returns:the StartTask object itself.
/** * Set the environmentSettings value. * * @param environmentSettings the environmentSettings value to set * @return the StartTask object itself. */
public StartTask withEnvironmentSettings(List<EnvironmentSetting> environmentSettings) { this.environmentSettings = environmentSettings; return this; }
Get if omitted, the task runs as a non-administrative user unique to the task.
Returns:the userIdentity value
/** * Get if omitted, the task runs as a non-administrative user unique to the task. * * @return the userIdentity value */
public UserIdentity userIdentity() { return this.userIdentity; }
Set if omitted, the task runs as a non-administrative user unique to the task.
Params:
  • userIdentity – the userIdentity value to set
Returns:the StartTask object itself.
/** * Set if omitted, the task runs as a non-administrative user unique to the task. * * @param userIdentity the userIdentity value to set * @return the StartTask object itself. */
public StartTask withUserIdentity(UserIdentity userIdentity) { this.userIdentity = userIdentity; return this; }
Get the Batch service retries a task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the task. If the maximum retry count is -1, the Batch service retries the task without limit.
Returns:the maxTaskRetryCount value
/** * Get the Batch service retries a task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the task. If the maximum retry count is -1, the Batch service retries the task without limit. * * @return the maxTaskRetryCount value */
public Integer maxTaskRetryCount() { return this.maxTaskRetryCount; }
Set the Batch service retries a task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the task. If the maximum retry count is -1, the Batch service retries the task without limit.
Params:
  • maxTaskRetryCount – the maxTaskRetryCount value to set
Returns:the StartTask object itself.
/** * Set the Batch service retries a task if its exit code is nonzero. Note that this value specifically controls the number of retries. The Batch service will try the task once, and may then retry up to this limit. For example, if the maximum retry count is 3, Batch tries the task up to 4 times (one initial try and 3 retries). If the maximum retry count is 0, the Batch service does not retry the task. If the maximum retry count is -1, the Batch service retries the task without limit. * * @param maxTaskRetryCount the maxTaskRetryCount value to set * @return the StartTask object itself. */
public StartTask withMaxTaskRetryCount(Integer maxTaskRetryCount) { this.maxTaskRetryCount = maxTaskRetryCount; return this; }
Get if true and the start task fails on a compute node, the Batch service retries the start task up to its maximum retry count (maxTaskRetryCount). If the task has still not completed successfully after all retries, then the Batch service marks the compute node unusable, and will not schedule tasks to it. This condition can be detected via the node state and scheduling error detail. If false, the Batch service will not wait for the start task to complete. In this case, other tasks can start executing on the compute node while the start task is still running; and even if the start task fails, new tasks will continue to be scheduled on the node. The default is true.
Returns:the waitForSuccess value
/** * Get if true and the start task fails on a compute node, the Batch service retries the start task up to its maximum retry count (maxTaskRetryCount). If the task has still not completed successfully after all retries, then the Batch service marks the compute node unusable, and will not schedule tasks to it. This condition can be detected via the node state and scheduling error detail. If false, the Batch service will not wait for the start task to complete. In this case, other tasks can start executing on the compute node while the start task is still running; and even if the start task fails, new tasks will continue to be scheduled on the node. The default is true. * * @return the waitForSuccess value */
public Boolean waitForSuccess() { return this.waitForSuccess; }
Set if true and the start task fails on a compute node, the Batch service retries the start task up to its maximum retry count (maxTaskRetryCount). If the task has still not completed successfully after all retries, then the Batch service marks the compute node unusable, and will not schedule tasks to it. This condition can be detected via the node state and scheduling error detail. If false, the Batch service will not wait for the start task to complete. In this case, other tasks can start executing on the compute node while the start task is still running; and even if the start task fails, new tasks will continue to be scheduled on the node. The default is true.
Params:
  • waitForSuccess – the waitForSuccess value to set
Returns:the StartTask object itself.
/** * Set if true and the start task fails on a compute node, the Batch service retries the start task up to its maximum retry count (maxTaskRetryCount). If the task has still not completed successfully after all retries, then the Batch service marks the compute node unusable, and will not schedule tasks to it. This condition can be detected via the node state and scheduling error detail. If false, the Batch service will not wait for the start task to complete. In this case, other tasks can start executing on the compute node while the start task is still running; and even if the start task fails, new tasks will continue to be scheduled on the node. The default is true. * * @param waitForSuccess the waitForSuccess value to set * @return the StartTask object itself. */
public StartTask withWaitForSuccess(Boolean waitForSuccess) { this.waitForSuccess = waitForSuccess; return this; }
Get when this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all task environment variables are mapped into the container, and the task command line is executed in the container.
Returns:the containerSettings value
/** * Get when this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all task environment variables are mapped into the container, and the task command line is executed in the container. * * @return the containerSettings value */
public TaskContainerSettings containerSettings() { return this.containerSettings; }
Set when this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all task environment variables are mapped into the container, and the task command line is executed in the container.
Params:
  • containerSettings – the containerSettings value to set
Returns:the StartTask object itself.
/** * Set when this is specified, all directories recursively below the AZ_BATCH_NODE_ROOT_DIR (the root of Azure Batch directories on the node) are mapped into the container, all task environment variables are mapped into the container, and the task command line is executed in the container. * * @param containerSettings the containerSettings value to set * @return the StartTask object itself. */
public StartTask withContainerSettings(TaskContainerSettings containerSettings) { this.containerSettings = containerSettings; return this; } }