DevOps

This section is dedicated to use of Step in the DevOps context. It targets developers who want to define their software automation artifacts for the whole DevOps lifecycle as code alongside their product code.

Automation as Code

Step’s unique Software automation as Code (short Automation as code) approach enables developers to define software automation workflows for the whole DevOps lifecycle as code alongside the actual application’s code. Read more

Automation Packages

Based on the Automation as Code paradigm, the new Automation Package extends Step with DevOps-native functionality, allowing to maintain application and automation code in tandem, and bringing powerful automation capabilities to DevOps pipelines, as well as simplifying Step’s own usage and maintenance. Read more

Automation Package descriptor

Automation Packages Definition format Read more

Automation Package in Java

Automation Packages Definition in Java code Read more

Step Automation Package UI

While Automation Packages are mostly meant to be operated via the CLI or the maven plugin to integrate Step with a CI/CD pipeline, the Step UI still allows to directly deploy, delete and execute Automation Packages directly. Read more

Getting started with Automation Packages

Link collection of devops related tutorials Read more

Automation Package CLI

Automation Packages come with a full-featured CLI that allows to build, execute and deploy Automation Packages Read more
Categories: DEVELOPER GUIDE CI CD DEV OPS ENTERPRISE