Version check doesnt handle none git installations

We are packaging git as rpm ourself for opensuse.

In the help screen we get: "GitLab 7.10.0.pre fatal: Not a git repository (or any of the parent directories): .git"

Is there any file we can provide which can hold the git revision for this?

This has been fixed with the external version checker.

Status changed to closed

still reproducable in master:

via "/help"

GitLab Community Edition 8.1.0.pre fatal: Not a git repository (or any parent up to mount point /srv) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set). 

rev 329e067f

Status changed to reopened

while we are at it ... could we define a file where I can provide the information like the git revision? then i could ship that file as part of the package and provide the information it would usually fetch from git.

@dzaporozhets

Any reason why your GitLab directory is not git repo?

I build an RPM for gitlab-ce. no need to ship the whole git history to every deployment host.

Same problem with Omnibus installation when a I run /opt/gitlab/bin/gitlab-rake gitlab:backup:create.

It outputs fatal: Not a git repository (or any of the parent directories): .git before doing the anyway.

Added ~65372 label

Any updates on this?

Status changed to closed

Closing due to lack of response.

on "/help"

"GitLab Community Edition 8.10.0-pre fatal: Not a git repository (or any parent up to mount point /srv) Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set)."

Verified with gitlab-ce-8.10.0~git857.7303de91.

I would be happy if we could define a file like GITLAB_CE_VERSION which would be read if it exists and only the fallback code is using git. I could create that file during my rpm build then and we would get a proper versioned number displayed without shipping the ".git/" tree.

Status changed to reopened

moved to gitlab#3731

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue

mentioned in merge request !14785