Click on the gear icon in the JFrog tab to access the extension settings.
By default, paths containing .git
, test
, venv
, and node_modules
are excluded from Xray scans. You can modify the exclusion patterns in the Extension Settings.
If your JFrog environment is behind an HTTP/S proxy:
- Navigate to Preferences → Settings → Application → Proxy.
- Set the proxy URL under Proxy.
- Ensure 'Proxy Support' is set to override or on. Alternatively, use the
HTTP_PROXY
andHTTPS_PROXY
environment variables.
If your proxy server requires credentials:
-
Follow the proxy configuration steps above.
-
Encode your credentials in Base64 format:
[Username]:[Password]
. -
In settings.json, add:
"http.proxyAuthorization": "Basic [Encoded credentials]"
-
For access token authorization, use:
"http.proxyAuthorization": "Bearer [Access token]"
If your machine lacks access to https://releases.jfrog.io
, configure Artifactory to act as a proxy:
- Log in to the JFrog Platform UI as an admin.
- Create a Remote Repository with these settings:
- Basic Tab:
- Package Type: Generic
- Repository Key: jfrog-releases-repository
- URL: https://releases.jfrog.io
- Advanced Tab:
- Uncheck Store Artifacts Locally.
This reduces storage.
- Uncheck Store Artifacts Locally.
- Basic Tab:
- In the JFrog VS Code Extension Settings, enter the repository key you created.
- Alternatively, set the
JFROG_IDE_RELEASES_REPO
environment variable with the repository key.
You can configure JFrog VS Code Extension to enforce security policies set in Xray:
- Create a JFrog Project or obtain an existing project key.
- Create a Policy in JFrog Xray.
- Create a Watch in Xray and assign your policy and project to it.
- Configure the project key in Extension Settings.
- Create one or more Watches in Xray.
- Configure the Watches in Extension Settings.
Adjust the log level to debug
, info
, warn
, or err
in the Extension Settings to diagnose issues effectively.