<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>CI/CD on Step Documentation</title>
    <link>https://step.dev/knowledgebase/31/categories/ci/cd/</link>
    <description>Recent content in CI/CD on Step Documentation</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language><atom:link href="https://step.dev/knowledgebase/31/categories/ci/cd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Automation as Code</title>
      <link>https://step.dev/knowledgebase/31/devops/automation-as-code/</link>
      <pubDate>Wed, 21 Aug 2024 00:00:00 +0000</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/devops/automation-as-code/</guid>
      <description>Step&amp;rsquo;s unique Software automation as Code approach (short Automation as code) enables developers to define software automation workflows for the whole DevOps lifecycle as code alongside the product code.
This concept is the key enabler for shift-left in not just testing but for all disciplines relating to software automation. This ranges from large scale E2E acceptance tests to load and performance tests, synthetic monitoring, RPA, and much more.
This pages presents the use-cases enabled by the Automation as Code approach.</description>
    </item>
    
    <item>
      <title>Maven plugin</title>
      <link>https://step.dev/knowledgebase/31/devops/automation-package-cli/ap-maven-plugin/</link>
      <pubDate>Wed, 22 May 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/devops/automation-package-cli/ap-maven-plugin/</guid>
      <description>The Step Maven plugin serves as Command Line Interface (CLI) for all operations related to Automation Packages in Java. It provides an integration with the Step server and an easy way to integrate Step with a CI/CD pipeline. For non-Java projects, it is recommended to use the Step CLI.
The Step Maven plugin supports following operations:
Upload Automation Packages to Step and execute them in isolation Deploy the content of Automation Packages to Step and enable the contained schedules Deploy an Automation Packages library to Step You can choose to integrate the plugin goals during the package phase or any later phase as you see fit in the Maven Lifecycle.</description>
    </item>
    
    <item>
      <title>Azure DevOps</title>
      <link>https://step.dev/knowledgebase/31/plugins/azuredevops/</link>
      <pubDate>Wed, 10 Apr 2019 14:24:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/azuredevops/</guid>
      <description>The Azure DevOps integration plugin provides an out-of-the-box integration of Step with the Azure Test Plans module of Azure DevOps.
With the Azure DevOps plugin you create, design and manage your automated test cases in Azure Test Plans, run them on Step&amp;rsquo;s Execution Engine, and evaluate the run results and test reports at the same place in Azure Test Plans. This plugins is therefore the perfect solution for users requiring the best of the 2 worlds: the unique power of the Step Execution Engine with the test management and reporting features of Azure Test Plans.</description>
    </item>
    
    <item>
      <title>Step CLI</title>
      <link>https://step.dev/knowledgebase/31/devops/automation-package-cli/step-cli/</link>
      <pubDate>Wed, 22 May 2024 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/devops/automation-package-cli/step-cli/</guid>
      <description>The Step CLI (Command Line Interface) is used for all operations with Step. It provides an integration with the Step server and an easy way to integrate Step with a CI/CD pipeline. Currently it is limited to the operations related to Automation Packages but might be extended in the future. For Java specific projects, the CLI is also available as a Maven plugin.
The CLI also includes Step Studio for creating and editing Automation Packages visually on your machine.</description>
    </item>
    
    <item>
      <title>Getting started with Automation Packages</title>
      <link>https://step.dev/knowledgebase/31/devops/devops-getting-started/</link>
      <pubDate>Tue, 06 Feb 2024 00:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/devops/devops-getting-started/</guid>
      <description>The easiest way to get started with Automation Packages is to use one of our tutorial projects.
Load and performance tests For automated and continuous performances tests, the tutorials include a complete project definition with a few simple keywords and plans defining a short load test scenario. It should be straightforward to execute these projects and start from there by modifying them according to your needs.
Browser-based load testing with Playwright Protocol-based load testing with okhttp Continuous load testing with Grafana K6 Synthetic Monitoring Similarly to the load and performance test scenario, the tutorial for synthetic monitoring contains simple keywords, execution plan and schedule to set up the synthetic monitoring.</description>
    </item>
    
    <item>
      <title>Maven plugins</title>
      <link>https://step.dev/knowledgebase/31/plugins/maven-plugins/</link>
      <pubDate>Wed, 29 Mar 2023 08:00:00 +0000</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/plugins/maven-plugins/</guid>
      <description>The documentation of the Maven plugins was moved to the DevOps section and is available here.</description>
    </item>
    
    <item>
      <title>Automation Package CLI</title>
      <link>https://step.dev/knowledgebase/31/devops/automation-package-cli/</link>
      <pubDate>Wed, 21 Aug 2024 00:00:00 +0000</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/devops/automation-package-cli/</guid>
      <description>Automation Packages come with a full-featured CLI that allows to build, execute and deploy Automation Packages. The CLI is available as native application for Windows and Linux, and as Maven plugin which is recommended for integration with Java projects.</description>
    </item>
    
    <item>
      <title>DevOps / Automation as code tutorials</title>
      <link>https://step.dev/knowledgebase/31/whatsnew/news/new-devops-tutorials/</link>
      <pubDate>Tue, 30 Jan 2024 06:00:00 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/whatsnew/news/new-devops-tutorials/</guid>
      <description>
Step 24 introduces a completely redesigned version of the Automation Package. 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&amp;rsquo;s own usage and maintenance.
We&amp;rsquo;ve just published a set of tutorials to illustrates this, check them out!
DevOps getting started</description>
    </item>
    
    <item>
      <title>DevOps</title>
      <link>https://step.dev/knowledgebase/31/devops/</link>
      <pubDate>Thu, 28 Feb 2019 14:08:01 +0100</pubDate>
      
      <guid>https://step.dev/knowledgebase/31/devops/</guid>
      <description>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.
To create and edit Automation Packages visually on your own machine, start with Step Studio.</description>
    </item>
    
  </channel>
</rss>
