I have a website that is created using Drupal. I installed and enabled all Project modules including: Project, Project Dependencies, Project package, and Project releases. I also installed and enabled all Version Control modules including: Git backend, Version Control / Project Node integration, Version Control / Release node integration, Version Control API, and Version Control Git / Project.

The problem is that when I create a new project, in the Version control tab for the created project I get the message:
"
No Repository is Available Yet

Go make a cup of tea. The repository should be ready before you get back.

Reload the page to try again.

If this message persists longer than 5 minutes, file an issue in the Git component of the Drupal.org Infrastructure queue. Important: Include a link to the project."

I have been waiting more than a day and the message did not change yet. Do you have any idea why the repository is not created by Git Version control, and how to solve this problem?
In case the repository was created, in which directory is it located (where can I find the repository)? or how can I know that it was already created?

A link to my project is:
http://www.cs.colostate.edu/remodd/vc-test/node/11

Thank you,

Comments

mohammedrefai created an issue. See original summary.

marvil07’s picture

marvil07 CreditAttribution: marvil07 as a volunteer commented
Category: Support request » Feature request
Priority: Critical » Major
Issue summary: View changes

Short answer: it seems like it is not currently possible unless you have drupalorg_versioncontrol module, which lives on drupalorg project, enabled; but not sure if that is what you want. If you have not many repositories, this can be done manually instead.

Long answer

Sadly the functionality for repository creation currently lives on a drupal.org customizations project, which makes this hard.

The real fix for this may be to move the hook_node's implementations like a piece of hook_node_insert doing the job en-queue from drupalorg_versioncontrol to versioncontrol_project_git here; but not sure if we want to do that since this would imply a synced release/deploy; apart for the code itself to extend it from drupalorg if needed.

Any strong opinions about this?

drumm’s picture

drumm
he/him
Location NY, US
CreditAttribution: drumm at Drupal Association commented

drupalorg_versioncontrol_node_insert() has some Drupal.org-specific logic for $repo_root and maybe elsewhere. That should be refactored within drupalorg module, and deployed incrementally, so the move to versioncontrol_project_git is straightforward.

mohammedrefai’s picture

mohammedrefai CreditAttribution: mohammedrefai commented
Issue summary: View changes

marvil07, drumm,
Thanks for your responses!

If it is possible to create the repository manually, then where (inside which directory) should I create the repository? also, are there specific steps that I need to follow to do that (i.e., write code to connect the project node to the repository path)?

When I attach files with a project release, they are stored inside /files/project, but what I am not sure about is when the repository for the project is created (either automatically or manually) where it should be located.

Thanks,