CI/CD Integration with A360

I've not this specifically with Automation Anywhere but have done this numerous times via some custom APIs. Now that we have web triggers in the product and supported in API Tasks and Task Bots, you could come up with a pretty compelling use case.

Are you just looking to deploy some GitHub Action workflows via Automation 360?

​@Oli.Morris After the code is checked in from the AA Control Room, the developer will create a pull request in Github. This pull request needs to go through an approval process, and once it is approved, the package should be deployed to the Production Control Room.

I recommend having a GitHub action that when a PR is merged into your main branch, it triggers an event listener in the Control Room. The listener would be connected to an API Task that then triggers the BLM APIs which promotes the automation to your production CR. The GitHub action would need to send a JSON payload to the API Task so that the files part of the BLM API request can be populated.

Yes, A360 does not have a direct built-in GitHub CI/CD integration, but it can be achieved by using GitHub for version control and GitHub Actions to trigger a pipeline that deploys bots to Automation Anywhere Control Room through its APIs, while securely storing credentials in GitHub Secrets.

Seeking an Automation 360 CLI that offers improved support for Bot Lifecycle Management (BLM) within CI/CD pipelines. The goal is to achieve closer integration that fits with current DevOps standards.