-
Bug
-
Resolution: Fixed
-
Blocker
-
None
-
Jenkins 2.401.3
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:
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!
[JENKINS-72829] Test Rsults aggregator gives Job NOT_FOUND with error Cannot invoke
Tamilarasan
added a comment - Can you guide me, how do I see the jenkins.log file? Tamilarasan
added a comment - Socrates Sidereas, any update on this issue ? Hello, i have a fix that could be the case in this issue, in the next release is going to be available,
so I would appreciate it if you can test once more using the latest release, thanks in advance, and sorry for the delays .
Tamilarasan
added a comment - socrates - I have tested the same with new released plugin version. I am getting similar error but with the different error messages. Error messages are mentioned below.
Console output from the error lines,
Total Jenkins jobs found 57 and Aggregator has resolved successfully 1/1.
Collect data
ERROR No last build details for job configuration job1 nullNo last build details for job configuration job1 nullNo last build details for job configuration job1 nullNo last build details for job configuration job1 null
Job 'job1' null
Job 'job1' found NOT_FOUND with error: Cannot invoke
"com.jenkins.testresultsaggregator.data.BuildWithDetailsAggregator.setResults(com.jenkins.testresultsaggregator.data.JobResults)" because the return value of "com.jenkins.testresultsaggregator.data.Job.getLast()" is null (0s)
Collect data .. Finished
Analayse .Finished
Note: I see the last build details is available and in the received mail I see "Job1" and no other details. Job1 is having a link with Jenkins baseURL. I am thinking with the Jenkins Base URL plugin is not able to get the last build details. If the URL is try accessing the https URL , it will be fetching the details. This is my assumption, please have a look.
Tamilarasan
added a comment - socrates - I have tested the same with new released plugin version. I am getting similar error but with the different error messages. Error messages are mentioned below.
Console output from the error lines,
Total Jenkins jobs found 57 and Aggregator has resolved successfully 1/1.
Collect data
ERROR No last build details for job configuration job1 nullNo last build details for job configuration job1 nullNo last build details for job configuration job1 nullNo last build details for job configuration job1 null
Job 'job1' null
Job 'job1' found NOT_FOUND with error: Cannot invoke
"com.jenkins.testresultsaggregator.data.BuildWithDetailsAggregator.setResults(com.jenkins.testresultsaggregator.data.JobResults)" because the return value of "com.jenkins.testresultsaggregator.data.Job.getLast()" is null (0s)
Collect data .. Finished
Analayse .Finished
Note: I see the last build details is available and in the received mail I see "Job1" and no other details. Job1 is having a link with Jenkins baseURL. I am thinking with the Jenkins Base URL plugin is not able to get the last build details. If the URL is try accessing the https URL , it will be fetching the details. This is my assumption, please have a look. Hello, is the job named configuration job1 ? ... I think the space in the job name is the issue, I will check it ASAP.
Meanwhile, if you have the availability you can test it again with a job name like configuration_job1
–
It looks like spaces into job names are handled, so this is not our case,
But i am still wondering about your job name, the error says :
ERROR No last build details for job configuration job1 null
It says: job configuration job1 ,
not job1 ... but the keyword configuration is not something from the plugin. can you please share more info?
Tamilarasan
added a comment - There is slight communication missed from my end. In the error also it says the actual job name, I do not want to give the exact name. That's the reason I mentioned as job1. We created a job name with _ and I am sure there is no issue with the job name. So the Job1 mentioned in the console indicates the actual job name.
Please have a look.
Thanks!
Tamilarasan
added a comment - There is slight communication missed from my end. In the error also it says the actual job name, I do not want to give the exact name. That's the reason I mentioned as job1. We created a job name with _ and I am sure there is no issue with the job name. So the Job1 mentioned in the console indicates the actual job name.
Please have a look.
Thanks! Ok understood. I will try to guess a few things like the suspicious "We have the load runner in the backend, so we converted the Jenkins base URL to https://jenkinsurl."
This could be a reason for the failure since the plugin is using one connection with Jenkins shared in threads for each job. Load balancer may interrupt this connection and thus the null result for the last build. I will try to change this and also print the stack trace into the console.log in the next release.
Tamilarasan
added a comment - socrates - do you have any updates on this issue?
Thanks!
Tamil. 
hi tamilarasan, i would like to have if possible the jenkins.log to see the full stack trace