Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to 0.7.0 renders some data unreadable #194

Open
Jmennius opened this issue Jun 19, 2020 · 9 comments
Open

Upgrade to 0.7.0 renders some data unreadable #194

Jmennius opened this issue Jun 19, 2020 · 9 comments
Labels
bug ❓ Possibly an ansicolor plugin bug

Comments

@Jmennius
Copy link

After the upgrade of ascicolor to 0.7.0 from 0.6.2 Jenkins complains that some data is unreadable.

Test environment

  • Jenkins Version: 2.205
  • AnsiColor Version: 0.7.0 (upgraded from 0.6.2)
  • Hostsystem: Ubuntu 18.04

Expected behavior

Nothing unusual after the upgrade.

Actual behavior

Jenkins greets with You have data stored in an older format and/or unreadable data.
and the table lists entries with:
CannotResolveClassException: hudson.plugins.ansicolor.ColorizedAction

Steps to reproduce the behavior

Have some jobs run with pre-0.7.0 ansicolor, upgrade to ansicolor 0.7.0 - observe Jenkins complain about "old data".

Apparently this is caused by 96aa4e0 which moved ColorizedAction into another package.

@conf
Copy link

conf commented Jun 22, 2020

This affects me as well.

@tszmytka
Copy link
Collaborator

This is harmless. ColorizedAction now serves a much broader purpose.
You can safely Discard Unreadable Data (on the Manage Old Data page) or Dismiss it altogether.

@rechc
Copy link

rechc commented Jul 6, 2020

How can I fix the problem permanently?

@chasip
Copy link

chasip commented Aug 13, 2020

we have this issure two

@AvnerCohen
Copy link

Too many "Unreadable Data points" have impact on jenkins performance, so having this in degrades jenkins across time.

Anyone has any pointers on how to avoid this altogether ?

@MichaelSp
Copy link

we're running ~100 jenkinse. Clicking Discard Unreadable Data on all of the servers is really painful. Especially if you have to check that there are no other, probably more important warnings in between. I'd love to have a more viable solution. Also considering the performance degradation aspect.

@KostyaSha
Copy link
Member

This is harmless. ColorizedAction now serves a much broader purpose.
You can safely Discard Unreadable Data (on the Manage Old Data page) or Dismiss it altogether.

https://wiki.jenkins.io/display/JENKINS/Hint+on+retaining+backward+compatibility#Hintonretainingbackwardcompatibility-Scenario:renameaclass

@ezequiels
Copy link

This continues to be an issue. The solution proposed is not acceptable. which was: "This is harmless. ColorizedAction now serves a much broader purpose.”

@dblock
Copy link
Member

dblock commented Jun 17, 2022

Let's reopen this. Please contribute a fix.

@dblock dblock reopened this Jun 17, 2022
@dblock dblock added the bug ❓ Possibly an ansicolor plugin bug label Jul 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug ❓ Possibly an ansicolor plugin bug
Projects
None yet
Development

No branches or pull requests

10 participants