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
> please add your comments h
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 roo
Vincent:
I can not see this in the changelog
http://jenkins-ci.org/changelog
which issue was that?
Andrei.
On Saturday, June 9, 2012 4:47:36 AM UTC-5, Vincent Latombe wrote:
>
> Hello,
>
> I think this has already been fixed toward 1.469, since it was causing
> regressions with sonar jobs as
Hello,
I think this has already been fixed toward 1.469, since it was causing
regressions with sonar jobs as well.
Vincent
2012/6/8 Andrei Pozolotin
> can you please file this bug on jenkins bug tracker?
> (I can not access it)
> thank you.
>
>
> On Wednesday, June 6, 2012 11:07:24 AM UTC-5,
can you please file this bug on jenkins bug tracker?
(I can not access it)
thank you.
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 chang
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
