"Changes will take effect when you restart Hudson" permanently

[tcendrowski-2]

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.

[Andrey Myatlyuk]

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 <[hidden email]> 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.

[Matthew.Webber]

What are you running, Hudson or Jenkins?
 

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Andrey
> Myatlyuk
> Sent: 19 June 2012 16:02
> To: [hidden email]
> Cc: [hidden email]
> Subject: Re: "Changes will take effect when you restart Hudson" permanently
>
> 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 <[hidden email]> 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.

--
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom

[tcendrowski-2]

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 <[hidden email]> 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.

[Andrey Myatlyuk]

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)
• Environment variable not available for Maven build/POM parsing. (issue 8865)
• Fixed a dead lock in concurrent builds of the same Maven projects. (issue 4220)
• Plugin Manager incorrectly displays "Changes will take effect when you restart Jenkins". (issue 8917)
• Added Manage Jenkins link in sidepanel of Plugin Manager and Update Center. (issue 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)
• Defined a mechanism to replace some of the key UI text. (issue 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 <[hidden email]> 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 <[hidden email]> 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.

[tcendrowski-2]

Unfortunately I have to stay with this Hudson version. How can I get only this patch?

On Wednesday, June 20, 2012 6:00:33 PM UTC+2, Andrey Myatlyuk wrote:

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)
• Environment variable not available for Maven build/POM parsing. (issue 8865)
• Fixed a dead lock in concurrent builds of the same Maven projects. (issue 4220)
• Plugin Manager incorrectly displays "Changes will take effect when you restart Jenkins". (issue 8917)
• Added Manage Jenkins link in sidepanel of Plugin Manager and Update Center. (issue 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)
• Defined a mechanism to replace some of the key UI text. (issue 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 <[hidden email]> 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 <[hidden email]> 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.

[Andrey Myatlyuk]

I have compiled 1.389 with just this change for you. You can take it from here:

https://dl.dropbox.com/u/290671/hudson.war

Or you can build it yourself as well, just take the source from github, apply the change and build the server.

$ git checkout hudson-1_389

-- apply the change from https://github.com/jenkinsci/jenkins/commit/584112aa274fcc698dd19db7e89900ede4bd1a9d

$ mvn clean package -Plight-test

Let me know how it works for you.

Andrey

On Thu, Jun 21, 2012 at 1:54 AM, tcendrowski <[hidden email]> wrote:

Unfortunately I have to stay with this Hudson version. How can I get only this patch?

On Wednesday, June 20, 2012 6:00:33 PM UTC+2, Andrey Myatlyuk wrote:

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)
• Environment variable not available for Maven build/POM parsing. (issue 8865)
• Fixed a dead lock in concurrent builds of the same Maven projects. (issue 4220)
• Plugin Manager incorrectly displays "Changes will take effect when you restart Jenkins". (issue 8917)
• Added Manage Jenkins link in sidepanel of Plugin Manager and Update Center. (issue 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)
• Defined a mechanism to replace some of the key UI text. (issue 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 <[hidden email]> 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 <[hidden email]> 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.

[tcendrowski-2]

Thank You. I have another problem with Hudson. In 1.389 version it's impossible after installing plot plugin and post-build task plugin to move post-build task section before plot plugin. I see that in jenkins it is possible just like moving shell script fields. Is it any simple way to patch it?

On Thursday, June 21, 2012 11:07:04 PM UTC+2, Andrey Myatlyuk wrote:

I have compiled 1.389 with just this change for you. You can take it from here:

https://dl.dropbox.com/u/290671/hudson.war

Or you can build it yourself as well, just take the source from github, apply the change and build the server.

$ git checkout hudson-1_389

-- apply the change from https://github.com/jenkinsci/jenkins/commit/584112aa274fcc698dd19db7e89900ede4bd1a9d

$ mvn clean package -Plight-test

Let me know how it works for you.

Andrey

On Thu, Jun 21, 2012 at 1:54 AM, tcendrowski <[hidden email]> wrote:

Unfortunately I have to stay with this Hudson version. How can I get only this patch?

On Wednesday, June 20, 2012 6:00:33 PM UTC+2, Andrey Myatlyuk wrote:

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)
• Environment variable not available for Maven build/POM parsing. (issue 8865)
• Fixed a dead lock in concurrent builds of the same Maven projects. (issue 4220)
• Plugin Manager incorrectly displays "Changes will take effect when you restart Jenkins". (issue 8917)
• Added Manage Jenkins link in sidepanel of Plugin Manager and Update Center. (issue 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)
• Defined a mechanism to replace some of the key UI text. (issue 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 <[hidden email]> 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 <[hidden email]> 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.

[Andrey Myatlyuk]

It is definitely possible to patch any changes which were made to Jenkins codebase to support that functionality. 

I'm afraid it will involve quite a few changes along the way, that effectively your instance code will be upgraded to other version.

It does make sense to investigate migration path for newer version of Jenkns instead. 

https://wiki.jenkins-ci.org/display/JENKINS/Upgrading+from+Hudson+to+Jenkins

Andrey

On Jul 2, 2012, at 3:18 AM, tcendrowski <[hidden email]> wrote:

Thank You. I have another problem with Hudson. In 1.389 version it's impossible after installing plot plugin and post-build task plugin to move post-build task section before plot plugin. I see that in jenkins it is possible just like moving shell script fields. Is it any simple way to patch it?

On Thursday, June 21, 2012 11:07:04 PM UTC+2, Andrey Myatlyuk wrote:

I have compiled 1.389 with just this change for you. You can take it from here:

https://dl.dropbox.com/u/290671/hudson.war

Or you can build it yourself as well, just take the source from github, apply the change and build the server.

$ git checkout hudson-1_389

-- apply the change from https://github.com/jenkinsci/jenkins/commit/584112aa274fcc698dd19db7e89900ede4bd1a9d

$ mvn clean package -Plight-test

Let me know how it works for you.

Andrey

On Thu, Jun 21, 2012 at 1:54 AM, tcendrowski <[hidden email]> wrote:

Unfortunately I have to stay with this Hudson version. How can I get only this patch?

On Wednesday, June 20, 2012 6:00:33 PM UTC+2, Andrey Myatlyuk wrote:

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)
• Environment variable not available for Maven build/POM parsing. (issue 8865)
• Fixed a dead lock in concurrent builds of the same Maven projects. (issue 4220)
• Plugin Manager incorrectly displays "Changes will take effect when you restart Jenkins". (issue 8917)
• Added Manage Jenkins link in sidepanel of Plugin Manager and Update Center. (issue 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)
• Defined a mechanism to replace some of the key UI text. (issue 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 <[hidden email]> 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 <[hidden email]> 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.