タスクのアップグレードのトラブルシューティング
Jira Data Center のゼロ ダウンタイム アップグレード
このページの内容
関連コンテンツ
- Merge a pull request
- Remote merge is not happening in Bitbucket Server
- How to define a default merge strategy per Project
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Automatic branch merging
- Commits missing from Pull Request merge on target branch
- Code changes lost on target branch despite PR showing as merged with conflicted files in Bitbucket Data Center
- Bitbucket Server is unable to create the merge diff for pull requests
- The diff in pull requests is showing unrelated files after upgrade of Bitbucket Server or Data Center to 7.x or 2-way diff change.
ゼロ ダウンタイムのアップグレードを使用して Jira Software または Jira Service Management Data Center をアップグレードする際には、アップグレードするバージョンに応じて、データに対してアップグレード タスクの実行が必要となる場合があります。まれに、これらのアップグレード タスクは完了に失敗したり、正常に実行できない場合があります。これにはさまざまな理由が考えられます。一般的なトラブルシューティングとして、ログを確認して、潜在的な問題を見つけることをお勧めします。
最終更新日 2017 年 5 月 29 日
関連コンテンツ
- Merge a pull request
- Remote merge is not happening in Bitbucket Server
- How to define a default merge strategy per Project
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Merging a pull request with 'rebase and fast-forward' strategy fails with merge conflict in Bitbucket Server
- Automatic branch merging
- Commits missing from Pull Request merge on target branch
- Code changes lost on target branch despite PR showing as merged with conflicted files in Bitbucket Data Center
- Bitbucket Server is unable to create the merge diff for pull requests
- The diff in pull requests is showing unrelated files after upgrade of Bitbucket Server or Data Center to 7.x or 2-way diff change.
Powered by Confluence and Scroll Viewport.