kotovalexarian-likes-gitlab/gitlab-org--gitlab-foss

Sean McGivern 9a73b634ab Add table for files in merge request diffs

This adds an ID-less table containing one row per file, per merge request
diff. It has a column for each attribute on Gitlab::Git::Diff that is serialised
currently, with the advantage that we can easily query the attributes of this
new table.

It does not migrate existing data, so we have fallback code when the legacy
st_diffs column is present instead. For a merge request diff to be valid, it
should have at most one of:

* Rows in this new table, with the correct merge_request_diff_id.
* A non-NULL st_diffs column.

It may have neither, if the diff is empty.

2017-06-16 18:30:01 +01:00

3.5 KiB

Raw Blame History

Project import/export

Notes:

Introduced in GitLab 8.9.

Importing will not be possible if the import instance version differs from that of the exporter.

For existing installations, the project import option has to be enabled in application settings (/admin/application_settings) under 'Import sources'. Ask your administrator if you don't see the GitLab export button when creating a new project.

You can find some useful raketasks if you are an administrator in the import_export raketask.

The exports are stored in a temporary shared directory and are deleted every 24 hours by a specific worker.

Group members will get exported as project members, as long as the user has master or admin access to the group where the exported project lives. An admin in the import side is required to map the users, based on email or username. Otherwise, a supplementary comment is left to mention the original author and the MRs, notes or issues will be owned by the importer.

Existing projects running on any GitLab instance or GitLab.com can be exported with all their related data and be moved into a new GitLab instance.

Version history

GitLab version	Import/Export version
9.4.0 to current	0.1.8
9.2.0	0.1.7
8.17.0	0.1.6
8.13.0	0.1.5
8.12.0	0.1.4
8.10.3	0.1.3
8.10.0	0.1.2
8.9.5	0.1.1
8.9.0	0.1.0

The table reflects what GitLab version we updated the Import/Export version at. For instance, 8.10.3 and 8.11 will have the same Import/Export version (0.1.3) and the exports between them will be compatible.

Exported contents

The following items will be exported:

Project and wiki repositories
Project uploads
Project configuration including web hooks and services
Issues with comments, merge requests with diffs and comments, labels, milestones, snippets, and other project entities

The following items will NOT be exported:

Build traces and artifacts
LFS objects
Container registry images
CI variables
Any encrypted tokens

Exporting a project and its data

Go to the project settings page by clicking on Edit Project:
Scroll down to find the Export project button:
Once the export is generated, you should receive an e-mail with a link to download the file:
Alternatively, you can come back to the project settings and download the file from there, or generate a new export. Once the file available, the page should show the Download export button:

Importing the project

The new GitLab project import feature is at the far right of the import options when creating a New Project. Make sure you are in the right namespace and you have entered a project name. Click on GitLab export:
You can see where the project will be imported to. You can now select file exported previously:
Click on Import project to begin importing. Your newly imported project page will appear soon.

3.5 KiB Raw Blame History