JFrog CLI: Two GitHub Actions Troubleshooting Tips
JFrog CLI: Two GitHub Actions Troubleshooting TipsTip 1: Getting Better Error MessagesIf you're setting up a GitHub Actions build for the first time, you may run across unhelpful errors blocking the build from starting, such as a "Unexpected token < in JSON" error when configuring the OIDC:
This error usually means that rather than a JSON "{" character, an HTML page (Using a "<" in "<html>") was returned instead. More information on this error would help you diagnose the cause of the issue and resolve it.
To print the full error and not just the first character, copy over a debugging "workflow.yml" found on the JFrog Project Examples GitHub. You can create a separate workflow in your project by creating a new file in your GitHub repository's "workflows" folder:
This will create a separate "JFrog CLI Example" job using the configuration in the simpleWorkflow.yml. When you run this other job, the CLI will print the full error HTML page you're getting in the other build:
It looks like the JFrog URL the project is using is behind an Nginx IP block .
Tip 2: Try a Local RunnerGitHub Actions run by default from a public IP address, and a lot of corporate networks do not allow external IPs to access internal resources.
To get around this issue, you can install a Local Runner. The steps are documented in the GitHub wiki, you can find the installer for the Local Runner in your GitHub project's Settings menu:
To switch to using the Local Runner, modify your build code to specify the preference:
jobs: build: runs-on: self-hosted
When the Action runs, it will send the job to the Local Runner to execute in the private corporate network: