[JIRA] (JENKINS-50595) build history disappeared after upgrade to 2.107.1

0 views
Skip to first unread message

jennifer_schuch@datacard.com (JIRA)

unread,
Apr 5, 2018, 10:43:03 AM4/5/18
to jenkinsc...@googlegroups.com
Jennifer schuch created an issue
 
Jenkins / Bug JENKINS-50595
build history disappeared after upgrade to 2.107.1
Issue Type: Bug Bug
Assignee: Unassigned
Attachments: image-2018-04-05-09-37-38-986.png, image-2018-04-05-09-38-50-846.png, image-2018-04-05-09-39-42-624.png, image-2018-04-05-09-40-43-041.png
Components: core
Created: 2018-04-05 14:42
Priority: Major Major
Reporter: Jennifer schuch

After upgrade to 2.107.1 windows from 2.89.3, build history disappeared for jobs that have either been renamed during their life or jobs where the build.xml was updated via file system and configuration reloaded from disk. attached is an example of 3 days of missing build history for a job that was renamed in January.

 

 

 
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

jennifer_schuch@datacard.com (JIRA)

unread,
Apr 5, 2018, 10:54:01 AM4/5/18
to jenkinsc...@googlegroups.com
Jennifer schuch commented on Bug JENKINS-50595
 
Re: build history disappeared after upgrade to 2.107.1

Also to note, the jobs that don't show the 3 days worth of build history, per configuration, where running when 'reload configuration from disk' was triggered for updates made to other jobs that where to begin their runtime within a few hours. The jobs updated outside the UI show no history although everthing is on the file system.

o.v.nenashev@gmail.com (JIRA)

unread,
Apr 5, 2018, 12:40:02 PM4/5/18
to jenkinsc...@googlegroups.com

Do you see any errors in the System logs? Maybe Build entries refuse to load due to the non-whitelisted classes (JEP-200) or maybe due to a regression with XML 1.1 introduction

thomas.frearson@cornerstonenw.com (JIRA)

unread,
Apr 13, 2018, 10:05:03 AM4/13/18
to jenkinsc...@googlegroups.com

Do all of your builds have a build.xml file in them? I'm having a similar issue, and I believe that is the reason they aren't showing up in the build history. I'm not sure why the build.xml file isn't being generated yet though.

thomas.frearson@cornerstonenw.com (JIRA)

unread,
Apr 13, 2018, 1:17:02 PM4/13/18
to jenkinsc...@googlegroups.com
Thomas Frearson edited a comment on Bug JENKINS-50595
Do all of your builds have a build.xml file in them (in the <build number> directory on the master) ? I'm having a similar issue, and I believe that is the reason they aren't showing up in the build history. I'm not sure why the build.xml file isn't being generated yet though.

jennifer_schuch@datacard.com (JIRA)

unread,
Apr 16, 2018, 1:02:01 PM4/16/18
to jenkinsc...@googlegroups.com

nothing is being reported in the system logs. appears that the config.xml upgraded to 1.1, i reverted back my installation of Jenkins to the previous version I had on this server. Build history seems to now be 'lost'. decided to purge build history of impacted build jobs and start anew.

there is/are no build.xml files located in root of <build number> directory of impacted build jobs. build.xml does exist in build number directories of jobs not impacted by this issue.  how would these build.xml files 'disappear'?

thomas.frearson@cornerstonenw.com (JIRA)

unread,
Apr 16, 2018, 1:22:03 PM4/16/18
to jenkinsc...@googlegroups.com

decided to purge build history of impacted build jobs and start anew

Did this work? Do the affected builds now have a build history? I have a few job that are being affected and may have to do the same.

I'm not sure how those build.xml files stopped being created in each build. That's the correlation I noticed though, is that jobs with accurate build history had a build.xml file in each build dir, job with disappearing history didn't have one.

I'm surprised that no one else has reported this issue, not sure what to do next short of re-deploying the build master to see if that fixes it.

jennifer_schuch@datacard.com (JIRA)

unread,
Apr 16, 2018, 1:39:01 PM4/16/18
to jenkinsc...@googlegroups.com

I'll find out by tomorrow morning. Those jobs are scheduled to run this evening. I'll update tomorrow.  For this update, I had selected their 'upgrade automatically'. Is this how you updated? I'm wondering if it's an issue via their war, instead of using their windows installer package.

thomas.frearson@cornerstonenw.com (JIRA)

unread,
Apr 16, 2018, 2:08:02 PM4/16/18
to jenkinsc...@googlegroups.com

going to this latest release, yes. I used the "upgrade automatically". for the last release though, I switched from the weekly builds to the Stable build. I'm wondering if I had an issue somewhere in that process. 

jennifer_schuch@datacard.com (JIRA)

unread,
Apr 17, 2018, 10:32:03 AM4/17/18
to jenkinsc...@googlegroups.com

build.xml files are still missing when job completes. this is consistently happening to a group of build jobs, where other jobs (similiar jobs) are creating build.xml. Not able to determine why this group of jobs won't/don't create build.xml.

jennifer_schuch@datacard.com (JIRA)

unread,
Apr 17, 2018, 2:17:01 PM4/17/18
to jenkinsc...@googlegroups.com

creating new jenkins job, using 'old' job as template, is our current work around. build history (i.e., build.xml is present) shows with newly created config.xml.

thomas.frearson@cornerstonenw.com (JIRA)

unread,
Apr 17, 2018, 2:20:02 PM4/17/18
to jenkinsc...@googlegroups.com

That's interesting. I had tried that and the build.xml file was present in the first build but not in any subsequent builds. 

I just updated the TAP plugin as I noticed that only builds involving TAP reports were exhibiting this behavior. Unfortunately, the newer versions of the TAP plugin don't work for me so I'm going to downgrade and see if it is still working after that.

julien.lafourcade@gmail.com (JIRA)

unread,
May 22, 2018, 12:17:01 PM5/22/18
to jenkinsc...@googlegroups.com

Hello,

 

We have exactly the same behavior. I see hold builds which have a build.xml inthe <build_number> folder. New build folders do not have build.xml. This only happens on build that are generated with jenkins DSL dans the seed plugin. 

 

Anyone knows what may be the cause ? 

 

Thx 

 

Julien

julien.lafourcade@gmail.com (JIRA)

unread,
May 22, 2018, 12:21:02 PM5/22/18
to jenkinsc...@googlegroups.com
Julien Lafourcade edited a comment on Bug JENKINS-50595
Hello,

 

We have exactly the same behavior. I see hold builds which have a build.xml inthe <build_number> folder. New build folders do not have build.xml. This only happens on build that are generated with jenkins DSL dans and the seed plugin. 


 

Anyone knows what may be the cause ? 

 

Thx 

 

Julien

aszmidt@infinera.com (JIRA)

unread,
May 24, 2018, 2:06:01 AM5/24/18
to jenkinsc...@googlegroups.com

We are also experiencing this issue in 2.107.3 as well. Is there any extra information that would be useful in addressing this bug?

aszmidt@infinera.com (JIRA)

unread,
May 24, 2018, 6:25:03 AM5/24/18
to jenkinsc...@googlegroups.com
Alfred Szmidt updated an issue
 
Change By: Alfred Szmidt
Priority: Major Blocker

thomas.frearson@cornerstonenw.com (JIRA)

unread,
May 24, 2018, 10:30:01 AM5/24/18
to jenkinsc...@googlegroups.com
Thomas Frearson commented on Bug JENKINS-50595
 
Re: build history disappeared after upgrade to 2.107.1

Alfred Szmidt Julien Lafourcade Jennifer schuch

I think to fix this issue, I had to install version 2.2.1 of the TAP plugin. I'm not sure if this fixes the issue or just puts a bandaid on things, and it wasn't the ideal solution as upgrading that plugin took away all test information other than pass/fail from my Slack reports. It seems to have kept the build history intact since I did that though, so I guess that's the better of two evils.

thomas.frearson@cornerstonenw.com (JIRA)

unread,
May 24, 2018, 10:34:03 AM5/24/18
to jenkinsc...@googlegroups.com
Thomas Frearson edited a comment on Bug JENKINS-50595
[~ams] [~jlafourc] [~schuchj]


I think to fix this issue, I had to install version 2.2.1 of the TAP plugin. I'm not sure if this fixes the issue or just puts a bandaid on things, and it wasn't the ideal solution as upgrading that plugin took away all test information other than pass/fail from my Slack reports. It seems to have kept the build history intact since I did that though, so I guess that's the better of two evils.


ETA: the reason I tried upgrading the TAP Plugin as a fix, is I eventually found that this issue only affected those job that were processing TAP results. Jobs that weren't were never affected by this bug. If you are noticing this happen, check if the jobs have TAP processing, and check your TAP plugin version.

noamshochat@gmail.com (JIRA)

unread,
Jun 4, 2018, 3:47:02 PM6/4/18
to jenkinsc...@googlegroups.com

We don't have TAP plugin installed and we also experienced this behaviour 

divyanshu_i@mechmocha.com (JIRA)

unread,
Jun 11, 2018, 6:31:01 AM6/11/18
to jenkinsc...@googlegroups.com

noam shochat
Check your system log you will find some errors 

divyanshu_i@mechmocha.com (JIRA)

unread,
Jun 11, 2018, 6:34:02 AM6/11/18
to jenkinsc...@googlegroups.com
Divyanshu Mehta updated an issue
 
Change By: Divyanshu Mehta
Attachment: groovy.log

divyanshu_i@mechmocha.com (JIRA)

unread,
Jun 11, 2018, 6:34:03 AM6/11/18
to jenkinsc...@googlegroups.com
 
Re: build history disappeared after upgrade to 2.107.1

I too face this issue the reason for the build disappearing is the the build.xml for the particular build is not being created at the end of the job. This mainly due to the JEP-200 changes to which several plugin have yet not made the changes. I am also facing this issue the error log for my casae is
groovy.log

divyanshu_i@mechmocha.com (JIRA)

unread,
Jun 11, 2018, 6:36:03 AM6/11/18
to jenkinsc...@googlegroups.com
Divyanshu Mehta edited a comment on Bug JENKINS-50595
I too face this issue the reason for the build disappearing is that the the build.xml for the particular build is not being created at the end of the job. This mainly due to the JEP-200 changes to which several plugin have yet not made the changes. I am also facing this issue the error log for my casae is
[^groovy.log]

divyanshu_i@mechmocha.com (JIRA)

unread,
Jun 11, 2018, 6:52:02 AM6/11/18
to jenkinsc...@googlegroups.com
Divyanshu Mehta edited a comment on Bug JENKINS-50595
I too face this issue the reason for the build disappearing is that the build.xml for the particular build is not being created at the end of the job. This mainly due to the JEP-200 changes to which several plugin have yet not made the changes. I am also facing this issue the error log for my casae case is
[^groovy.log]

darrell.taylor@skybettingandgaming.com (JIRA)

unread,
Jun 18, 2018, 8:40:02 AM6/18/18
to jenkinsc...@googlegroups.com

The solution for us was to uncheck the `Color ANSI Console Output` (xterm) in the Build Environment section.

This was on the only difference between our jobs that lost history and didn't, the overall job was essentially the same.

thomas.frearson@cornerstonenw.com (JIRA)

unread,
Jun 18, 2018, 11:28:02 AM6/18/18
to jenkinsc...@googlegroups.com

Darrell Taylor I have that checked too actually but as far as I can tell it doesn't actually do anything for my jobs. I may revert the TAP plugin and uncheck that and see if the build history is still working. Good find there!

Jennifer schuch is this plugin being used in jobs affected here?

yves.schumann@ti8m.ch (JIRA)

unread,
Nov 12, 2018, 1:36:02 AM11/12/18
to jenkinsc...@googlegroups.com

We have the same issue with Jenkins 2.121.3.

