Skip to content

[Feature Proposal] GitLab support svn features (ls, checkout and export) for private repos

Problem to solve

See the problem I have described at Since SVN does not support exporting the private repo from GitLab, is there some solution?.

In the terminal, it looks like:

 ~ svn ls https://gitlab.com/gusbemacbe/dotfiles/trunk/master/docker/gitea/docker-compose.yaml
svn: E170013: Unable to connect to a repository at URL 'https://gitlab.com/gusbemacbe/dotfiles/trunk/master/docker/gitea/docker-compose.yaml'
svn: E160013: '/gusbemacbe/dotfiles/trunk/master/docker/gitea/docker-compose.yaml' path not found

Intended users

Personas and developers

User experience goal

The svn ls, svn checkout and svn export allow the users to select only some files and folders from their private repos for their dot-files by middle of a shell script file or a yaml file.

Proposal

Add support for svn ls, svn checkout and svn export for both public (I tested and it does not work) and private repositories.

Further details

In reference to these questions, but svn ls, svn checkout and svn export is exclusively a GitHub features:

Permissions and Security

Since the repository is private, it requires username and password or access token. For example:

svn export https://gitlab.com/gusbemacbe/dotfiles/branches/docker/gitea/docker-compose.yaml --username=gusbemacbe password=xxxxx

Documentation

Availability & Testing

As the repository is private and contains confidential information, GitLab with svn should be stronger in security, all token access, GPG and SSH should be enforced.

  • Add the latest svn version and support with GitLab
  • Test svn with GitLab system
  • Test svn with gitlab-ci and pipelines

What does success look like, and how can we measure that?

A complete export without fail and error E170013 indicates a success.

What is the type of buyer?

Nothing, svn is totally open source

Is this a cross-stage feature?

Yes, so we intend to export multiple repositories, selecting some files and folders.

Links / references

Check the references above.

Extra: http://svnbook.red-bean.com/index.en.html

Extra

I think you must be interested in hearing from git-svn (we type git svn) and SCCS/shilytools.