GitFusion feedback

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Zendesk: https://gitlab.zendesk.com/agent/tickets/93787

Related to https://gitlab.com/gitlab-org/gitlab-ee/issues/3630

Feedback from a customer on the GitFusion integration:

I just finished some initial testing of mirroring a Git Fusion repository in GitLab using push and pull mirroring. I ran into some issues that will need to be resolved.

Here is our current workflow:

1. The user registers an SSH key with Git Fusion that is paired with their Perforce ID.
2. They then push a set of commits to Git Fusion.
3. If there are no conflicts, the commits show up in Perforce under that user's Perforce ID.

This contrasts to the GitLab Git Fusion connector workflow of:

1. Mirroring to and from Git Fusion gets set up on a per-project basis, with a single credential (generated ssh key or https user ID/password) handling all changes to Git Fusion.
2. User pushes to GitLab project, but that single user does all pushes to Git Fusion, causing all changes in Perforce to show up with that single ID configured in the GitLab project mirroring settings.

Requirements that we need:

1. We require that all Git Fusion commits are done by users with a perforce account. We expect the GitLab side of the mirror to reject commits that are rejected on the Git Fusion side of the mirror because that user does not have a Perforce ID.
2. We require the Git Fusion integration to push each commit to the Git Fusion repository as the user making the commit so that Perforce will show those changes under that user's Perforce ID.