Table of contents
- Introduction
- App Requirements
- Getting Started for Git Administrators
- Installation
- Managing License Key
- Working with SSH Keys
- Git URL Ports
- Setting Up Repositories
- Using the Auto-Connect Integration Wizard
- Connecting a Repository via Advanced Setup
- Adding a Repository Hosted on Windows Servers or Windows Network Share
- Tracked Folder and Special Integrations
- Managing Repository/Integration Configuration
- Repository/Integration Project Permissions
- Bulk Change
- Commit Email Notifications
- General Settings
- Web Linking
- Disabling Source and Commits Tabs
- Linking Git Commits to Jira Issues
- Smart Commits
- Repository Browser
- Viewing Commit Code Diffs
- Git User Identity
- Jira User Information Card
- Jira Issue Page
- Jira Project Page
- Jira Developer Panel
- Git Tags
- Reindexing
- JQL Searching
- Webhooks
- Jira Data Center (High Availability and Clustering)
- Localization
- Terms
- Licensing Notice
Documentation
Jira Data Center (High Availability and Clustering)
As of v2.6.12+ of the Git Integration for Jira app, the Data Center version of Jira is supported. Jira 6.3 or higher is required for Data Center editions of Jira.
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL PRIVILEGES ON tables TO jira1;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL PRIVILEGES ON tables TO jira2;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL PRIVILEGES ON sequences TO jira1;
ALTER DEFAULT PRIVILEGES IN SCHEMA public GRANT ALL PRIVILEGES ON sequences TO jira2; The configured repositories are located on the shared resource, since the nodes do not contain their own copy of the repositories.
The smart commits are processed by the reindex job which run once per cluster. The node updates the index during the scheduled reindex job. For Jira Data Centers, the indexes are stored in each node.
The GarbageCollection job should be run once on one node at the same time. The following are indexing triggers:
- Indexing is run on newly created repository on other nodes.
- Entries from index will be removed from other nodes.
- Reindex all repositories on other nodes when the reindex job is triggered.
For node changes:
When the number of nodes in the Data Center cluster is changed, the Jira administrator should manually perform a full reindex for all repositories to rebuild index on new nodes.
The trustFolderStat Setting
The trustFolderStat setting can be accessed in the following locations:
- Jira dashboard menu Git > Manage repositories > General Settings.
- Manage repositories > Actions > Edit integration connection settings.
- Actions > Show integration repositories > click a repository (Integration > repository level settings).
- Actions > Edit repository settings.
- Manage repositories page > Connect to Git repository > Advanced setup.
When the trustFolderStat setting is set to false, the .git/objects/pack folder will be always scanned to check for new pack files. If set to true, the last-modified attribute of the folder will be used to check the folder for modifications.
The default setting for Jira Data Center is false.
