circleci-cli: circleci config validate fails for project on GitHub Enterprise and CircleCI server

Meta:

CircleCI CLI Version: 0.1.24783+93e3e61 (homebrew)

Operating System: macOS Ventura 13.2.1

CircleCI CLI Diagnostic:


---
CircleCI CLI Diagnostics
---
Debugger mode: false
Config found: --redacted--
API host: --redacted, but correctly points to my GitHub Enterprise server --
API endpoint: graphql-unstable
OK, got a token.
Trying an introspection query on API... 
Ok.
Hello, Rieger, Joe.

Current behavior:

When running the CLI locally for CircleCI server and GitHub Enterprise as the location for the project, I receive the following:

circleci config validate produces the following output:

Validating config with following values
        id:     00000000-0000-0000-0000-000000000001    number: 1       project.git_url:        https://github.com/CircleCI-Public/circleci-cli project.type:   github  git.tag:                git.branch:     main    git.revision:  --redacted-- git.base_revision:      --redacted-- Error: Not Found

Expected behavior:

The CLI should respect and acknowledge that projects can live places other than public GitHub

When did this begin / Was this previously working?:

Began when I ran a brew update today for CircleCI CLI

Additional Information:

About this issue

Original URL
State: closed
Created a year ago
Comments: 20 (9 by maintainers)

Most upvoted comments

@jmrieger - the latest release should make it explicitly obvious that this is the underlying reason for config compilation and validation issues now.

I’m going to take a look into improving the documentation to show how folks can install older versions (not specific to brew) which should hopefully help other folks in your situation.

Are you happy for me to close this issue for now though?

@elliotforbes Absolutely. I appreciate the extra inches in the CLI being more verbose about the underlying errors.

jmrieger on Apr 1, 2023

I’ve been unable to replicate this issue in any of my tests unfortunately. Instead, I’ve taken a look at cleaning up the architecture of the code base and improving the error handling to be more explicit here - #884

It still needs to go through review process, but if you’d like to try make build and testing this out, it could really help with the investigations!

Trying now; will update with any findings.

jmrieger on Mar 23, 2023

I’ve been unable to replicate this issue in any of my tests unfortunately. Instead, I’ve taken a look at cleaning up the architecture of the code base and improving the error handling to be more explicit here - https://github.com/CircleCI-Public/circleci-cli/pull/884

It still needs to go through review process, but if you’d like to try make build and testing this out, it could really help with the investigations!

elliotforbes on Mar 23, 2023

I’ll likely have to take you up on that offer! Leave it with me for now and I’ll dig into our o11y tools tomorrow during my day and see if I can sniff out the underlying reason this appears to have regressed.

elliotforbes on Mar 22, 2023