java-application-build-verification
Summary
Verify that a Java application's automated build workflow (GitHub Actions CI/CD) successfully compiles, produces valid artifacts, and passes integrity checks. This skill validates that development builds are reproducible and deployable without fatal compilation errors.
When to use
When you need to confirm that a Java project's GitHub Actions workflow (e.g., 'dev_build_release.yml') has completed successfully and generated usable build artifacts; typically after code is pushed to a development or release branch, or when assessing the health of a project's CI/CD pipeline.
When NOT to use
- The workflow definition itself is malformed or missing; focus first on fixing the .yml file syntax and structure.
- The repository lacks GitHub Actions configured or the workflow file does not exist in .github/workflows.
- Your goal is to modify the Java source code or dependencies; this skill only verifies the build output, not code quality or functionality.
Inputs
- GitHub repository URL (e.g., github.com/mzmine/mzmine)
- Target branch name (e.g., 'dev', 'main')
- GitHub Actions workflow file path (e.g., .github/workflows/dev_build_release.yml)
Outputs
- Workflow execution status (success/failure)
- Build log with compilation step details
- Build artifacts (JAR, application bundles, installer packages)
- Artifact integrity validation result (checksum, file size, content inspection)
How to apply
Access the GitHub Actions workflow file in the .github/workflows directory of the target repository (e.g., mzmine/mzmine). Trigger the workflow via the GitHub Actions web interface or API, targeting the desired branch (e.g., 'dev' or 'main'). Poll the GitHub Actions API or web interface to monitor execution status until completion. Retrieve and inspect the workflow run log to verify that all Java compilation steps completed without fatal errors. Confirm that build artifacts (compiled JAR files, application bundles, or installer packages) were generated and are available for download from the workflow run details. Validate artifact integrity by checking file size, computing checksums, or attempting to extract and inspect the contents of generated files.
Related tools
- GitHub Actions (CI/CD platform that executes the automated build workflow and hosts build artifacts) — https://github.com/mzmine/mzmine
- JDK 25 (Java Development Kit used by the build process to compile Java source code)
- JavaFX 24 (Graphics library dependency required for compilation of GUI components in mzmine)
- mzmine (Target Java application subject to build verification) — https://github.com/mzmine/mzmine
Evaluation signals
- Workflow badge status is green/passing (linked from README badge)
- Build log contains no fatal compilation errors, only successful step outputs
- Artifact file exists and has a non-zero size consistent with expected application bundles
- Artifact checksum matches expected value or artifact can be extracted/inspected without corruption
- Build completion timestamp is recent and matches the intentional trigger time
Limitations
- Workflow execution time may be long; monitor via GitHub API polling or web interface rather than blocking.
- Artifacts are typically retained for only 90 days by GitHub; older workflow runs may not have downloadable artifacts.
- Build success does not imply functional correctness or runtime behavior; it only confirms compilation and packaging completed.
- Repository must have GitHub Actions enabled and the workflow YAML must be syntactically valid; misconfigured workflows will fail before generating artifacts.
Evidence
- [other] The mzmine repository includes a Development Build Release GitHub Actions workflow (dev_build_release.yml) accessible via badge link, indicating CI/CD automation is configured for the project.: "Development Build Release GitHub Actions workflow (dev_build_release.yml) accessible via badge link, indicating CI/CD automation is configured"
- [other] Trigger the workflow via GitHub Actions API or web interface with the desired branch (e.g., 'dev' or 'main'). Monitor the workflow execution until completion, polling the GitHub Actions API for status updates. Retrieve the build log and verify that all compilation steps completed without fatal errors. Confirm that build artifacts (compiled JAR, application bundles, or installer packages) were generated and are available for download from the workflow run. Validate artifact integrity by checking file size, checksum, or attempting to extract/inspect contents.: "Trigger the workflow via GitHub Actions API or web interface with the desired branch (e.g., 'dev' or 'main'). Monitor the workflow execution until completion, polling the GitHub Actions API for"
- [readme] mzmine should work on Windows, macOS, and Linux using either the installers or the portable versions. There are NO further requirements as mzmine packages a specific Java Virtual Machine.: "mzmine packages a specific Java Virtual Machine. This means the local Java installation has no impact on mzmine."
- [readme] mzmine development requires Java Development Kit (JDK) version 23 or newer: "mzmine development requires Java Development Kit (JDK) version 23 or newer"
1---2name: java-application-build-verification3description: Use when when you need to confirm that a Java project's GitHub Actions workflow (e.g., 'dev_build_release.yml') has completed successfully and generated usable build artifacts;4license: CC-BY-4.05---67# java-application-build-verification89## Summary1011Verify that a Java application's automated build workflow (GitHub Actions CI/CD) successfully compiles, produces valid artifacts, and passes integrity checks. This skill validates that development builds are reproducible and deployable without fatal compilation errors.1213## When to use1415When you need to confirm that a Java project's GitHub Actions workflow (e.g., 'dev_build_release.yml') has completed successfully and generated usable build artifacts; typically after code is pushed to a development or release branch, or when assessing the health of a project's CI/CD pipeline.1617## When NOT to use1819- The workflow definition itself is malformed or missing; focus first on fixing the .yml file syntax and structure.20- The repository lacks GitHub Actions configured or the workflow file does not exist in .github/workflows.21- Your goal is to modify the Java source code or dependencies; this skill only verifies the build output, not code quality or functionality.2223## Inputs2425- GitHub repository URL (e.g., github.com/mzmine/mzmine)26- Target branch name (e.g., 'dev', 'main')27- GitHub Actions workflow file path (e.g., .github/workflows/dev_build_release.yml)2829## Outputs3031- Workflow execution status (success/failure)32- Build log with compilation step details33- Build artifacts (JAR, application bundles, installer packages)34- Artifact integrity validation result (checksum, file size, content inspection)3536## How to apply3738Access the GitHub Actions workflow file in the .github/workflows directory of the target repository (e.g., mzmine/mzmine). Trigger the workflow via the GitHub Actions web interface or API, targeting the desired branch (e.g., 'dev' or 'main'). Poll the GitHub Actions API or web interface to monitor execution status until completion. Retrieve and inspect the workflow run log to verify that all Java compilation steps completed without fatal errors. Confirm that build artifacts (compiled JAR files, application bundles, or installer packages) were generated and are available for download from the workflow run details. Validate artifact integrity by checking file size, computing checksums, or attempting to extract and inspect the contents of generated files.3940## Related tools4142- **GitHub Actions** (CI/CD platform that executes the automated build workflow and hosts build artifacts) — https://github.com/mzmine/mzmine43- **JDK 25** (Java Development Kit used by the build process to compile Java source code)44- **JavaFX 24** (Graphics library dependency required for compilation of GUI components in mzmine)45- **mzmine** (Target Java application subject to build verification) — https://github.com/mzmine/mzmine4647## Evaluation signals4849- Workflow badge status is green/passing (linked from README badge)50- Build log contains no fatal compilation errors, only successful step outputs51- Artifact file exists and has a non-zero size consistent with expected application bundles52- Artifact checksum matches expected value or artifact can be extracted/inspected without corruption53- Build completion timestamp is recent and matches the intentional trigger time5455## Limitations5657- Workflow execution time may be long; monitor via GitHub API polling or web interface rather than blocking.58- Artifacts are typically retained for only 90 days by GitHub; older workflow runs may not have downloadable artifacts.59- Build success does not imply functional correctness or runtime behavior; it only confirms compilation and packaging completed.60- Repository must have GitHub Actions enabled and the workflow YAML must be syntactically valid; misconfigured workflows will fail before generating artifacts.6162## Evidence6364- [other] The mzmine repository includes a Development Build Release GitHub Actions workflow (dev_build_release.yml) accessible via badge link, indicating CI/CD automation is configured for the project.: "Development Build Release GitHub Actions workflow (dev_build_release.yml) accessible via badge link, indicating CI/CD automation is configured"65- [other] Trigger the workflow via GitHub Actions API or web interface with the desired branch (e.g., 'dev' or 'main'). Monitor the workflow execution until completion, polling the GitHub Actions API for status updates. Retrieve the build log and verify that all compilation steps completed without fatal errors. Confirm that build artifacts (compiled JAR, application bundles, or installer packages) were generated and are available for download from the workflow run. Validate artifact integrity by checking file size, checksum, or attempting to extract/inspect contents.: "Trigger the workflow via GitHub Actions API or web interface with the desired branch (e.g., 'dev' or 'main'). Monitor the workflow execution until completion, polling the GitHub Actions API for"66- [readme] mzmine should work on Windows, macOS, and Linux using either the installers or the portable versions. There are NO further requirements as mzmine packages a specific Java Virtual Machine.: "mzmine packages a specific Java Virtual Machine. This means the local Java installation has no impact on mzmine."67- [readme] mzmine development requires Java Development Kit (JDK) version 23 or newer: "mzmine development requires Java Development Kit (JDK) version 23 or newer"
HolobiomicsLab