[JIRA] (JENKINS-53170) SCM Sync unmaintained

[crai...@tataryn.net (JIRA)]

Title: Message Title

Craig Tataryn commented on JENKINS-53170   Re: SCM Sync unmaintained Craig Rodrigues Here's why I feel this plugin is still important: I have a whole ecosystem of "legacy" jobs (i.e. non-pipeline). They use a wide range of plugins, and special parameter types that I've cultivated over the years. Here's what I typically see when I try to use the "Convert to Pipeline" feature:   // Unable to convert a build step referring to "hudson.plugins.copyartifact.CopyArtifact". Please verify and convert manually if required. // Unable to convert a build step referring to "jenkins.plugins.publish__over__ssh.BapSshBuilderPlugin". Please verify and convert manually if required. // Unable to convert a build step referring to "jenkins.plugins.publish__over__ssh.BapSshBuilderPlugin". Please verify and convert manually if required. // Unable to convert a build step referring to "org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder". Please verify and convert manually if required. // Unable to convert a build step referring to "org.jenkinsci.plugins.conditionalbuildstep.singlestep.SingleConditionalBuilder". Please verify and convert manually if required. // Unable to convert a build step referring to "org.jenkinsci.plugins.conditionalbuildstep.ConditionalBuilder". Please verify and convert manually if required. // Unable to convert a build step referring to "org.jvnet.hudson.plugins.SSHBuilder". Please verify and convert manually if required. // Unable to convert a build step referring to "org.jvnet.hudson.plugins.SSHBuilder". Please verify and convert manually if required.   The Jenkins documentation is not very clear on what to do in this situation.  To keep up the the Jones' what I typically do is create an "umbrella" Pipeline script that takes care of orchestration between my legacy jobs.  I am perfectly content with leaving those legacy jobs as-is instead of trying to "fix" what ain't broken.  The only modification I'll make to my legacy jobs is strip them of their responsibility for kicking off downstream jobs. I instead let my orchestrating pipeline script handle that. I'll bet if you ask around, you'll find that my situation isn't at all unique in the community. Ultimately, stripping out the bells and whistles of per-change commit messages, the plugin is really just asking git (in my case) to commit/push using a .gitignore similar to:   # Ignore Everything * ####################### # Except these files... ####################### !.gitignore # Jenkins main config and job configs !config.xml # deployment keys for accessing bitbucket !sshkeys/* # plugin configs !hudson*.xml #Even if those files are in sub directories !*/ ####################### I think this plugin is still important, and it should live on in some fashion. It may have to drop some features, but at least it'll still give people a bit of security knowing that if they mistakenly messed up a job, they can easily go to SCM and lookup the previous version of their job in an effort to restore it.       Add Comment   This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.