Missing build status in the build history of several jobs

37 views
Skip to first unread message

ludovic.v...@atos.net

unread,
Nov 30, 2015, 2:53:58 AM11/30/15
to Jenkins Users

Dear,

 

We are currently using Jenkins 1.596.3 and we are facing issues with several Jenkins jobs for which the status of several builds is missing in the job history.

 

As an example, we have a job X for which the history displays the following build results:

 

    build 28 (job failed)

    build 27 (job failed)

    build 26 (job successfull)

    build 23 (job failed)

    build 21 (job failed)

    build 20 (job successfull)

 

The results of the builds #22, #24 and #25 are not displayed in the history of the job.

 

However, on the server, I see the following subdirectories:

 

lrwxrwxrwx 1 www server    2 Oct  9 20:55 lastUnstableBuild -> -1

 

lrwxrwxrwx
1 www server   19 Oct 20 19:30 20 -> 2015-10-20_19-30-25

drwxr
-xr-x 2 www server 4096 Oct 20 20:55 2015-10-20_19-30-25

lrwxrwxrwx
1 www server   19 Oct 21 19:30 21 -> 2015-10-21_19-30-27

drwxr
-xr-x 2 www server 4096 Oct 21 20:59 2015-10-21_19-30-27

lrwxrwxrwx
1 www server   19 Oct 22 19:30 22 -> 2015-10-22_19-30-22

drwxr
-xr-x 2 www server 4096 Oct 22 19:30 2015-10-22_19-30-22

lrwxrwxrwx
1 www server   19 Oct 23 12:19 23 -> 2015-10-23_12-19-12

drwxr
-xr-x 2 www server 4096 Oct 23 14:35 2015-10-23_12-19-12

lrwxrwxrwx
1 www server   19 Oct 23 19:30 24 -> 2015-10-23_19-30-28

drwxr
-xr-x 2 www server 4096 Oct 23 19:30 2015-10-23_19-30-28

lrwxrwxrwx
1 www server   19 Oct 24 19:30 25 -> 2015-10-24_19-30-26

drwxr
-xr-x 2 www server 4096 Oct 24 19:30 2015-10-24_19-30-26

lrwxrwxrwx
1 www server   19 Oct 26 07:06 26 -> 2015-10-26_07-06-15

lrwxrwxrwx
1 www server    2 Oct 26 08:17 lastStableBuild -> 26

lrwxrwxrwx
1 www server    2 Oct 26 08:17 lastSuccessfulBuild -> 26

drwxr
-xr-x 2 www server 4096 Oct 26 08:17 2015-10-26_07-06-15

lrwxrwxrwx
1 www server   19 Oct 26 19:30 27 -> 2015-10-26_19-30-24

drwxr
-xr-x 2 www server 4096 Oct 27 00:15 2015-10-26_19-30-24

lrwxrwxrwx
1 www server   19 Oct 27 00:30 28 -> 2015-10-27_00-30-28

lrwxrwxrwx
1 www server    2 Oct 27 03:00 lastFailedBuild -> 28

lrwxrwxrwx
1 www server    2 Oct 27 03:00 lastUnsuccessfulBuild -> 28

drwxr
-xr-x 2 www server 4096 Oct 27 03:00 2015-10-27_00-30-28

lrwxrwxrwx
1 www server   19 Oct 27 19:30 29 -> 2015-10-27_19-30-27

drwxr
-xr-x 2 www server 4096 Oct 27 19:30 2015-10-27_19-30-27


 

As you can see it, the builds #22, #24 and #25 are available on the disk.

 

However, in the subdirectories related to these builds, compared to the other builds which are well displayed, it seems that we are missing some files (build.xml and injectedEnvVars.txt):

 

ls -l 22/*

 

-rw-r--r-- 1 www server    6 Oct 22 19:30 22/changelog.xml

-rw-r--r-- 1 www server 1027 Oct 22 19:30 22/log

ls -l 24/*

-rw-r--r-- 1 www server    6 Oct 23 19:30 24/changelog.xml

-rw-r--r-- 1 www server 1672 Oct 23 19:30 24/log

ls -l 25/*

-rw-r--r-- 1 www server    6 Oct 24 19:30 25/changelog.xml

-rw-r--r-- 1 www server 1672 Oct 24 19:30 25/log


 

The logs of our Jenkins instance do not provide any information which can help us to understand the root cause of the issue.

 

There was no unavailability on the Jenkins instance at that time.

 

You will find attached to this ticket the files related to these builds which are not displayed in the history.

 

Could you please help us to identify the root cause of the issue ?

 

FYI: this ticket related to https://issues.jenkins-ci.org/browse/JENKINS-31228 which has been rejected for the following reason:

 

Daniel Beck added a comment - 17/Nov/15 12:53 PM

 

This is an issue tracker, not a support site. Furthermore, 1.596.x and 1.609.x are no longer supported, you need to show a bug exists on 1.625.x to get attention in this tracker.

 

To get help, ask the jenkinsci-users mailing list, or in #jenkins on Freenode.

 

 

Thanks

lvot...@redhat.com

unread,
Nov 30, 2015, 2:00:12 PM11/30/15
to Jenkins Users
It is possible that builds are not loaded. Try to check if Jenkins displays them - <url of job>/22. If Jenkins does not display them by UI, it means that probably builds are not loaded. In this case try to check Jenkins log if there is an error message about not loading these jobs. 

Daniel Beck

unread,
Nov 30, 2015, 4:14:00 PM11/30/15
to jenkins...@googlegroups.com

On 30.11.2015, at 20:00, lvot...@redhat.com wrote:

> It is possible that builds are not loaded.

The build.xml are missing, so they cannot be loaded.

---

Maybe these builds were deleted, and deletion was incomplete?

ludovic.v...@atos.net

unread,
Dec 1, 2015, 3:05:39 AM12/1/15
to Jenkins Users, m...@beckweb.net
Dear,

Accessing to the url <url-of-my-job>/22 displays an error 404.

I also did not find any reference to the deletion of this build in the logs of Jenkins (stdout.log and audit.log)

May I ask you what can cause missing build.xml files and how we can avoid such issues ?

Best regards

Victor Martinez

unread,
Dec 1, 2015, 5:03:35 AM12/1/15
to Jenkins Users, m...@beckweb.net
That's an interesting topic

I've never had such an issue, does anybody got access to remove files in the server? As far as I see, if you delete a particular build it won't throw any log traces by default, you will need to add some debug level, I guess so

Cheers

ludovic.v...@atos.net

unread,
Dec 1, 2015, 5:21:28 AM12/1/15
to Jenkins Users, m...@beckweb.net
No, only my team has an access to the server on which the Jenkins jobs are stored and we did not perform such a removal.
Reply all
Reply to author
Forward
0 new messages