FortifyToolsInstaller

Introduction

Build secure software fast with Fortify. Fortify offers end-to-end application security solutions with the flexibility of testing on-premises and on-demand to scale and cover the entire software development lifecycle. With Fortify, find security issues early and fix at the speed of DevOps.

The FortifyToolsInstaller.sh script in this repository allows for easily installing and optionally running various Fortify tools commonly used in CI/CD pipelines, like ScanCentral Client, FoD Uploader, and FortifyVulnerabilityExporter. See USAGE.txt for detailed instructions.

Requirements

The FortifyToolsInstaller.sh script is designed to use as little external tools as possible, allowing it to run on most systems and containers that provide the bash shell. The script uses the following external software:

• bash: Required to run the script
• curl or wget: Required to download tool installation bundles; the script will automatically select one of these tools based on availability
• sha256sum: Required to check integrity of downloaded installation bundles
• unzip: Required for most tool installations to extract tool installation bundles
• chmod: Optional but highly recommended to update script executable permissions
• mktemp: Optional, used to generate temporary filenames for download bundles

Developers

Update USAGE.txt

After making any user-facing changes to the script, make sure to run the following command to update usage documentation:

./FortifyToolsInstaller.sh -h 2> USAGE.txt

Conventional commits & versioning

Versioning is handled automatically by release-please-action based on Conventional Commits. Every commit to the main branch should follow the Conventional Commits convention, for example:

• fix: Some fix (#2)
• feat: New feature (#3)
• feat!: Some breaking new feature
• docs: Some documentation change

release-please-action invoked from the GitHub CI workflow generates pull requests containing updated CHANGELOG.md and version.txt files based on these commit messages. Merging the pull request will result in a new release version being published. Make sure to do a git pull after a release has been published to have your local and remote repositories in sync.

License

See LICENSE.TXT