frogbot
frogbot copied to clipboard
Does Frogbot support GHES
Does Frogbot support Github Enterprise Server? It is not clear from the documentation and when I tried it (using the JF_GIT_API_ENDPOINT) , I got the following error:
Frogbot /opt/hostedtoolcache/frogbot/[RELEASE]/x64/frogbot scan-repository 14:56:24 [Info] Frogbot version: 2.19.2 Error: 4 [Error] expected 200 status code while received 406 status code with error: GET https://<OUR GHES INSTANCE>/login?return_to=https%3A%2F%2F<OUR GHES INSTANCE>%2Frepos%2FCICD-Infra%2Ftemp-call-xray-lib-wkfls%2Fcontents%2F.frogbot%3Fref%3Dmain: 406 [] Error: The process '/opt/hostedtoolcache/frogbot/[RELEASE]/x64/frogbot' failed with exit code 1
@esmaila, Frogbot supports all flavors of GitHub (Enterprise / Cloud / Self-hosted). We will improve the documentation to clarify this. Will you be able to enable debug logging by adding the JFROG_CLI_LOG_LEVEL variable to your workflow with DEBUG as its value, and then sharing the complete log file with us here?
Frogbot /opt/hostedtoolcache/frogbot/[RELEASE]/x64/frogbot scan-repository 09:55:34 [Info] Frogbot version: 2.19.2 09:55:34 [Debug] Reading config from file system. Looking for .frogbot/frogbot-config.yml 09:55:34 [Debug] frogbot-config.yml wasn't found in /runner/_work/temp-call-xray-lib-wkfls/temp-call-xray-lib-wkfls/.frogbot/frogbot-config.yml. Searching for it in upstream directories 09:55:34 [Debug] Attempting to download frogbot-config.yml from CICD-Infra/temp-call-xray-lib-wkfls 09:55:34 [Debug] The frogbot-config.yml will be downloaded from main branch Error: 4 [Error] expected 200 status code while received 406 status code with error: GET https://<GHES-Server>/login?return_to=https%3A%2F%2F<GHES-Server>%2Frepos%2FCICD-Infra%2Ftemp-call-xray-lib-wkfls%2Fcontents%2F.frogbot%3Fref%3Dmain: 406 [] Error: The process '/opt/hostedtoolcache/frogbot/[RELEASE]/x64/frogbot' failed with exit code 1
I have a package.json at the root level and therefore frogbot-config.yml shouldn't be required? It is an npm project
Hey @esmaila, Frogbot usually tries to grab the frogbot-config.yml file from your repository to read its settings, but it's not mandatory, as Frogbot can operate using a configuration based on environment variables. The issue with the failing REST API suggests a possible omission in your configuration, likely related to the endpoint, such as the absence of the /api/v3
suffix. Typically, the endpoint for the GitHub enterprise server appears in this format: http(s)://HOSTNAME/api/v3
. Could it be that you're missing the /api/v3
suffix?