Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-60819

Jenkin Integration with Silk Performer 20.5 - LoadtestController: 3231 - No agents available

    Details

    • Similar Issues:

      Description

      Hi Team, 

      We were working on Integration between the Jenkins and Silk Performer 17.5 to enable DevOps process in the Performance testing Phase and now we upgraded our Silk Performer version to 20.5.

       

      So when we do the integration with the latest version, we are facing the below error message in the Build Console log and which is something we haven't faced in the integration with Silk Performer 17.5. Could you please have a look at the error details and advise the probable cause to resolve the error? 

       

      Results path: C:\Temp\workspace\Jenkins_Silk_CS\result
      Silk Performer installation directory: C:\Program Files (x86)\Silk\Silk Performer 20.5
      Using default workload: DemoAgent messages:
      com.segue.em.SGRuntimeException: LoadtestController: 3231 - No agents available.
      {{ at com.segue.em.SGExecutionManager.sgemStart(Native Method)}}
      {{ at com.segue.em.Ltc.start(Ltc.java:238)}}
      {{ at com.borland.jenkins.SilkPerformerJenkins.util.SilkPerformerTestManager.startTheLoadTest(SilkPerformerTestManager.java:58)}}
      {{ at com.borland.jenkins.SilkPerformerJenkins.ExecuteOnNode.call(ExecuteOnNode.java:89)}}
      {{ at com.borland.jenkins.SilkPerformerJenkins.ExecuteOnNode.call(ExecuteOnNode.java:34)}}
      {{ at hudson.remoting.UserRequest.perform(UserRequest.java:212)}}
      {{ at hudson.remoting.UserRequest.perform(UserRequest.java:54)}}
      {{ at hudson.remoting.Request$2.run(Request.java:369)}}
      {{ at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)}}
      {{ at java.util.concurrent.FutureTask.run(Unknown Source)}}
      {{ at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)}}
      {{ at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)}}
      {{ at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)}}
      {{ at java.lang.Thread.run(Unknown Source)}}
      Build step 'Execute Silk Performer Tests' marked build as failure
      Archiving artifacts
      Recording plot data
      Finished: FAILURE

        Attachments

          Activity

          Hide
          mihai_virag Mihai Virag added a comment -

          Hi,

          Can you check if in the project an agent is set. This error indicates that there are no agents set.

          Thanks,
          Mihai

          Show
          mihai_virag Mihai Virag added a comment - Hi, Can you check if in the project an agent is set. This error indicates that there are no agents set. Thanks, Mihai
          Hide
          chandru_s Chandrakumar Sekar added a comment -

          Hi Mihai,

           

          Yes the error indicates the project agents are not set, but i double checked the project file which being executed by Jenkins and Agents are mapped to the project. 

           

          Also, please be informed that this same project file was used in the silk performer 17.5 and it was running with no issues. And we have upgraded to silk performer 20.5 today and when using same project file (was running with no issues in previous version), showing an error now in 20.5 version. PFA, agent assignment on the Project. 

          Show
          chandru_s Chandrakumar Sekar added a comment - Hi Mihai,   Yes the error indicates the project agents are not set, but i double checked the project file which being executed by Jenkins and Agents are mapped to the project.    Also, please be informed that this same project file was used in the silk performer 17.5 and it was running with no issues. And we have upgraded to silk performer 20.5 today and when using same project file (was running with no issues in previous version), showing an error now in 20.5 version. PFA, agent assignment on the Project. 
          Hide
          chandru_s Chandrakumar Sekar added a comment -

          Hi Mihai, 

           

          I just saved the project file of 17.5 version in Silk Workbench (20.5) and uploaded to Git repository and re-run the build which completes successful. No other changes have been done. 

           

          So we can close this Jira now. 

          Show
          chandru_s Chandrakumar Sekar added a comment - Hi Mihai,    I just saved the project file of 17.5 version in Silk Workbench (20.5) and uploaded to Git repository and re-run the build which completes successful. No other changes have been done.    So we can close this Jira now. 

            People

            • Assignee:
              silk Silk Performer
              Reporter:
              chandru_s Chandrakumar Sekar
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: