How to configure Gitblit Federation

There are two ways to sync your reposittory

Federation Steps

Gitblit-Federation-Configuration

You can configure federation on Gitblit instance to keep then sync.One Gitblit instance keep in sync with other instance.

Requirements

• Two standalone Gitblit server

About Gitblit Federation

A Gitblit federation is a mechanism to clone repositories and keep them in sync from one Gitblit instance to another. If your Gitblit instance allows federation and it is properly registered with another Gitblit instance, each of the non-excluded repositories of your Gitblit instance can be mirrored, in their entirety, to the pulling Gitblit instance. You may optionally allow pulling of user accounts and backup of server settings.

Origin Gitblit Instance Requirements

• git.enableGitServlet must be true, all Git clone and pull requests are handled through Gitblit's JGit servlet
• federation.passphrase must be non-empty
• The Gitblit origin instance must be http/https accessible by the pulling Gitblit instance. That may require configuring port-forwarding on your router and/or opening ports on your firewall.

Configuring federation passphrase

The passphrase is used to generate permission tokens that can be shared with other Gitblit instances.
The passphrase value never needs to be shared, although if you give another Gitblit instance the ALL federation token then your passphrase will be transferred/backed-up along with all other server settings.
This value can be anything you want: an integer, a sentence, an haiku, etc. You should probably keep the passphrase simple and use standard Latin characters to prevent Java properties file encoding errors. The tokens generated from this value are affected by case, so consider this value CASE-SENSITIVE. The federation feature is completely disabled if your passphrase value is empty.
NOTE: Changing your federation.passphrase will break any registrations you have established with other Gitblit instances.

Pulling Gitblit Instance Requirement

• consider setting federation.allowProposals=true to facilitate the registration process from origin Gitblit instances

Controlling What Gets Pulled From Origin Instance

• After restarting your origin Gitblit instance, access federation page from user dropdown
• You can find different federation tokens on federation page, Note down any token based on what you want to allow to pull from this Instance
• Note down your http gitblit instance URL which you can access from your pulling gitblit instance, eg: http://111.111.111.111/gitblit

Controlling What Gets Pulled At Pulling Instance

• On your pulling Gitblit instance you can find # federation.example1.url in gitblit.properties , Modify it based on your requirement Eg:
federation.TestRepository.url = http://170.22.222.222/gitblit/
federation.TestRepository.token = 7620b6101eaa884cb89dce0
federation.TestRepository.frequency = 5 mins
federation.TestRepository.folder = TestRepository
federation.TestRepository.bare = true
federation.TestRepository.mirror = true
federation.TestRepository.exclude = *
federation.TestRepository.include = TestRepository.git TestRepo.git

Federation Pull Registration Kyes

Find the each registration keys [here] (http://gitblit.com/federation.html#H21)

Last Step To Sync Repository

• Restart your pulling instance. Wait for frequency time you have configured, you can find repository has been pulled from origin instance based on your configuration.
• On repository page you can see pulled repository under configured folder

Copy Repository Using Cron Job

• Create sell script with command to copy whole folder structure. like below
#!/bin/bash
scp –r /source/folder/path /target/Folder/path
• Add this script in to crone table with configurable time
crontab –e 
(Add below line and save it)
0 18 * * * /root/scripts/scp.sh

GitBlit Groovy Push Script

Comments

Post a Comment

Popular posts from this blog

Git Auto Increment tag

If you want GIT tag autoIncrement with one version number after each build you can use below shell script(./gittag.sh) as the hook. Scrip will find last committed TAG which starts with  ENV_TAG_PREFIX ( QA_V) and creates next release TAG then push tag to GIT. VERSION_MODE   [major|minor|revision|buildNumber - These are the possible value. each time one version is a tag with GIT. By default, buildNumber is pass which increment last digit in release tag like(x.x.x.1 to x.x.x.2). So if you want major release then you can pass major as option which tag GIT with major release  like (1.x.x.x to 2.x.x.x)] e.g. ./gittag.sh major       ./gittag.sh minor #!/bin/bash VERSION_MODE = $1 ENV_TAG_PREFIX = QA_V # "major": 1, # "minor": 0, # "revision": 0, # "buildNumber": 1 if [ "$VERSION_MODE" = "" ] ; then VERSION_MODE = "buildNumber" fi cd /path/to/your/git/checkout ...
Read more

Log rotate (catalina.out) of Tomcat

Rotate Catalina.out of tomcat on On Linux (Centos 7) server By default, Catalina.out file will not be rotated. To rotate it I have used logrotate. First, understand the  logrotate utility   Create tomcat file under /etc/logrotate.d/  using below command                               sudo vi /etc/logrotate.d/tomcat Press i to enable insert mode, past below script into file                                                                /opt/app/tomcat/logs/catalina.out {  su myuser myusergroup  missingok  notifempty  copytruncate  daily  size 5M  rotate 7 } Here /opt/app/tomcat/logs/catalina.out is path to your log file. press Esc key, then : wq!  to write and quite ...
Read more

Bypass SSL certificate check for Apache Axis2 client

For some reason, I wanted to totally ignore the certificate and trust store check with my Axis2 client stub implementations and I was looking for the solution. I came across a lot of articles which states about using  HttpsURLConnection to disable SSL check, but the problem is underlying Axis2 client doesn’t use the  HttpsURLConnection  Solution: We can use that TrustManager to create an SSLContext which trust all the servers. SSLContext sslCtx = SSLContext . getInstance ( "TLS" ); sslCtx . init ( null , new TrustManager [] { new TrustAllTrustManager ()}, null ); APIStub client = new APIStub ( url ); client . _getServiceClient (). getOptions (). setProperty ( HTTPConstants . CUSTOM_PROTOCOL_HANDLER , new Protocol ( "https" , (ProtocolSocketFactory) new SSLProtocolSocketFactory ( sslCtx ), 443 ));
Read more