Skip to main content Skip to complementary content

Running an analysis on an external Talend project

Procedure

  1. Select External Talend project and click Locate. The project must be in a Git repository or in a local workspace folder that contains the Talend project to analyze.
  2. Select the projects you want to analyze from the list of projects collected from the server.
  3. Select the provider and add details:
    • Git Repository: Provide the repository URI and credentials. If the repository URI refers to SSH protocol, the credentials fields won't be displayed, the default SSH key will be provided.
    • SVN Repository: Provide the repository URI and credentials.
    • Local workspace: Provide a path of a local folder containing one or more folders as a Talend project folder with a talend.project file. A Talend project folder must be a direct child folder of the parent one. There is no recursive search.
    Third step of the Project Analysis Wizard, where you get the project location, second part

    Example:

    parent_folder\
        project_1\
          talend.project
          ...
          processes\
          processes_mr\
          ...
        project_2\
          talend.project
          ...
          processes\
          processes_mr\
          ...

    In this example, the workspace is the path of the parent_folder containing two Talend projects: project_1 and project_2.

    Using a Talend Studio workspace as a local Talend Cloud Migration Platform workspace:
    • For a local project: The workspace folder is the Talend Studio workspace path.
    • For a remote project: The Talend Studio workspace has a folder structure similar to this one:
      workspace\
        .Java\
        .JETEmitters\
        .metadata
        .repositories\
          XXXXXX\     -> unique id
            .git
            master\
              project_1\
            branches\
              development\   -> any branch name
                project_1\
    In this case, the workspace can be either:
    • <path of workspace>\.repositories\XXXXXX\master
    • <path of workspace>\.repositories\XXXXXX\branches\development
  4. Click Load.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!