The visible history of all jobs which are created using Job-DSL disappear after some time (next day). The folders already exist on the master and each build folder has an build.xml. Jobs created using the OrgaScanner did not have this problem.

Please let me know if and which further details required to fix this.

 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

yves.schumann@ti8m.ch (JIRA)

unread,
Nov 12, 2018, 1:41:02 AM11/12/18
to jenkinsc...@googlegroups.com
Yves Schumann edited a comment on Bug JENKINS-50595
We have the same issue with Jenkins 2.121.3.

The visible history of all jobs which are created using Job-DSL disappear after some time (next day). The folders already exist on the master and each build folder has an contains a build.xml. Jobs created using the OrgaScanner did not have this problem.


Please let me know if and which further details required to fix this.

 

yves.schumann@ti8m.ch (JIRA)

unread,
Nov 14, 2018, 5:49:03 AM11/14/18
to jenkinsc...@googlegroups.com

Any news here? This is actually a show stopper...

yves.schumann@ti8m.ch (JIRA)

unread,
Nov 21, 2018, 4:01:02 AM11/21/18
to jenkinsc...@googlegroups.com

OK, I digged a little bit deeper into this. 

I setup the same automatic job creation we use on another Jenkins instance using bleeding edge Jenkins release. So I have a job, which creates other Jenkinsfile-based pipeline jobs using job dsl. The created jobs have one difference: Some of them have a periodic trigger of an hour, some of them have no such trigger. So the first portion of the created jobs run every hour and the other ones must be triggered real manually.

Now the first interesting part: The periodic triggered jobs have no problem with disappearing history. All fine here. But the manually triggered jobs loose their history on the UI at least on the next day. Actually I did not figured out when exactly the history disappears from the UI.

 

And the 2nd interesting part is, that the whole problem disappears after I uninstalled the JobConfigHistoryPlugin! Can anybody verify this? 

julien.lafourcade@gmail.com (JIRA)

unread,
Nov 21, 2018, 4:20:02 AM11/21/18
to jenkinsc...@googlegroups.com

We found out some of the problems where due to security hardening introduced in version 2.107.1. Everything is explained here :

https://jenkins.io/blog/2018/03/15/jep-200-lts/ 

You can find some useful information in the logs in order to know which classes you need to whitelist (although it's not a very good practice ...)

 

yves.schumann@ti8m.ch (JIRA)

unread,
Nov 21, 2018, 4:23:02 AM11/21/18
to jenkinsc...@googlegroups.com
Yves Schumann edited a comment on Bug JENKINS-50595
OK, I digged a little bit deeper into this. 

I setup the same automatic job creation we use on another Jenkins instance using bleeding edge Jenkins release. So I have a job, which creates other Jenkinsfile-based pipeline jobs using job dsl. The created jobs have one difference: Some of them have a periodic trigger of an hour, some of them have no such trigger. So the first portion of the created jobs run every hour and the other ones must be triggered real manually.

Now the first interesting part: The periodic triggered jobs have no problem with disappearing history. All fine here. But the manually triggered jobs loose their history on the UI at least on the next day. Actually I did not figured out when exactly the history disappears from the UI.

  
And the 2nd interesting part is, that the whole _problem disappears after I uninstalled the JobConfigHistoryPlugin_! Can anybody verify this? 

arielman22@gmail.com (JIRA)

unread,
Sep 8, 2019, 7:58:02 AM9/8/19
to jenkinsc...@googlegroups.com
Ariel M commented on Bug JENKINS-50595

Yves Schumann do you think the uninstall of JobConfigHistoryPlugin can help me solve this issue:

https://issues.jenkins-ci.org/browse/JENKINS-59239

arielman22@gmail.com (JIRA)

unread,
Sep 24, 2019, 4:46:02 PM9/24/19
to jenkinsc...@googlegroups.com
Ariel M updated an issue
 
Change By: Ariel M
Comment: [~swf] do you think the uninstall of _JobConfigHistoryPlugin_ can help me solve this issue:

https://issues.jenkins-ci.org/browse/JENKINS-59239
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages