Tosca CI/CD integration
The Tosca CI/CD integration allows you to incorporate Tricentis Tosca into your own CI/CD pipeline. You can also combine it with other environments, for example environments where you don't have Tosca installed. The integration minimizes the effort you have to invest into continuous integration and delivery; you can trigger your automated Tosca tests without user input.
Types of integration
Depending on your systems infrastructure, you can implement the Tosca CI/CD integration in one of the following ways:
Trigger tests via Tosca Execution Client. This option is only available if you use Tosca Distributed Execution with AOS. Tosca Execution Clients are fully script-based, so you can customize your Tosca CI/CD integration to meet your needs.
Integrate directly with the Tosca Server Execution API. This option is only available if you use Tosca Distributed Execution with AOS.
Legacy options: execution via Tosca Distributed Execution without AOS, execution via Remote Service, execution on the build server.
We recommend that you switch to Tosca Distributed Execution with AOS and take advantage of the first two options. They're easier to set up, give you more flexibility, and allow you to override configurations at run-time.
What's more, Tricentis is planning to discontinue legacy features. For detailed information on the deprecation plan and time line, see this Tricentis Knowledge Base article.
Choose how to set up the Tosca CI/CD integration:
Integrate directly with the Tosca Server Execution API.
Use one of the legacy integrations.