Jenkins importer should not fatal when unsupported SCMs are detected.

I'm evaluating Bamboo 5.5.0 and tried importing jobs from our existing Jenkins install (1.554.1 LTS). Problem is, every job uses Perforce and the importer sees this as a fatal condition.

Per a twitter conversation with James Dumay, he thought the importer would just not bring in the SCM config but otherwise bring in other parts of the job. My import experience did not match this.

I'd like to see the importer enhanced to support bringing in jobs and leaving the SCM configuration out, vs the current situation where nothing comes across. This would still save time, as the end user could then go job by job and fix the SCM configuration.

Relevant text from an import log:

--------------------------------------------------------------------------------------
Job name: AndroidClient-Trunk-Continuous
SEVERITY: HIGH
Unsupported configuration for plugin 'hudson.plugins.buildblocker.BuildBlockerProperty'
SEVERITY: HIGH
Unsupported configuration for plugin 'hudson.plugins.disk_usage.DiskUsageProperty'
SEVERITY: HIGH
Unsupported configuration for plugin 'hudson.plugins.perforce.PerforceSCM'
SEVERITY: HIGH
Unsupported configuration for plugin 'hudson.plugins.warnings.WarningsPublisher'
SEVERITY: HIGH
Unsupported configuration for plugin 'hudson.plugins.tasks.TasksPublisher'
SEVERITY: HIGH
Unsupported configuration for plugin 'hudson.plugins.violations.ViolationsPublisher'
SEVERITY: HIGH
Unsupported configuration for plugin 'Email-ext'
SEVERITY: FATAL
Scm cannot be imported