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
We are using Running GitHub enterprise in an air gapped environment. We have sync'd the synopsys-action into our environment and downloaded the bridge executable to the runner. When the SYNOPSYS_BRIDGE_PATH variable is set, the action still seems to attempt to download the executable from the synopsis
ok, I made some testing and I noticed that you have to give the Bridge version as well, otherwise it will check that do you have the latest version. So, you have to give these:
We are using Running GitHub enterprise in an air gapped environment. We have sync'd the synopsys-action into our environment and downloaded the bridge executable to the runner. When the SYNOPSYS_BRIDGE_PATH variable is set, the action still seems to attempt to download the executable from the synopsis
Runner OS - Windows 2019 Data Center Edition
Bridge Version Downloaded: https://sig-repo.synopsys.com/artifactory/bds-integrations-release/com/synopsys/integration/synopsys-action/0.1.192/
Path and Directory for the bridge:
Directory: C:\apps\blackduck-bridge
Mode LastWriteTime Length Name
d----- 4/25/2023 6:58 PM extensions
-a---- 4/25/2023 6:58 PM 8537 LICENSE.txt
-a---- 4/25/2023 6:58 PM 4078048 synopsys-bridge.exe
-a---- 4/25/2023 6:58 PM 4078048 bridge.exe
-a---- 4/25/2023 6:58 PM 515 versions.txt
GitHub Workflow File:
name: Hello World - Testing Black Duck
on:
jobs:
test_black_duck_windows_2019:
runs-on: App-Factory-Win-2019
Error Message:
Run vendor-actions/synopsys-action@v1.1.0
with:
coverity_project_name: ***
blackduck_apiToken: ***
blackduck_url: ***
SYNOPSYS_BRIDGE_PATH: C:\apps\blackduck-bridge
blackduck_scan_full: true
blackduck_scan_failure_severities: ALL
Synopsys Action started...
Checking for latest version of Bridge to download and configure
Error: Workflow failed! read ECONNRESET
The text was updated successfully, but these errors were encountered: