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: jenkinsci-users@googlegroups.com [mailto:jenkinsci-users@googlegroups.com] On Behalf Of Jason Swager Sent: 22 June 2012 20:38 To: jenkinsci-users@googlegroups.com 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".
