Install .NET agent and execute .NET keyword Read More »

Invoke step from ALM. Read More »

Integrate step with Azure DevOps. Read More »

Overview of Async packages 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 »

Be notified as soon as an execution fails or completes. 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 »

Description The artifact repository connector for Executable Bundles provides a seamless integration with classical artifact repositories like Nexus. It enables the retrieval and execution of Executable Bundles 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 Executable Bundles along with the source code of the application to be tested Build of the Executable Bundles as part of the CI pipeline and deployment of the Executable Bundles to an artifact repository Trigger of the central execution of the Executable Bundles 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 »