Project transfer for Crucible

お困りですか?

アトラシアン コミュニティをご利用ください。

コミュニティに質問

The Project transfer for Crucible is an external plugin you can install in Crucible, which allows you to export and import Crucible projects with code reviews. Export is made in a human-readable format as an archive with XML files. This lets you move projects between instances or perform instance consolidation. You can also use such archive as a long-term backup, outside Crucible instance.


インストール

You can download it from the Atlassian Marketplace. It requires Crucible 4.8.0 or higher to run. You can use Administration > Manage add-ons to install it straight from your Crucible.

用途

(info) Instructions below apply to the latest version of the plugin, older versions may have less features or more prerequisites.

前提条件

  • target instance must not contain project of the same name and key
  • target instance must contain all users involved in code reviews (author, moderator, reviewer) and project metadata (e.g. default reviewers)
  • target instance must contain all groups involved in code reviews and project metadata (e.g. default reviewers)
  • target instance must contain a permission scheme used by the project
  • target instance must contain source repositories used in the project 
    • both defined as source roots in project's settings
    • and as source of commits in code reviews
  • both source and target instance shall have the same, default set of defect classifications
    • if classifications have been edited, import plugin may not match them

Supported features

  • code review metadata (author, moderator, reviewers, summary, objectives, dates, linked issues etc)
  • files added in a review which originate from a repository (name of source repository, path, revision)
  • comments (global and inline comments including replies, defects, linked Jira issues, author, date etc)

サポートされない機能

  • uploaded files
    • attachments and patches are not imported
    • it means that also comments added to uploaded files are not imported
  • comment resolution status
    • the "needs resolution" and "resolved" are handled by an external plugin, so were out of scope of 1.0.0 version
  • code branches
    • commits which have been added from a branch are transferred, but there's no information about the branch name on the 'details' page
  • code review history 
    • the audit log from code review page Tools > View Review History may show incomplete information or incorrect dates
  • project metadata, including permission schemes and defect classifications
    • permission schemes and defect classifications are not created automatically during import
  • users and groups
    • missing users and groups are not created automatically during import
  • merging of projects is unsupported
    • you can't add code reviews from a source instance into a project of the same name on a target instance


手順

  • revoke permission to project being exported (set a permission scheme with no access) to ensure that no modifications will happen in the meantime
  • export the project
    • go to Administration > Projects Settings > Export / import projects
    • select the project from the drop-down and click the 'Export' button 
    • wait until progress bar completes, once ready, the project will be shown in the Recently exported table
    • click the down-arrow icon to download the archive or trash to delete it from the server
    • (warning) current version handles export / import of only one project at once, don't run it in parallel
  • import the project on a target instance
    • go to Administration > Projects Settings > Export / import projects
    • choose file and click the 'Import' button 
    • wait until progress bar completes

Version history

バージョン機能Link
1.0.0Export / import code reviews without attachments開く


Road map

In next iterations of the plugin we plan to add the following:

  • content of files added as a patch or an attachment
  • comment resolutions and read status
  • code branches added to a review
  • defect classifications (all historical versions)
  • content of files added from a source repository (it means that source repository will not have to exist on a target instance)

トラブルシューティング

Enabling debug logging

Go to Administration > Server and click 'Turn debugging ON'.


Removing exported files manually

Exported files are stored in <java.io.tmpdir>/crucible-export-<project_key> folder.

Exported archive is stored in <java.io.tmpdir>/crucible-export-<random>.zip file.


Tracking code reviews, files and comments mappings

In case you have external systems, which store references to code reviews, review files or review comments, you can find ID mappings in the logs if debug logging have enabled during the import. Example messages:

Created review '<old id>' as '<new id>'


Created review item '<old id>' as '<new id>'


Created versioned comment '<old id>' as '<new id>' for review '<review id>'


Created general comment '<old id>' as '<new id>' for review '<review id>'


Created reply to comment '<old id>' as '<new id>' for parent comment '<new parent id>'


Some content of reviews is missing

Not all features are supported. If you enable debug logging you can learn more about content skipped. Example messages:

Skipping import of review item '<old id>' into review '<new review id>' as patches are unsupported.


Skipping import of review item '<old id>' into review '<new review id>' as attachments are unsupported.


Can't find review item '<id>' for a versioned comment '<id>'. Attachments are unsupported. Skipping comment and its replies.


フィードバック

Please add comments to the https://jira.atlassian.com/browse/CRUC-681 suggestion.


最終更新日: 2019 年 12 月 6 日

この内容はお役に立ちましたか?

はい
いいえ
この記事についてのフィードバックを送信する
Powered by Confluence and Scroll Viewport.