Automation

Automation runs your routine operations as pipelines: deployments, service restarts, version rollbacks and repetitive or scheduled tasks. Curade drives an automation server, which runs each pipeline stage by stage. Tenant Admins open it; Tenant Users do not.

Templates

Create Pipeline starts a pipeline from a template, or from scratch:

Building a pipeline

A pipeline has a title and five parts: its configuration, such as a schedule, its environment variables, the libraries it imports, its functions and the stages of its pipeline script, which can run side by side. Save Pipeline saves it, and Save & Run saves it and runs it straight away (Create a pipeline).

The pipeline list

Pipeline lists every pipeline with its status, its type, its last successful build, its last build and its build time. A search, filters by status and type, and sorting by last build or build time narrow the list. On each pipeline, Run starts it, View shows its recent builds stage by stage, Edit changes it, Duplicate copies it under a new name and Delete removes it.

Builds and approvals

A pipeline's own page lists its builds, and View Log opens a build's log. A stage that waits for approval offers Proceed to carry on or Abort to stop the build. The build status panel on the pipeline list shows what is queued, what is running and what is waiting for approval, with the same two choices.

Credentials

Pipelines use passwords, secrets and keys without showing them. Manage Automation Credentials holds them (Manage automation credentials).