Hello,

I have this problem for the longest time but never got around to fixing it 
until recently.

I am running jenkins on winstone with java wrapper.

In my wrapper.conf, we have set 8070 as the http port that our jenkins 
instance listens to.

When starting or restarting my jenkins instance manually from command line, 
e.g. rc.d start jenkins, everything works as expected and my instance is 
launched and bound to the 8070 port.

However, after I have installed a jenkins plugin and selected the "go into 
automatic restart after plugin install", my jenkins instance gets started 
up on *port 32000*. I am not sure why this happens and everytime this 
happens, I have to - in command line - manually stop my jenkins instance 
and start it again.

Is there a configuration that I need to set to ensure that my jenkins - 
when restarted from its interface - uses the java wrapper service (which 
contains the correct port - 8070)?

I have also just posted up this question on stackoverflow so if you are an 
SO user, I am also tracking replies here - 
http://stackoverflow.com/questions/11886538/jenkins-restart-with-wrong-port-after-plugin-install

Thanks!
Calvin

Reply via email to