I don't think there is a corresponding issue, but the commit is https://github.com/jenkinsci/jenkins/commit/486be0748ad99adb755d5460f742cd58f81f5b88
According to several tweets, it seems to be fixed in the latest (1.470) release. Vincent 2012/6/16 Andrei Pozolotin <andrei.pozolo...@gmail.com> > please add your comments here > https://issues.jenkins-ci.org/browse/JENKINS-14123 > > > On Wednesday, June 6, 2012 11:07:24 AM UTC-5, Andrei Pozolotin wrote: > >> jenkns version 1.467 >> >> problem: >> >> project uses rootPOM path spec such as >> parent/child/pom.xml >> >> if you edit job config after change rootPOM entry looks fine >> >> after jenkins restart, if you edit job config now, >> rootPOM entry looks empty, despite appropriate entry >> is present OK in job/config.xml and job builds fine; >> >> if you now merely edit and save job config, >> the rootPOM entry is lost in job/config.xml >> and job does not build any more >> >>
