> As an alternative, I'm looking to use svnsync to fix this repository I'm just looking to clarify the process for completing this. > The fix for this (to dump & reload) has been successful with most of the repos, however to do this you need to have sufficient storage to duplicate the repos and one of the repos in question is over 700GB in size! In doing so we're encountering a handful of repos which were impacted by issue 4129 ( ). > We're in the process of migrating & upgrading our Subversion installation. See an example YAML file containing available configuration options.> On 13:23, Grierson, David (Lead Engineer) wrote: Please consult src-expose -help to learn more about the options available.įor more complex setups, configure your src-expose by providing a local configuration file: src-expose -snapshot-config config.yaml Your directories should now be syncing in Sourcegraph.
#Subversion sync code#
Go to Admin > Manage code hosts > Add repositories > Single Git repositories. You should use the network-accessible IP shown by ifconfig (rather than 127.0.0.1 or localhost). IMPORTANT: If you are using a Linux host machine, replace in the above with the IP address of your actual host machine because does not work on Linux. It may scroll by quickly due to logging, so if so, just scroll up.
src-expose will output a configuration to use.This command serves all Git repositories at the provided directory.ĭepending on whether you want to automatically sync and commit changes, or just serve the local directories. Or # Serve local Git repositories over HTTP. # Run a command periodically to sync changes, commit those changes as Git commits, and serve over HTTP. Pick the directory you want to export from, then run:
#Subversion sync full#
Start up a Sourcegraph instance (using our Quickstart or our full installation documentation). If you prefer to retain history, see serving repositories. While this syncing functionality means that the original change history will be lost, it eliminates any slow and costly Perforce-to-Git or Hg-to-Git or similar conversions that would otherwise be required. The new Git commit’s author will be src-expose, and will contain all changes since the last time the syncing command was run. Then Sourcegraph will run p4 sync every 10 seconds, and combine all of the fetched changes into a new Git commit. before : p4 sync # duration defines how often sync should happen. In addition to serving a local directory, src-expose can periodically run a command of your choice to fetch changes from a remote and combine them into a single new Git commit.įor example, if your src-expose is using a configuration YAML file that contains the following: # before is a command run before sync. Similar options exist for other non-Git VCSs. For example, if you are using Perforce, you can set up a cron job to run git p4 sync every few minutes or hours to fetch changes and convert them to Git commits that can then be served. In order to keep the code in the local repository up to date, you will need to run another command periodically to fetch changes.
If you wish to serve a local directory without running any syncing commands automatically, you can run src-expose serve (instead of the default src-expose) to only perform this function. In addition to simply providing a Git endpoint, it also provides a repository listing API that Sourcegraph expects a code host to have. Src-expose serves a list of local Git repositories over HTTP, making them available to Sourcegraph. See syncing and serving repositories, or run src-expose -h. Syncing changes, turning them into Git commits, and serving the resulting Git repositories src-expose can periodically run a command to sync changes to the code, and then combine those changes into a new Git commit in the local repository. See serving repositories, or run src-expose serve -h. Serving local Git repositories src-expose can serve local Git repositories over the network, and make them available to Sourcegraph (as if they were available on a traditional code host). You can run src-expose -h any time for help. Navigate to the directory that contains the Git repositories that you want to serve, then run the following commands. Additionally src serve-git uses a fast and modern git transfer protocol. We found users generally wanted to control the git repos and snapshotting complicated the setup. src serve-git only provides the serving of git repositories (no snapshotting). Since Sourcegraph 3.19 we recommend users to use src serve-git. NOTE: If using Perforce, see the Perforce repositories with Sourcegraph guide. For non-Git code hosts, Sourcegraph provides a CLI tool called src-expose to periodically sync and continuously serve local directories as Git repositories over HTTP.
Sourcegraph natively supports all Git-based Version Control Systems (VCSs) and code hosts. Non-Git code hosts (Perforce, Mercurial, Subversion, raw text, etc.)
0 kommentar(er)
