Turn a Git push into a release you can trace.
Define build, test and deployment steps in microtica.yaml. Trigger the pipeline from a selected Git branch or tag, and follow each run through its status and logs.
- Demo project
- catalog-service
- Pipeline run
Sample pipeline run for catalog-service at commit 7c9e2b1. The build stage passed checkout, install, test and docker-build. The deploy-staging step is running and its log shows the Kubernetes rollout finishing.
CI/CD pipelines
What you get
A pipeline run tied to a source revision, with build and deployment progress you can inspect.
What you bring
- Application code in a connected Git repository, a microtica.yaml pipeline definition, and the target environment.
- GitHub, GitLab and Bitbucket have documented connection paths.
How it works
Know what happens before you start.
- 01
Define the pipeline
Describe your build, test and deploy steps in microtica.yaml. Group steps into stages when you need parallel execution within a stage.
- 02
Choose the trigger
Configure the repository and branch or tag. Enable deployment on matching pushes when you want automated execution.
- 03
Follow the run
Open the pipeline run to inspect progress, logs and deployment status. Investigate a failed step before choosing the next action.
Configuration in your repository
The pipeline definition lives with your code. Importing an existing application may add Microtica’s required pipeline files to that repository.
Notifications for deployment work
Connect Slack or Microsoft Teams for pipeline notifications. Keep those notifications distinct from metric alarms and on-call paging.
“Microtica provided us with excellent guidance and support throughout the migration process, and the cloud platform has been a breeze to use since then. We are very thankful for the cost savings measures the platform provides.”
Access and control
A configured push trigger can deploy automatically
Review branch filters, pipeline variables and the target environment before enabling automation. A Mica approval card does not add a manual approval to an independently configured Git-triggered pipeline.
Try it on one service.
Start free with a development project, or bring your setup to a demo.