Hi,
I opened another thread on the mailing list regarding builds from new
configurations lost in existing matrix job.
Both problems look similar even though I did not loose any builds on disk
and I did not need to restart Jenkins
to loose the builds in Jenkins interface.
Strange thing, upgrading
Here we go: https://issues.jenkins-ci.org/browse/JENKINS-16014
If anyone finds any interesting info about this one, feel free to add it. I
don't have any useful logs that explain what is going on.
Will do, but I need to try this in another environment because I still
don't have a proper sequence to understand/reproduce this...
It's similar but not exactly the same as other cases I've seen on the list,
other posts don't mention folders being purged from the slave build
directory.
On Satur
Could you open a bug for this?
A.
On Thu, Nov 29, 2012 at 3:28 AM, Michaël Serisier <
michael.seris...@gmail.com> wrote:
> Hi all,
>
> I have several jobs set to use a configuration matrix. Since I upgraded to
> 1.492, it looks like builds are lost after each Jenkins restart. This
> happens for
Hi all,
I have several jobs set to use a configuration matrix. Since I upgraded to
1.492, it looks like builds are lost after each Jenkins restart. This
happens for some jobs only.
I have already had problems loading the old builds in such jobs in the past
(after the changes made to improve Je
