ASM Auto Deploy - Visual Studio Marketplace

#Apica ASM Auto deploy (RPA)

Overview

This task enables you to deploy assets to an Apica ASM (Apica Synthetic Monitoring ) instance. The assets which can be deployed with automation using the ASM API are.

Zebra Tester Scenarios
Browser Scenarios
Checks

The ideas is that you have source assets in a git repository. Default repository is the source repository associated with Azure DevOps Pipeline. You can use another repository by specify it in the run-time parameters or use a directory on the agent as the source directory. The task can compile your Zebra Tester Java plugins, if you provide source code to them in the source repository. That require a Zebra Tester installation on the agent used in the pipeline.

The task needs an deployment descriptor which contains meta data for manage the automation of the the deployment. More information about the deployment descriptor will come.

Contact Information

Please visit our home page if you want more information about the company Apica. Also, if you would like to share your feedback, e.g. about functionality that should be added to the task extension then please send an email to support support@apica.io.

Prerequisites for the task

Apica Synthetic Monitoring Portal (ASM) account

This task requires you to fill in a number of properties related to Apica ASM, see the details below. You can only provide valid entries if you have an account on the Apica ASM Portal website.

Detailed documentation for the task

The asm-auto-deploy can also be executed as command line tool. You can find detailed information about how the deployment deployment descriptor works at https://www.npmjs.com/package/@apica-io/asm-auto-deploy

Additional documentation for AzureDevOps

The repository parameters should only be used if you not use the default repository connected to the Pipe Line.
Set system.debug to get detailed information during execution of the task.
You must include an additional command line task after the ASM Auto Deployer (RPA) task to commit changes in deployment descriptor to the repository.
We have tested with a GitHub repository.

cd  $(Build.Repository.LocalPath)

git diff --exit-code
if [ $? -eq 1 ]
then
  git add -A
  git commit -m "Run $(Build.BuildNumber)"
  git push origin HEAD:main
fi

This is the syntax for bash and for the branch main. You can use the variable Build.SourceBranchName to get branch name and do the script more generic.