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

ignore insignificant licence change in baseline-check #1587

Closed

Conversation

fbricon
Copy link
Contributor

@fbricon fbricon commented Oct 30, 2023

Change-Id: I3667aef7789dc8d94c97ee685787c54a0982b8a7
Signed-off-by: Fred Bricon [email protected]

Change-Id: I3667aef7789dc8d94c97ee685787c54a0982b8a7
Signed-off-by: Fred Bricon <[email protected]>
Copy link
Contributor

@mickaelistria mickaelistria left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See #1478 (comment) , I think we should favor other solutions.

@fbricon
Copy link
Contributor Author

fbricon commented Oct 30, 2023

I will not go over dozens of manifests and pom files to fix it

Comment on lines 121 to 122
<ignore>jars/*.jar</ignore>
<ignore>Eclipse-SourceReferences</ignore>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, even those shouldn't be ignored as they're supposed to be stable across rebuilds. And if they're not stable, then they should be made stable.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unfortunately they are not stable since they contain the ID of the commit from which the bundle was build.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If configured correctly, the referenced commit is the last commit that has affected the particular module; which is stable as long as the bundle is not changed.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's a point.
But I likely added this because it failed the build, but if it would work without ignoring that, it would be even better.

@github-actions
Copy link

Test Results

0 tests  ±0   0 ✔️ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ±0 

Results for commit 672ab72. ± Comparison against base commit c6fac93.

@fbricon
Copy link
Contributor Author

fbricon commented Oct 30, 2023

CI ignores the directive anyway. Fuck it.

@fbricon fbricon closed this Oct 30, 2023
@mickaelistria
Copy link
Contributor

The failure is a consequence of 248d8fc / #1579

@mickaelistria
Copy link
Contributor

The proper fix is just to bump bundle version as they now have different content.

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

Successfully merging this pull request may close these issues.

3 participants