Creating and Using Tasks

A Task in CloudMunch is a logical grouping of Steps to perform an action. Currently, only a Plugin is used for a Step. Plugins are specialized commands (created by CloudMunch and is also available for users to build their own using the SDK) that are like Launching a Docker Container or Checking a URL. 

Tasks are created using CloudMunch Plugins and can be reused in other Applications as well. Every Task has a specific category, or the purpose of the Task, in its definition. The categories are: 

  • Build - creates an Application build, called a Run and a new build has incremental Run #. 
  • Provision - creates an Environment for an Application Environment
  • Build Action  - an action performed on an existing build (or Run) 
  • Environment Action - a Task that is performed on an existing Environment
  • Other - any generic Task

Creating a Task

To create a Task in an Application, select the Tasks tab. This page will list all the Tasks that are available in the application, created by a Template that you used.

In this page select Add Task. Let's walk through the process of creating a Task that will perform an action on a running Environment - meaning a category of Environment Action. Select the Continue button to create to the Task. 

Now the task appears in the Tasks list. Right now the Task is created, but there are no Steps in the Task.

Tasks are displayed in the list with its name, description and icon with a color that signifies the category of the Task. A Task has three configuration data

  1. Steps: Individual actions that are strung together to create a Task
  2. Variables: Task level variables which can be used to either pass information between steps or inputs that can be provided at execution time
  3. Schedule: Cron based schedule for periodically executing this Task

At a glance, you can see the number of Steps, Variables and Schedules associated with the Task. Selecting on either the edit button or selecting any of the configuration links will put the Task in edit mode, allowing you to make changes. Next, we'll now add Steps.  

Select Steps (0) and Add Step

Executing a Task

From the Application overview, Tasks can be executed. Each category of Task is executed differently.

  • Trigger Build button in a Pipeline
  • Environment Actions 

Tasks that are created as Environment Actions will show up at an Environment when you pull down on the carat. The Task can be executed by selecting from this list. In the example below the Environment T_am_21830_Main-2 has two Tasks - Start and Stop.


  • Insights 

The Templates provide Tasks that collect various Insights about your software delivery. These tasks can be executed by navigating to the Task from the Tasks navigation on the Application and the Trigger button starts the Task.