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 »

Install .NET agent and execute .NET keyword 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 »

Integrate Step with Jira Xray. 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 »

Invoke Step from ALM. Read More »

Integrate Step with Azure DevOps. 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 »

Overview of Async packages Read More »

Define custom rules for alerting, notifications, and integrations with external systems Read More »

The Step client exposes means to connect to the controller programmatically, access and use Step services in a headless way via the class STEPClient. Read More »

Define custom rules for alerting, notifications, and integrations with external systems Read More »

View and analyse created incidents based on your alerting rules Read More »

Be notified when various events occur. Read More »

Be notified as soon as an execution fails or completes. Read More »

xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx. Read More »

The Step client exposes means to connect to the controller programmatically, access and use Step services in a headless way via the class STEPClient. Read More »

The Step Maven plugins provide an integration with a running Step server during your build process and an easy way to integrate Step with a CI/CD pipeline. Read More »

Description The artifact repository connector for Automation Packages provides a seamless integration with classical artifact repositories like Nexus. It enables the retrieval and execution of Automation Packages that are deployed on artifact repositories. The main use-case of this plugin is the integration with CI/CD pipelines. A common workflow relying on this feature looks as follow: Development of Step Automation Packages along with the source code of the application to be tested Build of the Automation Packages as part of the CI pipeline and deployment of the Automation Packages to an artifact repository Trigger of the central execution of the Automation Packages on a Step Controller by the CI pipeline via artifact repository plugin Usage The artifact repository connector works like any other repository plugin like ALM, Jira, etc. Read More »

If you’ve purchased the Async package or are running the Premium Enterprise version of Step, you’ll be able to monitor in real time what’s happening in the EventBroker by navigating to the EventBrokerMonitor view: The Stats tab provides global statistics on the broker, such as the current amount of messages present in it and the high mark (or water mark), oldest & youngest events, etc. The next two tabs provide users with the ability to browse and search for events, and organizes the query results either by Id or Group. Read More »

How to make Step write data to external databases Read More »

Restore previous versions of entities Read More »

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

DevOps Read More »