[github] WIP: Add sinttest-openfire workflow

[Flowdalic]

No description provided.

[gemini-code-assist]

Hello @Flowdalic, 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!

Summary of Changes

This pull request introduces a new GitHub Actions workflow named sinttest-openfire.yml. This workflow is designed to run Smack's integration tests against Openfire. It sets up a CI environment with Docker, Java (versions 17 and 21), and Android SDK, and then executes the integration tests within a Docker container.

Highlights

• Workflow Setup: The workflow is triggered on push, pull requests, and merge group events.
• Environment Configuration: It uses Ubuntu 24.04, configures Docker with necessary privileges and shared memory, and sets up Java versions 17 and 21.
• Caching: The workflow caches Maven, Gradle, and Android SDK to speed up subsequent runs.
• Dependencies: It installs GraphViz, Android SDK Manager, and Docker, and prepares the Android SDK environment.
• Integration Tests: The workflow runs a Docker container with Openfire to execute Smack's integration tests.

Changelog

• .github/workflows/sinttest-openfire.yml
  • Added a new workflow file to define the CI pipeline for Smack integration tests against Openfire.
  • Configured the workflow to run on push, pull requests, and merge group events.
  • Specified the job to run on Ubuntu 24.04 with Docker service.
  • Defined a matrix strategy to test with Java 17 and 21.
  • Configured steps to checkout code, set up JDK, cache Maven, Gradle, and Android SDK.
  • Installed GraphViz, Android SDK Manager, and Android SDK.
  • Installed and tested Docker.
  • Added a step to run a Docker container with Openfire.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 is currently in preview and 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 to provide feedback.

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.

---

Trivia time!

What is the primary use case for YAML (YAML Ain't Markup Language)?

Click here for the answer

YAML is commonly used for configuration files and in applications where data is being stored or transmitted. It emphasizes human readability and is often used in situations where people will be reading or writing the data.

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

The pull request introduces a new GitHub Actions workflow to run Smack's integration tests against Openfire. The workflow sets up the necessary environment, including Java, Docker, and Android SDK, and then executes the tests. Overall, the workflow seems well-structured, but there are a few areas that could be improved for clarity and efficiency.

Summary of Findings

Merge Readiness

The workflow appears to be a good starting point for running Smack's integration tests against Openfire. However, before merging, consider clarifying the purpose of the final step (line 80) and ensuring that all dependencies are correctly installed and configured. I am unable to directly approve this pull request, and recommend that others review and approve this code before merging.