Check out locally a remote project already migrated

After one team member has migrated the remote project in NeoLoad 6.5, as described in Migrate a collaborative project, the other team members must:

To check out the remote project, NeoLoad 6.5 must be started. The Welcome to NeoLoad 6.5 screen is displayed. To check out a project, the Share > Check Out Project command must be chosen. The list of the projects shared on the collaboration server is displayed.

The project to check out must be selected in the list. Once selected, NeoLoad 6.5 makes it possible to give it a local name. The name can be different from the project collaborative name. By default, the suggested local name is the same as the remote one.

A click on Finish launches the retrieval of the project and the Project Sanity Check function is started automatically in background. When consistency errors or warnings are detected, the Project Sanity Check wizard is displayed, as described in Check the sanity of a project at design time.

  1. Choose Share > Check Out Project.
  2. Select a project.
  3. Click OK.
  4. When necessary, enter another name for the local duplicate.
  5. When necessary, change the local storage directory.
  6. Click Finish.

    If the Project Sanity Check wizard is displayed, you are able to see the project consistency errors or warnings.

Upgrade a Git project

The upgrade process consists in two steps:

  1. One team member migrates the project locally and push the migration to the Git server.
  2. Then, the other team members migrate their local project, and update the project to merge the remote project with the local one.

Migrate a Git project

After upgrading to NeoLoad 6.5 as described in Upgrade to NeoLoad NeoLoad 6.5, one team member only must migrate the remote project once for all. It is advised to designate the member with the most advanced project design because, in NeoLoad 6.5, all the project components can be published on the collaboration server. After the project is migrated on the Git server, the other team members will update their project to merge remote project with the local one.

Before starting the migration process, it is necessary to pay attention to the following prerequisites:

Migrating a project after upgrading NeoLoad is necessary to benefit from all the new functions available in the new major or minor version installed. The project migration process is fully automated. When a project is opened in NeoLoad, it detects the creation version and converts it.

NL-MigrateProject-6.3

Click on Yes to migrate the local copy of the project.

After local migration is completed, open the publication wizard to publish the migration onto the Git server.

NL-PublicationWizard-6.3

Add a comment for publication as described below.

NL-PublicationWizardDescription-6.3

Then click Next to validate the publication of the migration.

If the publication fails, it means the project is not up to date. For more information, see Common errors during project migration.

  1. Ensure that:
  2. In NeoLoad 6.5, open the project.
  3. In the message box for the project migration, click Yes.
  4. Open the publication wizard. Click Next.
  5. Enter a comment for migration publication. Click Next.
  6. Wait for the migration to be processed. Click Finish.
  7. Tell the other team members to update their Git project. See section “Update a Git project migrated”.

Update a Git project migrated

After one team member has migrated the remote project in NeoLoad 6.5, as described in Migrate a Git project, the other team members must:

Common errors during project migration

Some conflicts might be detected while publishing migration.

NL-MigrationConflictDetected-6.3

The publication cannot be pushed because the local project is not up to date with the remote version of the Git server.

It means that:

First, let’s check if the project has already been migrated by another team member:

  1. Start the update wizard.
  2. If an update is available, then the project has already been migrated by another team member. You can just click on Next to retrieve the update, and merge the remote project with the local one.
  3. Otherwise, if the error message below is displayed:

    NL-MigrationConflictdtected2-6.3

    Then another user edited the project with an older version of NeoLoad. There is a conflict. To resolve this conflict, you can either restart the migration process with a new clone of the project, or revert the other team member publication on the Git server.