{"id":628,"date":"2011-06-21T09:56:43","date_gmt":"2011-06-21T16:56:43","guid":{"rendered":"https:\/\/blogs.plm.automation.siemens.com\/t5\/Polarion-Blog\/Get-Going-with-Git\/ba-p\/380675"},"modified":"2026-03-26T05:29:05","modified_gmt":"2026-03-26T09:29:05","slug":"get-going-with-git","status":"publish","type":"post","link":"https:\/\/blogs.sw.siemens.com\/polarion\/get-going-with-git\/","title":{"rendered":"Get Going with Git"},"content":{"rendered":"

\"Git\"<\/A>By default, Polarion installs and uses a Subversion repository. But what if you have some codebase in an external repository… a Git<\/STRONG> repo, for example? And if you’re new to Git, how do you set up a repository? This post provides a few practical tips to help you get Git, and once you’ve got Git, get going \ud83d\ude42 so you can link Git revisions to Polarion Work Items.<\/p>\n

<\/p>\n

The Git project is hosted on: http:\/\/git-scm.com\/<\/A> There are download<\/STRONG> links for Windows<\/STRONG> and Linux<\/STRONG> versions.<\/p>\n

The Windows version uses a GUI application called GIT GUI for creating a repository. On Linux, you can use the console application GIT BASH to follow the Linux tutorial, which is also available online at: http:\/\/www.kernel.org\/pub\/software\/scm\/git\/docs\/gittutorial.html<\/A>.
\n

Setting up a Git repository<\/H3>
\nFor Polarion’s internal testing of the external repositories feature with a cloned Git repository, our QA team created a repository on www.github.com<\/A>. Let’s say this repo is called test2<\/SPAN>, and the user name is test2<\/SPAN>YourName.<\/p>\n

With the repository created on github.com, there are some steps needed on the client side.<\/p>\n

1. Global setup<\/p>\n

Download and install GIT. Then use the command line to run:
\n
\ngit config –global user.name “YourName”
\ngit config –global user.email your.name@yourdomain.com
\n<\/CODE><\/p>\n

2. Local initialization<\/p>\n

Run the following from the command line:
\n
\nmkdir test2
\ncd test2
\ngit init
\ntouch README
\ngit add README
\ngit commit -m ‘first commit’
\ngit remote add origin git@github.com:YourName\/test2.git
\ngit push -u origin master
\n<\/CODE><\/p>\n

Need to access an existing GIT Repo? Run this on the command line:
\n
\ncd existing_git_repo
\ngit remote add origin git@github.com:UserName\/RepoName.git
\ngit push -u origin master
\n<\/CODE>
\n

Authentication on Windows<\/H3>
\nGIT uses the SSH authentification method. You can find info on SSH setup for Windows at http:\/\/help.github.com\/win-set-up-git\/<\/A><\/p>\n

If you will configure Polarion to use your GIT repository, and if Polarion is running as a service (the preferred way unless you’re just running Polarion for an evaluation), you’ll need to add the HOME system variable pointing to the location where the .ssh folder is created. If you need a refreshed on how to add a system variable, check out: http:\/\/www.itechtalk.com\/thread3595.html<\/A>.
\n

Git it Working With Polarion<\/H3>
\nBy default, Polarion uses the Subversion (SVN) repository that was bundled with the distribution and installed with the platform. This Default<\/SPAN> repository is used for all projects. The assumption is that development code bases are managed in this same SVN repository. However, if you have code bases managed in another repository, you can configure your Polarion project to enable linking of Polarion Work Items (Default<\/SPAN> repository) to revisions in the external repository. External repositories can be either Git or Subversion.<\/p>\n

How to configure your Polarion Project for Git<\/STRONG>
\nThe Repositories Configuration<\/SPAN> topic in project Administration enables you to specify one or more external repositories so that revisions there can be linked to Polarion Work Items in the project. It’s possible to configure more than one external repository, and you can have both Subversion and Git repositories.<\/p>\n

Here’s the step-by-step to for configuring Polarion to work with a Git repository:
\n


    \n\t
  1. Log in with administrator permissions for the project you want to configure to use a Git repository, and open the project. (Enter Administration if your login did not already take you into it.)<\/LI>
    \n\t
  2. In Navigation, select Repositories Configuration<\/SPAN><\/LI>
    \n\t
  3. In the Repositories Configuration page, click the Add New Repository<\/SPAN> button.<\/LI>
    \n\t
  4. In the Provider list, select Git<\/STRONG>. When you select the repository type, a set of fields specific to the selected type appears below the list control. In this case, you’ll see the fields for Git.<\/LI>
    \n\t
  5. Fill in the fields with data specific to the repository you want the Polarion project to access, noting the required fields marked with a red asterisk (*).
    \nComment<\/EM>: Local Repository is the location of the “.git” folder on the filesystem in your git repository clone.<\/LI>
    \n\t
  6. Click the Save button to save the configuration settings.<\/LI>
    \n<\/OL>
    \nIt’s important to remember that the Default<\/SPAN> SVN repository is always used by Polarion to store Work Items and other Polarion data. If you have source code for the project in this repository as well as in the external Git repository, then after adding the external Git repository(ies) to the configuration, you must explicitly add the Default<\/SPAN> repository back to the project configuration. If you don’t do that, then users won’t be able to link source code revisions in the Default<\/SPAN> repository to Work Items. In this case, you would repeat the above steps selecting Default in the Provider list.<\/p>\n

    By default, Polarion installs and uses a Subversion repository. But what if you have some codebase in an external repository… a Git repo, for example? And if you’re new to Git, how do you set up a …<\/p>\n","protected":false},"author":68984,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"spanish_translation":"","french_translation":"","german_translation":"","italian_translation":"","polish_translation":"","japanese_translation":"","chinese_translation":"","footnotes":""},"categories":[1],"tags":[],"industry":[],"product":[],"coauthors":[],"class_list":["post-628","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/628","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/users\/68984"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/comments?post=628"}],"version-history":[{"count":1,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/628\/revisions"}],"predecessor-version":[{"id":629,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/posts\/628\/revisions\/629"}],"wp:attachment":[{"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/media?parent=628"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/categories?post=628"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/tags?post=628"},{"taxonomy":"industry","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/industry?post=628"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/product?post=628"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/blogs.sw.siemens.com\/polarion\/wp-json\/wp\/v2\/coauthors?post=628"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}

    We learned a few things about Git as our development team got Polarion working with it in version 2011-SR1. But we’re still more Git Newbie than Git Expert (Subversion<\/A> has been our thing). If you’ve got a good tip for people who are just getting going with Git – please post a comment!<\/p>\n","protected":false},"excerpt":{"rendered":"