Agreed, I am seeing this issue too after the "upgrade" to 1.467 I have also experienced the loss of 90% of my jobs even though they still exist on disk
On Wednesday, 6 June 2012 17:07:24 UTC+1, 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 > >
