I have seen similar issue. But only with jobs that have been renamed. Fix
for my instance is a restart of Jenkins. Build history come back.
Den 28. juni 2013 12.12 skrev "Louis Roché" følgende:
> I have the same problem. But my job has many build steps.
>
> I don't know why yet, but it's really a
I have the same problem. But my job has many build steps.
I don't know why yet, but it's really annoying.
L.
On Wednesday, June 26, 2013 10:49:42 PM UTC+2, Michael Smolyak wrote:
>
> The build in question does not have any build steps. All it does is pulls
> a repository from Git and exposes fi
I don't have an answer for you, but I'm seeing similar results with auto
triggered builds.
I did temporarily fix the issue by deleting all of my history, but the
problem came back after a couple weeks worth of builds again.
I've reverted back to some older builds of Jenkins but still run into the
The build in question does not have any build steps. All it does is pulls a
repository from Git and exposes files in one of the directories as build
artifacts to be used by Ansible scripts.
The problem is that the build history along with the build artifacts gets
removed automatically shortly a
