Skip to content

[TESTING ONLY] Testing common changes required for duplicate artifactId #45181

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

Draft
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

JimSuplizio
Copy link
Member

I'm testing changes to API review creation. These changes will pass a list of PackageInfo files instead of a list of Artifact.Names. This allows passing around the PackageInfo object instead random pieces of data. Passing around the PackageInfo object also allows the FindArtifactForApiReviewFnV2 to correctly, and easily, find the sources jar since the PackageInfo file contains the Group. This eliminates the janky code that had to exist in the original FindArtifactForApiReviewFn which had to play a guessing game with the group to get correct path to the sources.jar

The other changes are to update the detect-api-changes, updating to use the FindArtifactForApiReviewFnV2 instead of the FindArtifactForApiReviewFn also, in some cases, pass the PackageInfo file to functions so we're not loading the same PackageInfo multiple times.

Testing changes to this, at least for create-apireview.yml, requires a pipeline to be manually kicked off against the refs/merge of this PR to test yml path for PackageInfo files and the new script.

@JimSuplizio JimSuplizio added the Central-EngSys This issue is owned by the Engineering System team. label May 1, 2025
@JimSuplizio JimSuplizio self-assigned this May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Central-EngSys This issue is owned by the Engineering System team.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant