Tracker fails to update jenkins server address

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Edit the settings of a server changing the port to the new port value (the 
server responds to that new port and no longer to the old one, according to the 
web frontend)
2. Select the jobs to monitor
3. Observe that on the main window, the addresses of the jobs remain with the 
old port number and yet fail to contact the server.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system? 0.12.3.0


Please provide any additional information below.

Original issue reported on code.google.com by [email protected] on 27 May 2014 at 12:00

[GoogleCodeExporter]

This is a critical defect because the tray tracker is now useless to me. 
Reinstalling it doesn't fix the issue because it remembers the previous 
configuration.

Original comment by [email protected] on 27 May 2014 at 12:02

[GoogleCodeExporter]

it's because <JenkinsServer>/Configure contains wrong "Jenkins Location" 
address. 
Blank this field and save changes. 

Original comment by [email protected] on 4 Sep 2014 at 11:03

[GoogleCodeExporter]

Edit %appdata%\Hudson Tray Tracker\hudson.configuration with notepad++ or 
equivalent to update the server address.

Btw, i am trying to take over this project with lots of bug fixes, enhancements 
and features but the owner is too busy to respond.

Original comment by [email protected] on 23 Nov 2014 at 10:47

[GoogleCodeExporter]

<<i am trying to take over this project>>
great!!!

Original comment by [email protected] on 26 Nov 2014 at 5:52

[GoogleCodeExporter]

Any solution to this?

Original comment by [email protected] on 26 Nov 2014 at 3:25

[GoogleCodeExporter]

I made a fix and released an alpha version of Jenkins Tray.
https://github.com/zionyx/jenkins-tray/releases/tag/v1.0-alpha2

Please let me know if it fixes your problems. Please comment on the issue here: 
https://github.com/zionyx/jenkins-tray/issues/25, if it works for you.

Thank you.

Original comment by [email protected] on 22 Jan 2015 at 3:04