Hi! This issue was resolved in Jenkins version 1.401
What's new in 1.401 (2011/03/13) - Fix for JENKINS-8711 breaks deployments with credentials (issue 8939<http://issues.jenkins-ci.org/browse/JENKINS-8939> ) - Environment variable not available for Maven build/POM parsing. (issue 8865 <http://issues.jenkins-ci.org/browse/JENKINS-8865>) - Fixed a dead lock in concurrent builds of the same Maven projects. (issue 4220 <http://issues.jenkins-ci.org/browse/JENKINS-4220>) - Plugin Manager incorrectly displays "Changes will take effect when you restart Jenkins". (issue 8917<http://issues.jenkins-ci.org/browse/JENKINS-8917> ) - Added Manage Jenkins link in sidepanel of Plugin Manager and Update Center. (issue 8780 <http://issues.jenkins-ci.org/browse/JENKINS-8780>) - Thread dump now reports all the threads from all the slaves, not just the master. - Made the extension point implementation discovery logic customizable by a plugin (issue 8897<http://issues.jenkins-ci.org/browse/JENKINS-8897> ) - Defined a mechanism to replace some of the key UI text. (issue 8579<http://issues.jenkins-ci.org/browse/JENKINS-8579> ) Is there any way for you to upgrade? If you are in the environment where the software upgrade takes time, you will be better by using Long Term Support(LTS) version of Jenkins. Currently it is 1.447.2 If you would like to migrate from Hudson to Jenkins, here's the link with the instructions to follow: https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins Another way to fix it would be to build 1.389 with the patch in. Hope it helps. Andrey On Wed, Jun 20, 2012 at 2:52 AM, tcendrowski <brandnewd...@interia.pl>wrote: > Yes, after few restarts message is still there. Hm, in which log? In > hudson.err.log and hudson.out.log last entries are from few days before it > happened. And no warning in plugin page. Unfortunately I have to work on > Hudson 1.389. > > > On Tuesday, June 19, 2012 5:01:40 PM UTC+2, Andrey Myatlyuk wrote: >> >> Hi! >> So you restarted Jenkins process and the message still there? Any >> exceptions in the log? Any warnings on plugins page? Can you try to upgrade >> to latest (1.471) version? >> Andrey >> >> On Jun 19, 2012, at 7:50 AM, tcendrowski <brandnewd...@interia.pl> >> wrote: >> >> > Hi, >> > >> > After installing 2 plugins and restarting Hudson (1.389) this message >> is still shown. I've ridden that it could be beacuse of incorrect hudson >> shutdown. Do you know what to do to make this message disappear? >> > >> > Greets. >> >
