You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Include a field to add custom properties to FOSSA analysis. Some users are dealing with custom builds which require custom properties to be passed to the invocation.
@NielsDoucet provided a use case where a custom gradle wrapper is used where custom system properties are passed (e.g. ./gradlew -Dany.system.prop=value)
jobs:
fossa-scan:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2
- uses: fossas/fossa-action@main # Use a specific version if locking is preferred
with:
api-key: ${{secrets.fossaApiKey}}
- gradle:
- system-properties:
sys.prop1: value1
sys.prop2: value2
- properties:
prop1: value1
prop2: value2
The text was updated successfully, but these errors were encountered:
I did some further digging into the issue and I'm now convinced this can't be solved exclusively at the GitHub action level. This requires the fossa cli tool to adapt how it invokes gradle. This issue should probably be moved to the fossa-cli tool repository.
Include a field to add custom properties to FOSSA analysis. Some users are dealing with custom builds which require custom properties to be passed to the invocation.
@NielsDoucet provided a use case where a custom gradle wrapper is used where custom system properties are passed (e.g.
./gradlew -Dany.system.prop=value
)The text was updated successfully, but these errors were encountered: