Git and Provar Projects

Getting Started

Once the Git plugin is installed, you will need a Provar Project to work on.

This can be done in various ways:

  1. By importing a Provar Project from an existing local repository;
  2. By cloning from an existing Project stored in Git;
  3. By creating a Project locally and linking it to Git.

Select one of these options to get started.

Once you have your Project sorted, refer to Working with Git for more best practices on using Git with Provar.

Option 1: Importing a Project from an existing local repository

To import a Project from an existing local repository, first ensure that you already have the relevant repository in your local file system and you know where it is located. This could be done by cloning the repository in advance, creating it from scratch or copying it from another location.

Then click the link ‘Import a Test Project from Git’ on the Provar Welcome Screen:

This will present the following screen:

Select ‘Existing local repository’ then click the ‘Next’ button:

On the next screen, specify a directory and then click ‘Search’ to trigger a scan for Git repositories contained in that directory.

If Git repositories are found, they will be listed and you can select one or more to add:

Select the desired repository, then click the ‘Finish’ button.

On the next screen, select the desired import process. The default option ‘Import existing Eclipse projects’ is recommended:

Then click the ‘Next’ button.

The next screen will display available Test Projects in the repository:

Click the ‘Finish’ button to import the selected Test Project into the workspace.

Option 2: Cloning a Project from Git

Cloning a remote repository will copy a repository from Git to your local file system.

To clone a remote repository, first click the link ‘Import a Test Project from Git’ on the Provar Welcome Screen:

Then select ‘Clone URI’ and click the ‘Next’ button:

The following screen will be presented:

Enter the information as follows:

  • URI: The complete URI of the remote repository or the path on the file system. This field is automatically synchronized with the other fields.
  • Host: The name of the remote host
  • Repository Path: Path to the remote repository
  • Protocol: The following Protocols are supported:
    • file: File system access to the repository
    • ftp: File Transfer Protocol
    • git: The most efficient built-in git protocol (default port 9418). This protocol doesn’t provide authentication. Typically used for anonymous read access to the repository
    • http: Hypertext Transfer Protocol can be tunneled through firewalls
    • https: Hypertext Transfer Protocol Secure can be tunneled through firewalls
    • sftp: SSH File Transfer Protocol
    • ssh: Git over secure shell (SSH) protocol. Typically used for authenticated write access to the repository
  • Port: Port number
  • User: The username used for authentication
  • Password: The password used for authentication
  • Store in Secure Store: Whether the password is saved in the Eclipse secure store

Then click the ‘Next’ button.

The following screen, Branch Selection, will display branches available in the repository.

If you have multiple repositories, select the one which contains your project:

Then click the ‘Next’ button.

Select the workspace by clicking the ‘Browse’ button:

Then click the ‘Next’ button.

The following screen will display the project for import:

Click the ‘Finish’ button to import the project.

Option 3: linking a local Project to Git

To link a local Project to Git, you must first have created a Project in Provar which can be pushed to Git. (Refer to Creating and Importing Projects for information on how to do this.)

Once you have a Project ready to be linked, right-click on the Project Name in the Navigator, then select Team > Share Project… Committing and Pushing to Repository:

Browse a path for the repository field:

Then click the ‘Finish’ button.

Then right-click on the Project and select Team > Commit

In the next screen, select the files you want to commit and add comments:

Then click the ‘Commit’ button.

Then right-click on Project and select Team > Push Branch ‘master’:

Enter the repository URL, User & Password:

Then click the ‘Next’ button.

On the next screen, enter your chosen branch (it should be ‘master’ in this case), tick the ‘Force Overwrite’ checkbox:

Note that, since the ‘Force Overwrite’ checkbox is being ticked, this push will overwrite any files on the remote branch which conflict with the ones you are pushing. This option is therefore not recommended for use in general workflow as there is a risk of losing work. For a better practice in resolving conflicts, please refer to to Pull Requests and Resolving Conflicts.

Then click the ‘Next’ button.

On the next screen, review the details of the push you are about to make:

To confirm the push, click the ‘Finish’ button.

Committing Work

Once changes have been completed, the work should be committed and pushed to the repository.

To commit work, right-click on the Project in the Navigator view, then select Team > Commit…:

 This will display the following screen:

Enter a Commit message and select your files, then choose ‘Commit and Push’ or ‘Commit’.

Pushing Commits

All committed tasks need to be pushed to the repository.

To push your committed work, right-click on the Project in the Navigator view, then select Team > Push Branch [BranchName]…:

This will display the following screen:

Specify your preferred settings then click the ‘Next’ button.

This will display a Push Confirmation:

Click the ‘Finish’ button to push to repository.

The results will be displayed as follows:

Then click ‘OK’ to finish.

Once you have your Project sorted, refer to Working with Git for more best practices on using Git with Provar.

2017-08-24T17:00:21+00:00

Leave A Comment