detailed test results on local bamboo server goes to seemingly random ip address

andrew January 8, 2016

This question is in reference to Atlassian Documentation: JUnit Parser

JUnit parser is reading my testresults.xml file and reporting correctly. 

 Screenshot 2016-01-08 10.28.40.png

Protractor with JUNIT has 7 Protractor tests that run and report to the Build Dashboard appropriately. It also shows correctly all the way down until you want to see the actual results of the test. 

 Screenshot 2016-01-08 10.29.01.png

This is the Project page showing the plans. 

Screenshot 2016-01-08 10.29.30.png

And this is the Plan summary, again showing 7 tests passed. 

Clicking on the "7 passed" link takes you to the Test results page.  

Screenshot 2016-01-08 10.29.39.png

Everything works as expected until you click on the "See detailed test results for Test Protractor". Then, rather than going to 'localhost:8085/browse/ANG-JUN-JOB1-3/test' it goes to a seemingly random ip address that fails to load. 

Screenshot 2016-01-08 10.29.58.png

10.2.2.56 isn't my ip address, and doesn't show up in any traceroute that i've run. it also appears nowhere in the code generating the reports. 

 

Why is bamboo routing to a nonsense IP, and how can i keep it pointing to the actual bamboo server (in this case localhost)? 

 

For technicals, I have Protractor running e2e tests on Angular.JS code which is then reporting with the node module jasmine-reporter, using this repo:

 https://github.com/excenter/angular-phonecat

which is a fork of 

https://github.com/angular/angular-phonecat

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Answer accepted
andrew January 8, 2016

In Admin/ General configuration, under "What is the server's address?" the pre-filled information is 10.2.2.56, with a hint of "This is the base URL of this installation of Bamboo. All links created (for emails etc) will be prefixed by This URL. for example "http://10.2.2.75:8085"" 

Changing the base URL to 10.2.2.75:8085 fixes the issue. 
this seems to be an issue where an IP address changed from when I set up the server, where most pages when on localhost refer to localhost rather than the base URL, but Detailed test results does not.

I'm going to see if I can file a bug.  

TAGS
AUG Leaders

Atlassian Community Events