Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update java version doc #256

Merged
merged 1 commit into from
Jul 1, 2024
Merged

Update java version doc #256

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 4 additions & 14 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -243,27 +243,17 @@ jobs:

The configuration above will perform a dry run, meaning it will only print out the Docker command that it would run if `dryRun` were set to `false`, which is the default. Finally, it tells HawkScan to use the `stackhawk.yml` configuration file and overlay the `stackhawk-extra.yml` configuration file on top of it.

## Windows Support
The HawkScan action is also supported on windows! With some nuances:
## Java Requirements for HawkScan
HawkScan 4 and above requires Java 17 through 21. If you are defaulting to latest version of HawkScan, please ensure your Java is set to the correct version on your Github runners.

### Ensure java is up to date
Github's `windows-2022` runners may default to an earlier version of Java 11. As a result, you might see this error when running on Windows:

```
Error: A JNI error has occurred, please check your installation and try again
com/stackhawk/zap/Bootstrap has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
```

To address this, Java on Hosted Windows Runners can be easily setup in a prior workflow step to instead use a later java version:
To address this, Java on Hosted Runners can be easily setup in a prior workflow step to instead use the correct Java version:
```yaml
- uses: actions/setup-java@v3
- uses: actions/setup-java@v4
with:
distribution: 'temurin'
java-version: '17'
```

Due to the nature of powershell and how we call java, this defect may not fail a build, and can pass silently.

## Need Help?

If you have questions or need some help, please email us at support@stackhawk.com.
Loading