check out the remote migrated project to get the latest version of the project.
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.
To check out a project
Choose Share > Check Out Project.
Select a project.
When necessary, enter another name for the local duplicate.
When necessary, change the local storage directory.
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:
One team member migrates the project locally and push the migration to the Git server.
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:
All the other team members should publish their local projects from a previous minor version of NeoLoad onto the Git server. After that, they must stop updating it until the migration is complete.
The team member in charge of migration should be up to date in the previous minor version of NeoLoad.
The local disk must have enough free space because it is used as a temporary workspace for the migration process.
It is advised to back up the project in the previous version of NeoLoad before migrating it. For more information, see Export a project.
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.
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.
Information: When the publication is related to a project migration, all the elements of the project need to be published, so the remote version can be fully migrated. As a result, it is not possible to choose which element can be pushed or not (unlike regular publication).
Add a comment for publication as described below.
Then click Next to validate the publication of the migration.
open the project with NeoLoad 6.5 to migrate their local project,
update their project to merge the remote project with the local copy.
Common errors during project migration
Some conflicts might be detected while publishing migration.
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:
either the project has already been migrated by another team member,
or the project has been updated with a lower version of NeoLoad , by another team member.
First, let’s check if the project has already been migrated by another team member:
Start the update wizard.
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.
Otherwise, if the error message below is displayed:
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.