Skip to end of metadata
Go to start of metadata

Change Log

Version 2.10 (March 8, 2019)

  • Option to append variable set environment to session tag when publishing to DTP (issue CTP-4394)

Version 2.9 (February 1, 2019)

  • Optionally continue build steps after a test scenario job fails (issue CTP-4307)

Version 2.8 (January 27, 2019)

  • Allow publishing results from CTP test scenario job to Parasoft DTP as part of the Jenkins build step (issue CTP-4267)
    Requires Parasoft CTP 3.1.3 and Parasoft DTP 5.4.0 or higher.

Version 2.7 (December 28, 2018)

  • Allow users to parameterize the CTP job name to a Jenkins environment variable in the Parasoft Environment Manager plugin (issue CTP-3942)

Version 2.6 (September 25, 2018)

  • Improve API query performance for test execution jobs (issue CTP-4082)

Version 2.5 (Aug 3, 2017)

  • Fix build step drop down not able to display more than 100 test execution jobs (issue CTP-2841)

Introduction

The Parasoft Environment Manager plugin for Jenkins lets you rapidly configure various actions needed for automated, continuous testing across your software delivery pipeline. You can configure build steps for:

  • Provisioning environments into the specific states needed for automated testing
  • Replicating environments and associated assets to different Virtualize servers, including servers dynamically-provisioned from Docker or other container technologies
  • Executing Parasoft test scenario jobs (tests suites that execute vs. specific environment configurations)
  • Destroying "dirtied" test environments to ensure that subsequent tests always begin with a clean slate
  • Disconnecting a Virtualize server from Environment Manager to remove unnecessary connections

For documentation please visit the link Environment Manager Plugin for Jenkins