https://step.dev/knowledgebase/30/devops/automation-package-cli/ Recent content in Automation Package CLI on Step Documentation Hugo -- gohugo.io en Wed, 21 Aug 2024 00:00:00 +0000 https://step.dev/knowledgebase/30/devops/automation-package-cli/ap-maven-plugin/ Wed, 22 May 2019 14:08:01 +0100 https://step.dev/knowledgebase/30/devops/automation-package-cli/ap-maven-plugin/ 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. https://step.dev/knowledgebase/30/devops/automation-package-cli/step-cli/ Wed, 22 May 2024 14:08:01 +0100 https://step.dev/knowledgebase/30/devops/automation-package-cli/step-cli/ 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 Step CLI supports following operations for Automation Packages: