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 »

Overview Automation Package Libraries (AP Libraries) extend Step’s Automation Package model by enabling common code, libraries and entities to be packaged, deployed, and referenced independently from individual Automation Packages (APs). They offer a structured mechanism for sharing logic at scale and optimizing performance across large automation ecosystems. AP Libraries are reusable, versioned code artifacts that can provide: Shared logic across multiple Automation Packages Common utilities and helper classes Shared libraries Shared AP entities (Keywords, Plans) Important: Read More »

Automation Packages Multi-version support Read More »

Automation Packages Definition in Java code Read More »

Link collection of devops related tutorials Read More »

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