Automation Assembler supports integration with Bitbucket for use as a Git-based repository for ABX action scripts and VMware cloud templates.
In Automation Assembler, you can work with two types of repository items using Bitbucket integration: VMware cloud templates or ABX action scripts. You must synch projects that you want to work with before using a Bitbucket integration. ABX actions support write back to the Bitbucket repository, but you cannot write back cloud templates from the integration. If you want to create new versions of cloud template files, you must do so manually.
Prerequisites
- Set up an on premises Bitbucket Server deployment with one or more ABX or cloud template-based projects that you want to use with your deployments. Bitbucket Cloud is currently not supported.
- Create or designate Automation Assembler project to associate your Bitbucket integration.
- Cloud template files to be synched to a Bitbucket integration must be named blueprint.yaml.
Procedure
Results
Bitbucket integration is configured with the specified repository configuration, and you can view and work with ABX actions and cloud templates contained in configured repositories. When you add a project to a Bitbucket integration, a synch operation runs to pull the latest versions of ABX action scripts and cloud template files from the designated repository. The History tab on the Bitbucket integration page shows records of all synch operations for the integration. By default, files are automatically synched every 15 minutes,but you can manually synch a file by selecting it and clicking SYNCH at any time.
What to do next
You can work with ABX actions on the Automation Assembler Extensibility page, and you can work with cloud templates on the Design page. If you save a changed version of an ABX action on the Extensibility area of Automation Assembler, the new version of the script is created and written back to the repository.