Product / Deployments & automation
Deployments and automation
Chain pipelines into delivery flows, control who can deploy to each environment, and run scheduled or on-demand jobs. Every feature below has a video and links to the docs.
TL;DR
- Promotions connect pipelines: build, staging, production, manual or automatic.
- Deployment targets limit who can deploy where and keep history per environment.
- Tasks run pipelines on a schedule or on demand with parameters.
- Everything is configured in the same YAML as your CI.
Features at a glance
| Feature | What it does | Docs |
|---|---|---|
| Tasks | Scheduled and on-demand pipelines. | Tasks |
| Deployment Targets | Control who can deploy where, with history per environment. | Deployment targets |
| Promotions | Chain pipelines into multi-stage delivery flows. | Promotions |
Tasks
Run any pipeline on a cron schedule or start it by hand with parameters: nightly builds, database backups, dependency updates or one-off maintenance jobs.
Tasks feature page → · Tasks →
Deployment Targets
Define environments such as staging and production, restrict who can promote to each one and from which branches, attach environment secrets, and see the deployment history per target.
.semaphore/semaphore.yml
promotions:
- name: Deploy to production
pipeline_file: deploy-prod.yml
deployment_target: production
Deployment Targets feature page → · Deployment targets → · Deployment target YAML →
Promotions
Connect pipelines into a delivery flow: build, then deploy to staging, then production. Promotions can run on a click or automatically when a condition is met, such as tests passing on the main branch.
.semaphore/semaphore.yml
promotions:
- name: Deploy to staging
pipeline_file: deploy-staging.yml
auto_promote:
when: "result = 'passed' and branch = 'main'"
Promotions feature page → · Promotions → · Conditions DSL →
Also included
- Orchestration. Parallel blocks, dependencies and promotions model complex release flows in one place. Workflows docs.
- Oversight. Deployment history, audit events and role-based access show who deployed what and when. Audit events.
- Secrets per environment. Attach secrets to a deployment target so only that environment can read them.
- Monorepo deploys. Use
change_inin promotions to deploy only the services that changed. Monorepos.
FAQ
Yes. Add auto_promote with a condition, for example result = ‘passed’ and branch = ‘main’, and the next pipeline starts without a click.
Create a production deployment target and limit it to specific people, roles or branches. Everyone else sees the promotion but cannot start it.
Yes. Tasks run any pipeline on a cron schedule, or on demand with parameters you fill in when you start it.
In secrets. Attach them to a deployment target so only pipelines promoted to that environment can read them.
Next steps
Set up promotions → · Security & compliance → · Plans and pricing →
Blog · Deep dive
A step-by-step guide to continuous deployment on Kubernetes
Build, push and deploy to Kubernetes with Semaphore pipelines and promotions.