chore(jdbc): JDBC presubmit & nightly pipelines

[logachev]

• Adding JDBC to the parent pom.xml
• Excluding JDBC project from integration/graal-vm Kokoro runs
• Add 2 new cloudbuilds: presubmit & nightly
• Update versions.txt to contain jdbc version

Note: for now I also enabled ignoring "used but undeclared dependencies". I'm not sure what's the right path given that those dependencies are entirely due to BQ/BQ-Storage dependencies. Not sure if duplicating the list makes a lot of sense

[gemini-code-assist]

Summary of Changes

Hello @logachev, 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 focuses on a build configuration update to formally include the google-cloud-bigquery-jdbc module within the main project's Maven build structure. This integration is a necessary step to facilitate the setup of presubmit checks for the JDBC module, ensuring its code quality and stability are maintained through automated testing.

Highlights

• Build Configuration Update: The google-cloud-bigquery-jdbc module has been explicitly added to the project's pom.xml as a build module. This change is foundational for enabling presubmit checks and ensuring the module is properly integrated into the continuous integration pipeline.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 integrates the google-cloud-bigquery-jdbc module into the project's build by adding it to the root pom.xml. This change correctly includes the JDBC module in the Maven reactor build, which will ensure it is covered by presubmit checks. The changes are straightforward and appropriate for the stated goal. No issues were found.

[logachev]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces presubmit and nightly build pipelines for the JDBC module, along with necessary adjustments to the build scripts and POM files. The changes are generally well-structured. However, I've identified a configuration issue in the pom.xml for handling undeclared dependencies and a potential syntax error in the build.sh script. Addressing these points will improve the robustness of the new build configurations.