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

Test Results Aggregator plugin not fetching the test results of downstream jobs

      We have a main job running the gradle test command to run some test cases and archive the artifacts at the end. the main job calls multiple downstream jobs as a post-build success step, which in turn runs some gradle test cases and archives the artifacts just like the main job. The main job is supposed to wait for all the downstream jobs to finish and aggregate the test results of all the jobs and display the results in the common view.

      We are using the latest Jenkins version: 2.375. and have the latest version of the Test Results Aggregator plugin installed: 1.2.12. We are following the correct syntax to configure the main job as per this doc: https://github.com/sdrss/test-results-aggregator-plugin 

      Have configured the Plugin in the Jenkins global setting also correctly, But still the plugin is not fetching the test results of individual downstream jobs and we are not seeing any errors in the console logs. Attaching the console logs of the main job in the screenshots

      NOTE: The plugin was working fine just 4 weeks back and was able to aggregate all the downstream jobs test results in the main job under the Job Results Aggregator view but is not showing any results now.

      17:15:05  BUILD SUCCESSFUL in 1m 56s
      17:15:05  93 actionable tasks: 78 executed, 15 up-to-date
      17:15:05  + mkdir -p build/fingerprint
      17:15:05  + echo Care_QA/qa-01-critical-response--build-all-78
      17:15:05  + ls build
      17:15:05  fingerprint
      17:15:05  kotlin
      17:15:05  reports
      17:15:05  resources
      17:15:05  test-results
      17:15:05  version
      [Pipeline] }
      [Pipeline] // stage
      [Pipeline] stage
      [Pipeline] { (archive and aggregate)
      [Pipeline] archiveArtifacts
      17:15:05  Archiving artifacts
      17:15:05  Recording fingerprints
      [Pipeline] junit
      17:15:06  Recording test results
      17:15:06  [Checks API] No suitable checks publisher found.
      [Pipeline] script
      [Pipeline] {
      [Pipeline] echo
      17:15:06  Care_QA/qa-01-critical-response-AdminIntegrationsSuite
      [Pipeline] build (Building Care QA » qa-01-critical-response-AdminIntegrationsSuite)
      17:15:06  Scheduling project: Care QA » qa-01-critical-response-AdminIntegrationsSuite
      17:15:14  Starting building: Care QA » qa-01-critical-response-AdminIntegrationsSuite #37
      [Pipeline] copyArtifacts
      17:19:02  Copied 1 artifact from "Care QA » qa-01-critical-response-AdminIntegrationsSuite" build number 37
      [Pipeline] testResultsAggregator (hide)
      17:19:02  Starting Aggregate Test Results Action
      17:19:10  Not found results for Care_QA/qa-01-critical-response-AdminIntegrationsSuite
      17:19:10  Analyze ...Finished
      17:19:10  Generate XML Report...Finished XML Report
      17:19:10  Generate HTML Report...Finished HTML Report
      17:19:10  Generate HTML Report for all Ignored Jobs...Finished HTML Report
      17:19:10  Generate Email Report
      17:19:10  No mail will be Send since all Jobs are having status 'NOT_FOUND'.
      17:19:10  Generate Email Report for all Ignored Jobs
      17:19:10  No mail will be Send since all Jobs are having status 'NOT_FOUND'.
      17:19:10  Finished Aggregate Test Results Action
      [Pipeline] }
      [Pipeline] // script
      [Pipeline] }
      [Pipeline] // stage
      [Pipeline] }
      [Pipeline] // timestamps
      [Pipeline] }
      [Pipeline] // node
      [Pipeline] End of Pipeline
      Finished: SUCCESS
       

       

          [JENKINS-71586] Test Results Aggregator plugin not fetching the test results of downstream jobs

          zubair added a comment -

          socrates Could you please provide some updates? This is currently a priority issue for us.

          zubair added a comment - socrates Could you please provide some updates? This is currently a priority issue for us.

          Ekambir added a comment -

          Hello, I am seeing the same error with latest plugin version. My aggregator job is not able to find the child jobs. But when I rolled back to previous version, it is working fine and my aggregator job is able to find other jobs in the same folder. 
          Job 'childjob' found NOT_FOUND (19ss)

          Ekambir added a comment - Hello, I am seeing the same error with latest plugin version. My aggregator job is not able to find the child jobs. But when I rolled back to previous version, it is working fine and my aggregator job is able to find other jobs in the same folder.  Job 'childjob' found NOT_FOUND (19ss)

          Syamil added a comment - - edited

          Hi, i am seeing somewhat of the same issue. Recently upgraded jenkins alongside with the plugin.

          Job 'FoldernameXXX/JobnameXXX' found build number 0 with statusJob 'FoldernameXXX/JobnameXXX' found NOT_FOUNDwith error : null (3s)

          Test Result Aggregator Plugin v2.0

          Jenkins 2.414.3

          Note: i was unable to test the older version as i am not the jenkins admin. Just a user.

          Syamil added a comment - - edited Hi, i am seeing somewhat of the same issue. Recently upgraded jenkins alongside with the plugin. Job 'FoldernameXXX/JobnameXXX' found build number 0 with statusJob 'FoldernameXXX/JobnameXXX' found NOT_FOUNDwith error : null (3s) Test Result Aggregator Plugin v2.0 Jenkins 2.414.3 Note: i was unable to test the older version as i am not the jenkins admin. Just a user.

          zubair added a comment - - edited

          esidhu I was seeing the issue with the previous versions as well but the error was a little different. Since the previous version is working for you, I just needed to ask, Are you using the http or https url for the Jenkins? With the earlier version of the plugin installed, I am getting the following error:

           Starting Aggregate Test Results Action
          14:31:06  Collecting Data from Jenkins Job with name 'downstreamtest1' ...Finished with no data for last build url https://care-jenkins.########.com/job/downstreamtest1/lastBuild/api/json?depth=1 has no data

          zubair added a comment - - edited esidhu I was seeing the issue with the previous versions as well but the error was a little different. Since the previous version is working for you, I just needed to ask, Are you using the http or https url for the Jenkins? With the earlier version of the plugin installed, I am getting the following error: Starting Aggregate Test Results Action 14:31:06 Collecting Data from Jenkins Job with name 'downstreamtest1' ...Finished with no data for last build url https://care-jenkins.########.com/job/downstreamtest1/lastBuild/api/json?depth=1 has no data

          The latest release 2.1 is fixing a bug for jobs inside folders, so this version should fix the issues mentioned by syamil and esidhu   

           

          Socrates Sidereas added a comment - The latest release 2.1 is fixing a bug for jobs inside folders, so this version should fix the issues mentioned by syamil and esidhu     

          zubair added a comment -

          socrates We are not able to upgrade to version 2.1 as it needs Jenkins version above 2.375 which we are currently using. It's not possible for us to upgrade to the above Jenkins as it will break the whole Jenkins. Please suggest.

          zubair added a comment - socrates We are not able to upgrade to version 2.1 as it needs Jenkins version above 2.375 which we are currently using. It's not possible for us to upgrade to the above Jenkins as it will break the whole Jenkins. Please suggest.

          The next latest release is fixing another one issue for jenkins under https , its tested with several jenkins under https , if you can also check it I would appreciate , thanks in advance 

          Socrates Sidereas added a comment - The next latest release is fixing another one issue for jenkins under https , its tested with several jenkins under https , if you can also check it I would appreciate , thanks in advance 

          zubair added a comment - - edited

          socrates 
          I hope you are doing great! I had one ticket regarding the test-results-aggregator plugin opened a long time ago. We have recently upgraded our Jenkins to 2.440 version and installed the latest versions of plugin 2.2 and 2.1, but we are seeing a connection refused error while the aggregator plugin runs.
           
          Below is the log from my test job. 

          [Pipeline] script
          [Pipeline] {
          [Pipeline] build (Building criticaltestchild)
          13:28:24  Scheduling project: criticaltestchild
          13:28:30  Starting building: criticaltestchild #23
          13:28:35  Build criticaltestchild #23 completed: SUCCESS
          [Pipeline] copyArtifacts
          13:28:35  Copied 1 artifact from "criticaltestchild" build number 23
          [Pipeline] }
          [Pipeline] // script
          [Pipeline] testResultsAggregator
          13:28:35  Starting Aggregate Test Results Action
          13:28:37  Total Jenkins jobs found 14 and Aggregator has resolved successfully 1/1
          13:28:37  Collect data
          13:28:38  No last build details for job criticaltestchild Connect to care-jenkins.qa.######.com:443 [care-jenkins.qa.######.com/10.244.61.175] failed: Connection refused (Connection refused)
          13:28:38  No last build details for job criticaltestchild Connect to care-jenkins.qa.######.com:443 [care-jenkins.qa.######.com/10.244.61.175] failed: Connection refused (Connection refused)
          13:28:38  No last build details for job criticaltestchild Connect to care-jenkins.qa.######.com:443 [care-jenkins.qa.######.com/10.244.61.175] failed: Connection refused (Connection refused)
          13:28:38  Job 'criticaltestchild' found NOT_FOUND with error : null (1s)
          13:28:38  Collect data ...Finished
          13:28:38  Analyze ...Finished
          13:28:38  Generate XML Report...Finished XML Report
          13:28:38  Generate HTML Report...Finished HTML Report
          13:28:38  Generate HTML Report for all Ignored Jobs...Finished HTML Report
          13:28:38  Generate Email Report
          13:28:38  No mail will be Send since the Recipients List is empty.
          13:28:38  Generate Email Report for all Ignored Jobs
          13:28:38  No mail will be Send since the Recipients List is empty.
          13:28:38  Finished Aggregate Test Results Action
          [Pipeline] }
          [Pipeline] // script
          [Pipeline] }
          [Pipeline] // stage
          [Pipeline] stage
          [Pipeline] { (Declarative: Post Actions)
          [Pipeline] archiveArtifacts
          13:28:38  Archiving artifacts

          Could you please help us in resolving the error. This is certainly the different error than the ones we have been seeing earlier. Have also configured the plugin correctly in the configure settings with the URL: http://jenkinsurl:8080 the connection is happening fine there. This is critical for us.

          zubair added a comment - - edited socrates   I hope you are doing great! I had one ticket regarding the test-results-aggregator plugin opened a long time ago. We have recently upgraded our Jenkins to 2.440 version and installed the latest versions of plugin 2.2 and 2.1, but we are seeing a connection refused error while the aggregator plugin runs.   Below is the log from my test job.  [Pipeline] script [Pipeline] { [Pipeline] build (Building criticaltestchild) 13:28:24 Scheduling project: criticaltestchild 13:28:30 Starting building: criticaltestchild #23 13:28:35 Build criticaltestchild #23 completed: SUCCESS [Pipeline] copyArtifacts 13:28:35 Copied 1 artifact from "criticaltestchild" build number 23 [Pipeline] } [Pipeline] // script [Pipeline] testResultsAggregator 13:28:35 Starting Aggregate Test Results Action 13:28:37 Total Jenkins jobs found 14 and Aggregator has resolved successfully 1/1 13:28:37 Collect data 13:28:38 No last build details for job criticaltestchild Connect to care-jenkins.qa.######.com:443 [care-jenkins.qa.######.com/10.244.61.175] failed: Connection refused (Connection refused) 13:28:38 No last build details for job criticaltestchild Connect to care-jenkins.qa.######.com:443 [care-jenkins.qa.######.com/10.244.61.175] failed: Connection refused (Connection refused) 13:28:38 No last build details for job criticaltestchild Connect to care-jenkins.qa.######.com:443 [care-jenkins.qa.######.com/10.244.61.175] failed: Connection refused (Connection refused) 13:28:38 Job 'criticaltestchild' found NOT_FOUND with error : null (1s) 13:28:38 Collect data ...Finished 13:28:38 Analyze ...Finished 13:28:38 Generate XML Report...Finished XML Report 13:28:38 Generate HTML Report...Finished HTML Report 13:28:38 Generate HTML Report for all Ignored Jobs...Finished HTML Report 13:28:38 Generate Email Report 13:28:38 No mail will be Send since the Recipients List is empty. 13:28:38 Generate Email Report for all Ignored Jobs 13:28:38 No mail will be Send since the Recipients List is empty. 13:28:38 Finished Aggregate Test Results Action [Pipeline] } [Pipeline] // script [Pipeline] } [Pipeline] // stage [Pipeline] stage [Pipeline] { (Declarative: Post Actions) [Pipeline] archiveArtifacts 13:28:38 Archiving artifacts Could you please help us in resolving the error. This is certainly the different error than the ones we have been seeing earlier. Have also configured the plugin correctly in the configure settings with the URL: http://jenkinsurl:8080 the connection is happening fine there. This is critical for us.

          zubair added a comment -

          socrates I have been waiting for your response on this issue. It would greatly be appreciated if we could please get some help specifically on the error we are getting as mentioned above. I assume the plugin is not able to connect to the Jenkins master instance to fetch the test result of the downstream sample job, so the result is a connection error. But this is my guess. 

          zubair added a comment - socrates I have been waiting for your response on this issue. It would greatly be appreciated if we could please get some help specifically on the error we are getting as mentioned above. I assume the plugin is not able to connect to the Jenkins master instance to fetch the test result of the downstream sample job, so the result is a connection error. But this is my guess. 

          zubair added a comment -

          socrates  We have fixed the issue at our end causing Test Results Aggregator plugin to fail while fetching the test results. This ticket can be closed. Thank you for all of your help!

          zubair added a comment - socrates   We have fixed the issue at our end causing Test Results Aggregator plugin to fail while fetching the test results. This ticket can be closed. Thank you for all of your help!

            socrates Socrates Sidereas
            zubairbhat zubair
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: