SVN to GIT/Bitbucket Migration Steps

-

Please follow below steps to perform SVN to GIT/Bitbucket migration:

Prerequisites:
1. Must have a RHEL-7 or higher Linux server available to perform the steps.
2. The location where you decide to create new directory as “git_migration” must have enough disk space to hold the final GIT repository. Check the actual source SVN repo size
/root/git_migration
3. Must have installed these software/tools in server Min. JDK-8, SVN and GIT client
Installation commands, if you have access to internet from Linux server and subscription is in place:
yum install subversion
yum install git
yum install git-svn

4. Its assumes that your SVN repo uses standard directory convention as  trunk/tag/branches
5. You must have a Bitbucket/Git account created and new repository as “mygit” is ready to add a new repo code base.

Atlassian scripts to download for basic sanity on prerequisite environment is proper or not:
https://bitbucket.org/atlassian/svn-migration-scripts/downloads/
https://bitbucket.org/atlassian/svn-migration-scripts/src/master/

Verify that all necessary tools are installed
java -jar svn-migration-scripts.jar verify

e.g. output will show like below
[root@hostname]# java -jar svn-migration-scripts.jar verify
svn-migration-scripts: using version 0.1.56bbc7f
Git: using version 2.31.1
Subversion: using version 1.10.2
git-svn: using version 2.31.1


Preparation steps:
  1. Create new blank repository in your GitHub account "svn_git_migration"
  2. On new VM perform below steps to prepare authors file which will needed for history revision number and author name. 
  3. java -jar svn-migration-scripts.jar authors <Your SVN Repo URL> <user_name> <Password>     e.g.  java -jar svn-migration-scripts.jar authors https://mysvn.com/svn/REPO ram_krishna Pasword123 
  4. Will get output as below and create new authors.txt file and change name as per git user naming convention 
    user_name = user_name <user_name@mycompany.com>
  5. Create local Git repository from SVN repo. Run below command.
  7. nohup git svn clone --no-metadata -A /root/git_migration/authors.txt  https://mysvn.com/svn/REPO --trunk=trunk --tags=Tags --branches=Branches --username=user_name > svn_git_migration.out &
  8. This command will run in background and take time based on your SVN repository size.
  9. You can verify the output in tail mode as $ tail -1000f svn_git_migration.out

Once above process gets successfully completed then you can verify by running below commands

1. Can see all the branches are migrated from SVN to local git repository.
$ git branch -a
master
trunk
my_branch


** Now based on your requirement you can start push the code into your remote git branch.
Before this make sure below global configuration of git is already updated and SSH key setup done on git profile setting to push the code.

$ git config --list --show-origin

$ ssh -T git@github.com
> Hi USERNAME! You've successfully authenticated, but GitHub does not
> provide shell access.

Check whether ssh agent is running or not, It will give u PID
$ eval "$(ssh-agent -s)"

Generate ssh key from gitbash or command prompt:
$ ssh-keygen -t rsa -b 4096 -C "Ur_Email_ID"

You can refer below articles if you faced any issues during initial setup:
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token

Generating a new SSH key and adding it to the ssh-agent - GitHub Docs // Adding a new SSH key to your GitHub account - GitHub Docs
https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup

2. Finally you can checkout the respective branch and push the code into remote git repo

$ git remote add origin https://github.com/demo/mygit.git

$ git checkout -b trunk origin/trunk

$ git push origin origin/trunk

3. You can login to GitHub portal and cross check whether push code is present or not.

That's it, If branch is visible in GitHub then you have successfully migrated repository from SVN to GIT.




Splitting Your Git Repo While Maintaining Commit History:

Lets say this is the base git repo which contain your UI and API code base as below
Existing repository with combined code base directory:
https://github.com/demo/AllCode.git
---FrontEnd/
---BackEnd/

Create two new repository as FrontEnd_UI and BackEnd_API
https://github.com/demo/FrontEnd_UI.git
https://github.com/demo/BackEnd_API.git

Perform below steps one by one:
You can change here branch as per your setup, here used  trunk branch

Set-1] UI
git clone -b trunk https://github.com/demo/AllCode.git
cd <Folder>
git filter-branch --prune-empty --subdirectory-filter FrontEnd/ -- trunk
git remote remove origin
git remote add origin https://github.com/demo/FrontEnd_UI.git
git push --all 
git push --tags


Set-2] API
git clone -b trunk https://github.com/demo/AllCode.git
cd <Folder>
git filter-branch --prune-empty --subdirectory-filter BackEnd/ -- trunk
git remote remove origin
git remote add origin https://github.com/demo/BackEnd_API.git
git push --all 
git push --tags



Comments

Post a Comment

Popular posts from this blog

PUTTY - The server's host key is not cached in the registry cache

-
Error: "The server's host key is not cached in the registry. You have no guarantee that the server is the computer you think it is. The server's rsa2 key fingerprint is: [SSH KEY FINGERPRINT] If you trust this host, enter "y" to add the key to PuTTY's cache and carry on connecting. If you want to carry on connecting just once, without adding the key to the cache, enter "n". If you do not trust this host, press Return to abandon the connection. Store key in cache? (y/n) y" Answer: Simply run this command in your windows preferred terminal (cmd.exe etc) and agree to accept the host and store the cache: C:\Program Files (x86)\PuTTY\plink.exe -ssh [SSH USERNAME]@[SSH HOST] -P [SSH PORT] echo y | pscp -i /path/to/key/file user@remote:/tmp/file  . echo y | plink -i /path/to/key/file scripts.sh Usually you would hit “y” here, assuming the host key is correct, in order to store it in future connection.  The storage of this goes into the Registry under ...
Read more

OIM-12c Installation - FMW - SOA - IDM

-
Image
Oracle Identity Manager (OIM) 12c Installation Prerequisites: The Oracle Identity Manager software includes the following: 1] Oracle's Java Development Kit (JDK) 1.8 (jdk-8u311-linux-x64.tar.gz) 2]  Fusion Middleware 12.2.1.4.0 3]  SOA Suite 12.2.1.4.0 4] Oracle Identity and Access Management  12.2.1.4.0 What Do You Need? For completing Oracle IDM Setup you will need, Environment as below: Oracle Enterprise Linux 6 or similar, with access to the Internet At least 8GB RAM (16GB recommended) An Oracle Database Enterprise Edition 12 or superior installed and running. Note: Installing a Database for Identity and Access Management (IDM) Suite provides instructions on how to install an Oracle Database that is suitable for Oracle Identity and Access Management Suite. oracle and root user credentials SYS database user credentials Basic understanding of Linux An Oracle Technology Network (OTN) account OIM-11g PS3 Installation Steps: Just for reference https://www.oracle.com/webfol...
Read more

SAML & OAuth 2.0

-
Both SAML (Security Assertion Markup Language) and OAuth 2.0 are widely used protocols for authentication and authorization in web applications, but they serve different purposes. SAML (Security Assertion Markup Language) Purpose: Primarily designed for authentication and single sign-on (SSO) . How it works: A user attempts to access a service provider (SP). The SP redirects the user to an identity provider (IdP). The IdP authenticates the user and sends a SAML assertion to the SP. The SP validates the assertion and grants access to the user. Common use cases: Enterprise applications, government services, and federated identity management systems. OAuth 2.0 Purpose: Designed for authorization , allowing users to grant third-party applications access to their data on a specific service. How it works: A user attempts to access a resource on a service provider. The SP redirects the user to the authorization server. The user grants permission to the application. The authorization s...
Read more