I have been with Jenkins since the freestyle jobs (read pre-pipeline plugin suite) days.
*Question:* Why does Cloudbees want users to maintain two pipeline orchestration definition formats i.e. (DECLARATIVE) GROOVY (IN CLASSIC/STATIC/CORE-JENKINS) and YAML (JENKINS-X). What if any is the bottleneck-removal automated migration path/strategy (like freestyle=>pipeline job converter plugin) that Cloudbees offers for their multi-year loyal Pre-JenkinsX users who have invested in their groovy (declarative) Jenkinsfiles to move to jenkins-x.yml when they move their applications (including Jenkins) from VMs to K8. Thanks much for your consideration in reading above and if possible providing your answer on it. Firmsoil -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/8802dbeb-33bd-4c33-87af-58ac28ad9c4e%40googlegroups.com.
