-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add GitHub Enterprise Server support #42
Comments
@advanced-security/advanced-security-dependency-graph Can you have a look? |
@jhutchings1 afaict the dependency graph team has never contributed to this project but i've asked FR to take a look |
Getting the same error: |
I opened #67 to fix this. Need to get it reviewed and merged. |
@jhutchings1 Thank you for your prompt response! Will test it once its merged. |
@jhutchings1, any updates on the GHE support, Apologies for being persistent but this is quite urgent. |
Still waiting on the PR to be approved and merged. I'm the interim, you're welcome to use it by referencing tht action with @ghes-fix as the version. Let me know if that works for you. |
I tested it with @ghes-fix:
Pls find my script below, I am still manually downloading the binary:
Am I missing something here? |
@nihalraghuraj-assent Interesting. I didn't see that error on my test instance. I'll spin up a new instance and have a look. Your workaround is a good one, though, and definitely something folks should look at to unblock themselves in the interim. |
FYI, I am currently blocked on validating additional changes here while I figure out an issue with my GHES test instance. I should be able to loop back in the coming days. |
Any updates on the issue @jhutchings1 ? |
I'm blocked on a gnarly testing environment issue. Suggest following the
workaround above. That's long term supportable and mirrors what I'm trying
to do in the action itself
|
@jhutchings1 even with this workaround, I get the errors as mentioned here: Error-http Any advice on how to get around this? |
The workaround was still listing the @ghes-fix step, so my guess is that it was failing in the same place. Does it work if you do this? If not, can you provide more details about where specifically you're seeing that error? I assumed it was in the new code that tries to connect to download the component-detection binary. |
I did try the same workaround pointing to
Let me know if you need further information. |
@nihalraghuraj-assent Thanks for sharing the detailed logs. You're actually failing much further down than I expected. That error is getting thrown when submitting the snapshot. Can you confirm that the dependency graph is enabled in your server and on the repository you're running this against? |
@jhutchings1 I can confirm that dependency graph is enabled both in repository and the server as well |
@nihalraghuraj-assent Can you also confirm your version of GHES? I do not have a repro of what's happening on my end, so I'm kind of guessing at causes for why that API call isn't working when it submits the snapshot. We may need to have you escalate with GitHub Support to get a better idea of what's happening. |
GitHub Enterprise Server |
Ok, 3.13.3 should work appropriately. I think my test environment issue should be fixed in the next day or so, but I'll keep you posted when I'm able to have another look. |
Sure, thank you for your prompt response! |
@nihalraghuraj-assent Can you actually proactively open a support ticket for this one? I'm leaving GitHub for a new opportunity next week, and I don't want to see the ball drop if I run out of time, particularly since I won't have a GHES instance to help you out once my access is cut. You can mention that I asked you to do so, and that should get it escalated to the team very quickly. |
@jhutchings1 do you want me to open a github support ticket? |
Yes please |
The Action uses Octokit to download
microsoft/component-detection
but does not specify that it should be fromgithub.com
. This means use on GitHub Enterprise Server leads to trying to resolve that org/repo on the local server, which fails with a 404.You can work around this by manually downloading the appropriate release binary in the Actions workflow before running this Action, e.g. with
wget
.It then attempts to submit using the Dependency Submission Toolkit. I haven't worked out precisely why, but this fails with a
Cannot read properties of null (reading 'toString')
error in the toolkit.The text was updated successfully, but these errors were encountered: