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

Test Rsults aggregator gives Job NOT_FOUND with error Cannot invoke

XMLWordPrintable

      Hi Team,

      I have installed the latest test results aggregator plugin which is 2.1. I have successfully added the Jenkins base URL and username , password. I have added admin credentials and tested the connection. Test shows total jobs found with the count.

      New job created with the name of AggregateTestResultsForDev and I have added Aggregate Test Results in the Post-build Actions. I have provided two jobs names for the testing. The two jobs are in the same view of AggregateTestResultsForDev. There are no folders, so directly provided the job name here. 

      After I ran the job, I am getting an error in the Build console. I am sure I have configured in a right way , because in the console it shows Total Jenkins jobs found 56 and Aggregator has resolved successfully 2/2.

      I am writing the console lines here,

      Started by user Admin

      Running as System

      Building on VM1

      Starting Aggregate Test Results Action

      Total Jenkins jobs found 56 and Aggregator has resolved successfully 2/2

      Collect data

      Job 'job1' found NOT_FOUND with error : Cannot invoke "String.endsWith(String)" because the return value of "java.lang.Exception.getMessage()" is null (0)s

      Job 'job2' found NOT_FOUND with error : Cannot invoke "String.endsWith(String)" because the return value of "java.lang.Exception.getMessage()" is null (0)s

      Collect data ..Finished

      Analyze ..Finished

      Generate XML Report.. Finished XML Report

      Generate HTML Report.. Finished HTML Report

      Generate HTML Report for all Ignored Jobs... Finished HTML Report

      Sent message successfully to:

      xx@cm.com

      Finshed: Success

       

      The above are the console lines.

      job1 and job2 are having builds and builds are success. Published the TestNG results as well.

      I could see TestNG results in each of the Jobs.

      We have the load runner in the backend, so we converted the Jenkins base URL to https://jenkinsurl. Is it impacting and gives the issue?

       

      If yes, how come in the console it says Aggregator has resolved successfully 2/2. 

      Configured user is the Admin user, so it has the full access to the jobs as well.

       

      Please check on this priority and give me a solution? 

      The Jenkins version is 2.401.3

      Let me know if you need any other details. I could not share URL or screenshots since all those are in company device.

       Thanks!

            socrates Socrates Sidereas
            tamilarasan Tamilarasan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: