ci(container-registry): skip tests

[glasnt]

Description

Addresses #10180

Unblocks #10129

Checklist

• I have followed Sample Format Guide
• pom.xml parent set to latest shared-configuration
• Appropriate changes to README are included in PR
• These samples need a new API enabled in testing projects to pass (let us know which ones)
• These samples need a new/updated env vars in testing projects set to pass (let us know which ones)
• Tests pass: mvn clean verify required
• Lint passes: mvn -P lint checkstyle:check required
• Static Analysis: mvn -P lint clean compile pmd:cpd-check spotbugs:check advisory only
• This sample adds a new sample directory, and I updated the CODEOWNERS file with the codeowners for this sample
• This sample adds a new Product API, and I updated the Blunderbuss issue/PR auto-assigner with the codeowners for this sample
• Please merge this PR for me once it is approved

[gemini-code-assist]

Summary of Changes

Hello @glasnt, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request implements a temporary measure to skip several integration tests in the container-analysis module. The primary purpose is to mitigate an existing issue that causes these tests to fail, thereby unblocking progress on another dependent pull request. This allows the continuous integration pipeline to proceed without being halted by these specific test failures, while the root cause of the underlying problem is being investigated.

Highlights

• Test Skipping: Multiple tests within SamplesTest.java in the container-registry/container-analysis module have been temporarily disabled using the @Ignore annotation.
• Issue Resolution: This change directly addresses issue container-registry: API deprecation #10180, which likely indicates a problem preventing these tests from passing reliably.
• PR Unblocking: The skipping of these tests is intended to unblock pull request fix(deps): update java #10129, suggesting a dependency or conflict that needed to be resolved.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request disables all tests in SamplesTest.java by adding @Ignore annotations to each test method, referencing an issue. While this achieves the goal, a more maintainable approach would be to use a single @Ignore annotation at the class level, since all tests are being skipped for the same reason. My review includes suggestions to remove the individual annotations from each method to facilitate this refactoring. This will make the code cleaner and easier to manage when the tests are eventually re-enabled.

[gemini-code-assist]

Since all tests in this class are being ignored for the same reason, it would be cleaner to add a single @Ignore annotation to the SamplesTest class instead of annotating each test method individually. This would make the code more concise and easier to maintain when the tests are re-enabled. Please remove this annotation and add @Ignore("https://github.com/GoogleCloudPlatform/java-docs-samples/issues/10180") to the SamplesTest class.

[gemini-code-assist]

As per the suggestion on testCreateNote, a single class-level @Ignore annotation should be used. Please remove this redundant method-level annotation.

[gemini-code-assist]

As per the suggestion on testCreateNote, a single class-level @Ignore annotation should be used. Please remove this redundant method-level annotation.

[gemini-code-assist]

As per the suggestion on testCreateNote, a single class-level @Ignore annotation should be used. Please remove this redundant method-level annotation.

[gemini-code-assist]

As per the suggestion on testCreateNote, a single class-level @Ignore annotation should be used. Please remove this redundant method-level annotation.

[gemini-code-assist]

As per the suggestion on testCreateNote, a single class-level @Ignore annotation should be used. Please remove this redundant method-level annotation.

[gemini-code-assist]

As per the suggestion on testCreateNote, a single class-level @Ignore annotation should be used. Please remove this redundant method-level annotation.

[gemini-code-assist]

As per the suggestion on testCreateNote, a single class-level @Ignore annotation should be used. Please remove this redundant method-level annotation.

[gemini-code-assist]

As per the suggestion on testCreateNote, a single class-level @Ignore annotation should be used. Please remove this redundant method-level annotation.

[gemini-code-assist]

As per the suggestion on testCreateNote, a single class-level @Ignore annotation should be used. Please remove this redundant method-level annotation.

[iennae]

@glasnt gave feedback that based on the per test is easier versus at the class layer since removing the tests individually may be the future plan. going ahead and approving based on goal of unblocking tests as a whole.