8 docs tagged with "schedule"

Deploy keeps all active tasks in the Monitoring section, which is located under the search bar at the top left of the screen.

You can create a package retention policy (policy.PackageRetentionPolicy) that retains the deployment packages based on the configured regular expression. Deployed packages are never removed by the package retention policy. If a deployed package is part of the packages identified for removal, then it will be skipped, with no impact on other packages.

Deploy records and archives information about all tasks that it executes. This information is available through the statistics, graphs, and task archives on the Reports screen.

A task is an activity in Deploy. When starting a deployment, Deploy will create and start a task. The task contains a list of steps that must be executed to successfully complete the task. Deploy will execute each of the steps in turn. When all of the steps are successfully executed, the task itself is successfully executed. If one of the steps fails, the task itself is marked as failed.

In Deploy with the custom microservices deployment technologies, concurrent deployments are causing issues because of middleware limitations that allow only for a single deployment to be performed to the target at a given time.

Deploy uses a scheduling mechanism to run various system administration jobs on top of the repository, such as garbage collection, purge policies, and so on. You can also use this mechanism to run specific control tasks on configuration items (CIs) stored in the repository.

Using Deploy, you can schedule deployment tasks for execution at a specified moment in time. For more information, see scheduling tasks.

In Deploy you can schedule or reschedule a task for execution at a specified date in time. You can schedule or reschedule tasks that are in a PENDING or SCHEDULED state.