Forums : Technical Issue Help
Dear Open Hub Users,
We’re excited to announce that we will be moving the Open Hub Forum to
https://community.blackduck.com/s/black-duck-open-hub.
Beginning immediately, users can head over,
register,
get technical help and discuss issue pertinent to the Open Hub. Registered users can also subscribe to Open Hub announcements here.
On May 1, 2020, we will be freezing https://www.openhub.net/forums and users will not be able to create new discussions. If you have any questions and concerns, please email us at
[email protected]
Unable to add new project
I was unable to add a new project to ohlo.
Apparently the issue has something to do with the git url, it says invalid.
git://github.com/saltstack/salt-bootstrap.git
Is there something specific searched in the repositories which git://github.com/saltstack/salt-bootstrap.git does not have?
Regards.
Pedro,
Continue on to create the project then add the enlistment as a separate step. The initial check presumes that there will be a master
branch and when it finds none it fails. Be sure when you add the enlistment to specify develop
as the branch to enlist. Any further problems, let me know here.
Thanks!
Thanks! It's now added, though a proper error could be more useful :)
Thanks!
Pedro,
I suspect you are right. Sometimes these things are overlooked because you have a mind-set that becomes like the forest which obscures the trees!
Glad your new project came together despite the forest!
Thanks!
I just hit the same problem.
You recommended to continue on
to create the project and enlist the repo later. I can't see a way to do that. The Project Source Code
field is marked as required
and I get an error when trying to submit without the repo information.
So now I seem to be stuck.
Tim.
Your repository needs a master branch
Ok, thanks. Wouldn't it be a better user experience if ohloh would use whatever the default git branch is, at least in the case where there is no master?
Tim,
Click Check Code Location
with a blank field for the repository URL. You will be brought to a page to create the outlines of the project and you can fill in the repository later. The only required fields are Project Name and preferred Ohloh Project URL.
Let me know here how it proceeds. It's possible that git may not have a way to determine the default branch in a repeatable way and communicate it back to the ohloh servers. It's unlikely we would attempt to scrape that info off the web interface - too many variables, I suspect.
Come on ssnow-blackduck, that's a bad excuse.
You either force the user to tell you the branch by typing it, and thus, any missing branch is now user error, or, you try to list all branches, and have the user choose.
The simplest to ohloh would be forcing the user to provide the branch name. You could even pre-set it to what you already choose as the default, 'master'.
Oh, and better error messages please...
Cool? :)
Pedro,
At this point, it's not an excuse, just an observation. I see plenty of user-interface issues here and complain when I do but there's just so much time and I don't want to spend it all complaining...
Cool! :)
Get your code in github and we'll fork to fix it ;)
Hi ssnow.
Re It's possible that git may not have a way to determine the default branch
I think you'll find that all you need to do is stop trying to specifically checkout master
. A plain git clone $repo
will checkout the default branch, which will typically be master
but might be something else. In other words the fix might be to just let git do what it would do by default. (Or, after a 'git clone --bare' or 'git clone --no-checkout', I think a 'git symbolic-ref HEAD' will tell you which branch is the default.)
Re Click
Check Code Locationwith a blank field for the repository URL
- that worked, thanks! The subsequent Add Enlistment page at https://www.ohloh.net/p/devel-sizeme/enlistments/new even offered me a nice field where I could enter the branch name to use! Surely it wouldn't be too hard to add that same field to the https://www.ohloh.net/p/check_forge page.
Thanks again.
Tim.
Pedro,
Done some time ago. See: https://github.com/blackducksw for the code for the source code line counter and the SCM library. There is a great deal that seems arcane about it but on reflection much of it is there for a reason... We need to interface to a whole lot of very different SCM types and reduce them all down to a single coherent system. It isn't trivial.
Tim,
Glad you were able to get the project going. The check_forge page is a new, streamlined way for most users to quickly add their projects efficiently. It certainly doesn't accommodate all situations. We could use a bit of a hint on that page to indicate the older tried-and-true way of entering projects for those who need it. The good thing is, if it works, it fills in a lot of the blanks for you automatically.