Skip to main content Skip to complementary content
Close announcements banner

To add a project which is not stored in GIT

If you have already executed your Jobs on a development environment and want to have the exact same Jobs you have previously generated on your production environment, you can create a "no-GIT" project in which you will import the generated Jobs.

In this case, note that the name of the project must be the same as the name of the development project in which you have previously generated your Jobs.

For more information on how to import a Job that has been previously generated, see Adding an execution task to a pre-generated Job.


  1. From the toolbar of the Projects page, click Add.
    Mandatory fields in the Project panel to the right are followed by .
  2. In the Project panel, enter the following information:




    Type in the project name. This name should match the project name in which you have previously generated your Jobs.


    Select/clear this check box to activate/deactivate the current project.


    When you select a project in the Projects list that is already used as a project reference, this check box is selected by default.


    Fill in a description if needed.


    The first and last names of the project author. This field is read-only and so cannot be modified.

    Project type

    Select the type of project according to the license you set in Talend Administration Center. For more information, see What domains can you work in depending on your user type and license.

    Information noteNote: If the license set in Talend Administration Center is a Data Integration or ESB license only, this field will not display as there will not be other types available.

    Big Data Enabled

    Enable so that only Big Data Enabled users/user groups can access the project.


    Select the storage type None as your project is not stored in Git.

  3. Click Save to validate the creation of the new project or click Cancel to cancel it.

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 – let us know how we can improve!