Skip to content

Fetching SPM from private repository when including CodeQL init step #2809

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

Open
einar-notland opened this issue Mar 17, 2025 · 5 comments
Open

Comments

@einar-notland
Copy link

Not sure what causes this. But our Xcode build job just gets stuck at SPM trying to fetch a framework from a private repository when having the CodeQL initialisation step in our workflow.

The SPM fetching works fine for workflows where we do not initialise CodeQL.

The workflow does not fail, it just gets stuck at the place where it is trying to fetch the private repository package. To allow it to fetch this private repo, I use this action to add the credentials: akiojin/store-git-credential-github-action@v1. And this credentials stuff works fine for our normal builds. But in our CodeQL workflow it fails the way I have described, just being stuck at the fetching step.

Anybody have any idea here?

@rvermeulen
Copy link
Contributor

rvermeulen commented Mar 19, 2025

Hi @einar-notland,

Thanks for your question. Is it possible to share the database creation and build tracer logs so we can diagnose what may cause the slowdown?

If this is a private project we may need to find a way to securely share these logs to ensure we do not disclose information.

@einar-notland
Copy link
Author

Yeah, I could also try to just find the part you're interested in and try to anonymise it.

But how do I extract what you are interested in. Currently the logs for the workflow just show the SPM fetching logs, like this:
Fetching from https://github.com/[ORG]/[REPO]

@rvermeulen
Copy link
Contributor

Hi @einar-notland, let me inquire if we can provide you with interesting parts to look for in the logs and get back to you.

@einar-notland
Copy link
Author

@rvermeulen Did you get the time to investigate this? As stated above, our workflow just gets stuck. And the final line in the log is:
Fetching from https://github.com/[ORG]/[REPO]

Then the job just continues to run until it is force-quitted or time-out after 6 hours.

@smowton
Copy link
Contributor

smowton commented Apr 8, 2025

Could you upload the database directory in its partially-created state? If there's confidential information you wouldn't want visible on this public issue tracker, perhaps you could use Google Drive and share to smowton@github.com?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants