debian-mirror-gitlab/doc/user/project/settings/import_export.md

116 lines
4.7 KiB
Markdown
Raw Normal View History

2016-08-24 12:49:21 +05:30
# Project import/export
>**Notes:**
2016-09-13 17:45:13 +05:30
>
> - [Introduced][ce-3050] in GitLab 8.9.
2016-09-29 09:46:39 +05:30
> - Importing will not be possible if the import instance version differs from
> that of the exporter.
2018-11-08 19:23:39 +05:30
> - For GitLab admins, please read through [Project import/export administration](../../../administration/raketasks/project_import_export.md).
2016-09-13 17:45:13 +05:30
> - For existing installations, the project import option has to be enabled in
> application settings (`/admin/application_settings`) under 'Import sources'.
2016-11-03 12:29:30 +05:30
> Ask your administrator if you don't see the **GitLab export** button when
> creating a new project.
2018-03-17 18:26:18 +05:30
> - Starting with GitLab 10.0, administrators can disable the project export option
> on the GitLab instance in application settings (`/admin/application_settings`)
> under 'Visibility and Access Controls'.
2016-09-13 17:45:13 +05:30
> - You can find some useful raketasks if you are an administrator in the
> [import_export](../../../administration/raketasks/project_import_export.md)
> raketask.
> - The exports are stored in a temporary [shared directory][tmp] and are deleted
> every 24 hours by a specific worker.
2017-08-17 22:00:37 +05:30
> - Group members will get exported as project members, as long as the user has
2018-11-08 19:23:39 +05:30
> maintainer or admin access to the group where the exported project lives. An admin
2017-08-17 22:00:37 +05:30
> 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.
2018-03-27 19:54:05 +05:30
> - Control project Import/Export with the [API](../../../api/project_import_export.md).
2019-02-15 15:39:39 +05:30
> - If an imported project contains merge requests originated from forks,
> then new branches associated with such merge requests will be created
> within a project during the import/export. Thus, the number of branches
> in the exported project could be bigger than in the original project.
2016-08-24 12:49:21 +05:30
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.
2016-09-29 09:46:39 +05:30
## Version history
2018-03-17 18:26:18 +05:30
| GitLab version | Import/Export version |
| ---------------- | --------------------- |
2018-11-08 19:23:39 +05:30
| 11.1 to current | 0.2.4 |
| 10.8 | 0.2.3 |
2018-10-15 14:42:47 +05:30
| 10.4 | 0.2.2 |
2018-03-17 18:26:18 +05:30
| 10.3 | 0.2.1 |
| 10.0 | 0.2.0 |
| 9.4.0 | 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 |
2017-08-17 22:00:37 +05:30
2016-09-29 09:46:39 +05:30
> 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.
2016-08-24 12:49:21 +05:30
## Exported contents
The following items will be exported:
- Project and wiki repositories
- Project uploads
2019-02-15 15:39:39 +05:30
- Project configuration, including services
2016-08-24 12:49:21 +05:30
- Issues with comments, merge requests with diffs and comments, labels, milestones, snippets,
and other project entities
2018-05-09 12:01:36 +05:30
- LFS objects
2016-08-24 12:49:21 +05:30
The following items will NOT be exported:
- Build traces and artifacts
2017-08-17 22:00:37 +05:30
- Container registry images
- CI variables
2019-02-15 15:39:39 +05:30
- Webhooks
2017-08-17 22:00:37 +05:30
- Any encrypted tokens
2016-08-24 12:49:21 +05:30
## Exporting a project and its data
1. Go to the project settings page by clicking on **Edit Project**:
![Project settings button](img/settings_edit_button.png)
1. Scroll down to find the **Export project** button:
![Export button](img/import_export_export_button.png)
1. Once the export is generated, you should receive an e-mail with a link to
download the file:
![Email download link](img/import_export_mail_link.png)
1. 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:
![Download export](img/import_export_download_export.png)
## Importing the project
1. 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**:
![New project](img/import_export_new_project.png)
1. You can see where the project will be imported to. You can now select file
exported previously:
![Select file](img/import_export_select_file.png)
1. Click on **Import project** to begin importing. Your newly imported project
page will appear soon.
[ce-3050]: https://gitlab.com/gitlab-org/gitlab-ce/issues/3050
[tmp]: ../../../development/shared_files.md