-
Notifications
You must be signed in to change notification settings - Fork 67
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
Error Disallowed checkout type, the project must be checked out over one of the supported schemes: SSH #263
Comments
Hi @nextorlg, first of all, great issue report! That's all I need to be helpful here. If so, technically Buildasaur doesn't yet support Github Enterprise servers, but there are a couple of people working on it (and have their forks), see this issue with links: #99. There's even a WIP pull request: #251. Hope this helps. As I don't have an Enterprise server myself, I can't get the support in myself, so I'm relying on contributors. It might be worth to try to chat to them directly. |
Possibly related to #259. |
Yup looks related to the github enterprise instance. Our setup is not standard, I will check the issues as PRs you referenced and see if I can be of some help |
As we don't technically yet support GitHub Enterprise yet, I'll close this. If you're using a fork of Buildasuar, it's probably best to open a ticket in the fork's issues section and later try to ask them to PR the improved version into main Buildasaur. Unfortunately I cannot help with forked code as I don't know what's been changed. |
I got the following error adding a repo:
Although the repo was clone using SSH I followed the workaround steps creating the blueprint file but I still get the same error.
Is it possible to get more detail about what is producing the error?
The blueprint file added looks like (anonymised):
Thanks for your work!
The text was updated successfully, but these errors were encountered: