Importing Configurations
The Jenkins Import matches the incoming Jenkins' jobs in Continua CI based on the Configuration name. If a conflict exists then the project and configuration are not added. However, if a child of the configuration still needs to be added then this will be added to the existing Configuration.
For example, if you try to import a Jenkins job called "myTestProject" into Continua CI which already has a configuration called "myTestProject", then the Jenkins job properties will not be converted over. However, if a new Jenkins Source Control system is attached to "myTestProject", then that will be added to the existing Configuration in Continua CI.
Importing Repositories
All Jenkins' source control management systems are added as repositories on the matching configuration. When source control management systems are converted to Continua CI repositories, they are given the name <repository type>-<Configuration name>_<counter>. The <counter> is only used if there are multiple SCMs of the same type on a single Jenkins job.
If a repository exists with the same name then it will not be created in Continua CI.
Importing Triggers
JenkinsImport checks if there is already a trigger with the same name. If the name exists then the trigger is not imported into Continua.
Importing Actions
Actions will only be created in Continua when an action's parent configuration is created. If you are modifying an existing configuration then actions will not be added into continua.