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 »

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 Packages Definition format Read More »

The Step Maven plugin serves as Command Line Interface (CLI) for all operations related to Automation Packages. It provides an integration with the Step server and an easy way to integrate Step with a CI/CD pipeline. Read More »

The Step CLI is a Command Line Interface for all operations related to Automation Packages available for Windows and Unix System. It provides an integration with the Step server and an easy way to integrate Step with a CI/CD pipeline. Read More »

Automation Packages Definition in Java code Read More »

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 »

Automation Packages come with a full-featured CLI that allows to build, execute and deploy Automation Packages Read More »

DevOps Read More »