Introducing CollabNet GitEye

GitEye LogoToday I have the pleasure of announcing a new graphical client for Git that we have been working on — CollabNet GitEye.

GitEye is a Java GUI client for Git written on top of the Eclipse RCP framework. We are providing downloads for Windows, OSX and Linux though we can theoretically produce builds for a few other operating systems as well if the demand is there. Leveraging the Eclipse RCP framework allows us to provide a native GUI experience on all of these different operating systems, while still benefiting from the cross platform nature of Java. This approach also allows us to leverage a number of existing Eclipse plugins, such as EGit and our own CollabNet Desktop. That said, it is important to note for those that are IDE-averse, that using the Eclipse RCP framework does not mean we are using or repackaging the Eclipse IDE itself. We are simply building this client on the same low-level framework and libraries upon which the Eclipse IDE is built. A framework that we happen to think allows us to build an outstanding and highly functional Git client.

Enough of the low-level details, and more about GitEye. First off, GitEye is a full-featured Git client with all of the options you would expect in a graphical client. Most of the common Git actions are available from the GUI, such as clone, push, fetch, pull, merge, rebase, reset etc. There is a nice graphical view of your History and Annotations and there is a lot of tactical usage of git diff to provide context of changes within the UI as well as a full-blown graphical compare and merge tool. GitEye is a Git client, not an IDE, so the expectation is that you are using other tools and editors to work on your code. GitEye provides a simple text editor for making quick changes, but it also provides context-options to open up your Terminal or native File Manager to the selected location in your file system. You can also define custom commands which allows you to launch other tools. As an example, I work on OSX and use TextMate a lot. So I can right-click on folders or files and open them in TextMate to edit.

If these were all of the features of GitEye, it would be worthy of trying out, but really this is just scratching the surface of what is there. GitEye includes support for GitHub, including Pull Requests, Issues and Gists. All Git clients can presumably clone and push with GitHub, but we go well beyond that in our integration by providing native GUI support for these tools via the GitHub Eclipse plugin. Likewise, we have complete support for CloudForge and TeamForge and the agile planning tools in TeamForge. So besides being able to edit artifacts from within GitEye you can also use tools like the Agile Planning Board and Task Board from TeamForge. The GitHub and TeamForge tools are all built on top of the Eclipse Mylyn framework, so you also have the ability to install support for other trackers, such as Bugzilla, Trac and JIRA from within the application. Additional features that are included are support for Gerrit code reviews and Jenkins/Hudson build monitoring.

Keep your eyes open for future blog posts that describe these individual features in greater detail. Hopefully this was enough to entice you to want to try GitEye. You will be happy to learn that GitEye is Free. Learn more about the features and download it now here:

Mark Phippard

Engineering manager for several teams at CollabNet, including CloudForge, Subversion, Subversion Edge, Git and our Desktops and Integrations. Project owner for the Subclipse project, which provides Subversion support in Eclipse. Also a full committer for the Subversion project. Product owner for GitEye, Subversion Edge and the CollabNet Desktops and Integrations.

Tagged with: , , , , , , ,
Posted in CloudForge, Git, TeamForge
13 comments on “Introducing CollabNet GitEye
  1. Leo Hadacz says:

    Hi Mark,

    I downloaded GitEye and made an account on CloudForge ( to be able to register the GitEye client. Unfortunately GitEye rejects to register via “Connect to Your Account” due to invalid credentials. I used the default CloudForge server ( and exactly the same credentials (user name, password, domain) as for login on CloudForge. I can login on CloudForge. Can you explain please (make a video), howto register GitEye? Thanks.

  2. FIl says:


    I have the same problem, I’ve signed to free CloudForge account and cannot pass by the creditentials check when trying to connect, only that my 30-day trial has already expired and I cannot get to the preferences settings, cause it doesn’t let me in… Doh!!!!

    What now – anyone have any ideas?

    • Mark Phippard says:

      In your home folder there will be a folder named “.giteye”. You can blow that away and restart. This will also blow away any settings or data you have done in the client but will let you start over. You can easily re-add your Git repositories after doing this but any other tweaks you might have done would need to be reapplied.

      You can then do whatever needs to be done to add CloudForge and register the client.

  3. Mike Mezeul says:

    We’re using Giteye with CTF and due to password aging on our CTF site need to now update the cached Giteye password as we’re no longer able to connect to CTF since changing the password. Does anyone know how to do this on Giteye? We’ve poked around and tried searching but to no avail.


    • Mark Phippard says:

      I posted a reply that looks like it did not come through as a reply. So adding this in case you only asked to see replies via email. Go view all comments if you did not get it.

      • Mike Mezeul says:

        Thanks Mark – I know that the engineer that was having the problem got around it somehow but I will keep this information in a safe place as I’m sure it will come up again the next time someone changes their password.


  4. Mark Phippard says:

    I assume you are specifically talking about cached credentials for Git repositories you have locally cloned?

    FWIW, I typically use SSH which users keys rather than passwords. This is nice because you do not have these issues when your password changes. SSH is also faster than HTTPS.

    GitEye does not cache HTTPS credentials by default, but there is a checkbox you can set when cloning a repository to store your password in secure storage.

    For cached HTTPS passwords, if you expand your Git repository you will see a section named “Remotes”. Expand that, and expand whatever nodes are beneath it. Most likely it will be one called “Origin”. This will show the URL for the Git repository. Right-click on it and there are options to Clear Cached Credentials as well as Change Credentials.

    You can also access and clear or change any credentials that have been stored in the Secure Storage via the Preferences. Open Preferences and go to General > Security > Secure Storage.

  5. pooja says:

    hi, i cannot configure proxy settings in GitEye. i cannot find network connection unser Preferences in GitEye Tab?
    how do i go about it?

  6. baban says:

    how can I add custom commands to launch third party application? you mentioned you were able to launch textmate could you please share us the procedures to do it.

  7. Marc says:

    Hi Mark,
    would you be kind to explain me how to make pull requests between branches, so that an assignee can review and edit the request, prior to merging branches? (i.e. a developer with no write rights on a branch).
    I haven’t seen any “pull requests” action in GitEye

Leave a Reply

Your email address will not be published. Required fields are marked *




connect with CollabNet
   Contact Us

Have new blog posts sent directly to your email.

looking for something

CloudForge: Join #CollabNet for the TeamForge® 8.1 release webinar and learn about its new powerful enterprise #Git features
Date: 1 September 2015 | 5:00 pm

CloudForge: Join this #CollabNet #webinar and learn how to reduce server loads with #Git replication and improve Git performance
Date: 31 August 2015 | 6:00 pm

CloudForge: Seamlessly integrate #Git upstream and downstream to tools such as #Jira and #Jenkins on this #CollabNet #webinar
Date: 28 August 2015 | 5:30 pm