183 create a build script and optional sca scan script for fis gui #4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request introduces two new GitHub Actions workflows to the repository, aimed at automating the build and security scanning processes for the File Integrity GUI project. These workflows help ensure that builds are reproducible and that security vulnerabilities are detected early in the development cycle.
CI/CD Automation:
build.ymlworkflow to automatically build the FIS-GUI project on every push and pull request to themasteranddevelopbranches using Java 21 and Maven. (.github/workflows/build.yml, .github/workflows/build.ymlR1-R23)Security Automation:
snyk-scan.ymlworkflow to run a Snyk Software Composition Analysis (SCA) scan for vulnerabilities on the File Integrity GUI, triggered on pushes and pull requests to themasterbranch as well as manually. (.github/workflows/snyk-scan.yml, .github/workflows/snyk-scan.ymlR1-R17)