MY ACCOUNT / MY ORGANIZATON
Troubleshooting
BEST PRACTICES

What are Workflows and Why to Use Workflows?

A workflow is a ladder of steps taken to build your applications.

Each step has a different purpose and the workflow can be customized by modifying step parameters and inputs, running custom scripts or re-ordering steps.

Workflows allow you to have complete control on your build process and enhance it with third-party services and features.

Please note that modifying workflow steps may cause your builds to fail, so utmost care is recommended when editing workflows.

Worfklow Steps

Appcircle will build your application with the steps defined in the workflow of the branch. Steps will be executed in order from the top to the bottom.

You can customize each step for specific configurations with your application structure. Step parameters can be modified, outputs of each step can be used in another step and step versions can be selected accordingly.

Workflow Marketplace

Appcircle's powerful Workflow Editor has a built-in Workflow Marketplace that allows you to select and insert unlimited amount of steps to your workflow.

You can find the full list of available workflow steps in our central component repository at: https://github.com/appcircleio/appcircle-workflow-components‚Äč

You can add platform-specific workflow steps, custom scripts and other steps into your workflow and re-order them as you like. You can also remove the steps you don't need.

To access to the Workflow Marketplace, go to the Workflow Editor and click on the Edit button:

You will see the Workflow Marketplace on the right and your Workflow steps on the left. You can now drag and drop steps into your workflow. Any unwanted workflow steps can be removed by clicking on the delete button on the right side of each step.

You can also reorder steps so that they will be executed in the order you specify.

Workflow Settings

Each workflow step has its own set of configuration options, which can be set by clicking on the step in the workflow screen.

The first three items are common for all steps and they are set individually for each step:

  • Step Execution Active: To enable/disable the step execution without removing it from the workflow

  • Continue with the next step even if this step fails: If a step is optional or if its result should not cause a build failure, you can select this option to continue the workflow in case of the failure of this specific step. In the default workflows, this option is turned on for certain steps.

  • Workflow Step Version: You can select a specific version of a step with which to execute your build. If you select a version with an asterisk (*), you will receive the minor updates to the workflow step automatically. The major versions may include added or removed input fields and manual version selection is required for major version updates.

The items in the "Inputs" section is specific to that step. The reserved environment variables are assigned to these fields by default and the values of these variables are set in the build configuration.