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

Jenkins ECJ plugin detects way too less warnings #1169

Closed
jukzi opened this issue Feb 5, 2024 · 2 comments
Closed

Jenkins ECJ plugin detects way too less warnings #1169

jukzi opened this issue Feb 5, 2024 · 2 comments

Comments

@jukzi
Copy link
Contributor

jukzi commented Feb 5, 2024

My workspace shows 962 warnings for JDT.UI repo, but jenkins only shows two
https://ci.eclipse.org/jdt/job/eclipse.jdt.ui-Github/job/master/2/eclipse/
image
image

@laeubi any idea?

@laeubi
Copy link
Contributor

laeubi commented Feb 5, 2024

One thing I ave noticed in the past is that if one has some project specific preference and then there is a new preference key (not mentioned in the existing one) then it always uses the workspace default (what can differ).

So to analyze this one needs a reference to one project and one file there where a warning as shown that is configured in that project preference and is not shown at Jenkins.

To prove this one then could for example change it from warning > error in this project to see that it is actually picked up (e.g. fails the build).

@jukzi
Copy link
Contributor Author

jukzi commented Feb 5, 2024

with eclipse-platform/eclipse.platform.releng.aggregator#1774
https://ci.eclipse.org/jdt/job/eclipse.jdt.ui-Github/job/master/5/ failed due to quality gate :
image

and 688 warnings are much more but still not exactly all i see in workspace:
image

jukzi pushed a commit to jukzi/eclipse.jdt.ui that referenced this issue Feb 5, 2024
jukzi pushed a commit that referenced this issue Feb 5, 2024
@jukzi jukzi closed this as completed Feb 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants