ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Devtest Jenkins Plugin Support with Slave machine configuration not working properly

book

Article ID: 185424

calendar_today

Updated On:

Products

CLOUDTEST CA Application Test CA Cloud Test Mobile MOBILECLOUD Service Virtualization

Issue/Introduction

I have been integrating Jenkins Plugin for our client and facing issue.
    When I tested the plugin in an environment where "Master" have connectivity with my Registry Host, it is working fine.
But when I moved to the Production environment where Master doesn't have connectivity with Registry but one of the slave does have, it is not working/connecting. It seems that the plugin is still running on master machine and trying to execute Invoke API from there even when I configured the pipeline stage to run on a specific slave machine.
   Could you please help me get a fix for the plugin so that it can run on a slave machine instead of executing always on master.

 

Environment

Release : 10.5

Component : CA Service Virtualization

Resolution

      As per Devtest Jenkins plugin is designed, master server should have connectivity/communication with registry server. When you choose run on slave server, plugin will take the details from slave machine and run invoke API call from master server.
Powered by Wolken Software