"Restrict where this project can be run" not saving...

[Jason Swager]

We've been running Jenkins 1.471 for a few days, and just updated a couple plugins (XTrigger ones).  After the restart, we found that for no job can set the "Restrict where this project can be run".  Regardless of what value that is enter and Saved, the field is blank when reloaded.  

Has anyone else seen this?  Might it be related to a recent plugin change?

I haven't seen any JIRA items submitted for this, so I'm wondering if it's "just my system".

[Matthew.Webber]

I don’t think it is just you. I just noticed that we had a number of jobs waiting for executors, but the master and all slaves were idle. Restarting the master did not help. Moreover, I think that the affected jobs previously had “restrict where this project can run” set, but now it’s unset.

I’m guessing it’s related to one of the following updates which I did yesterday

Build result trigger plugin 0.7 à 0.8

Monitoring plugin 1.39 à 1.39

Promoted builds plugin 2.5 à 2.6

 

Yep, downgrading  the promoted builds plugin to 2.5 fixes the problem of the “"Restrict where this project can be run" value not being saved.

 

If the original reporter could file a ticket, that would be good.

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of Jason Swager
Sent: 22 June 2012 20:38
To: [hidden email]
Subject: "Restrict where this project can be run" not saving...

 

We've been running Jenkins 1.471 for a few days, and just updated a couple plugins (XTrigger ones).  After the restart, we found that for no job can set the "Restrict where this project can be run".  Regardless of what value that is enter and Saved, the field is blank when reloaded.  

 

Has anyone else seen this?  Might it be related to a recent plugin change?

 

I haven't seen any JIRA items submitted for this, so I'm wondering if it's "just my system".

[Jason Swager]

https://issues.jenkins-ci.org/browse/JENKINS-14197 submitted

[da7489]

Thanks, I just ran into the same issue after installing the above mentioned plugin.
Downgrading it to 2.5 fixed the problem.

[Xiaopan Bao]

Hi
How's this issue going on?
I also met this problem, now it's block my projects.

在 2012年6月23日星期六UTC+8上午3时38分28秒，Jason Swager写道：

We've been running Jenkins 1.471 for a few days, and just updated a couple plugins (XTrigger ones).  After the restart, we found that for no job can set the "Restrict where this project can be run".  Regardless of what value that is enter and Saved, the field is blank when reloaded.  

Has anyone else seen this?  Might it be related to a recent plugin change?

I haven't seen any JIRA items submitted for this, so I'm wondering if it's "just my system".

在 2012年6月23日星期六UTC+8上午3时38分28秒，Jason Swager写道：

We've been running Jenkins 1.471 for a few days, and just updated a couple plugins (XTrigger ones).  After the restart, we found that for no job can set the "Restrict where this project can be run".  Regardless of what value that is enter and Saved, the field is blank when reloaded.  

Has anyone else seen this?  Might it be related to a recent plugin change?

I haven't seen any JIRA items submitted for this, so I'm wondering if it's "just my system".

[Xiaopan Bao]

sorry, I saw the solution just now.  thx very much, I will try now...

在 2012年6月23日星期六UTC+8上午3时38分28秒，Jason Swager写道：

We've been running Jenkins 1.471 for a few days, and just updated a couple plugins (XTrigger ones).  After the restart, we found that for no job can set the "Restrict where this project can be run".  Regardless of what value that is enter and Saved, the field is blank when reloaded.  

Has anyone else seen this?  Might it be related to a recent plugin change?

I haven't seen any JIRA items submitted for this, so I'm wondering if it's "just my system".