Jenkins Javascript modules should not use the "jenkins-cd" organization

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      In Jenkins 2 we finally got rid of the Jenkins CI term. Jenkins is a universal automation server. Seems now we are about doing the same mistake with all the Javascript stuff. All new node.js modules go to the "jenkins-cd" organization. But they actually are not about CD.

      I think the organization and all modules should be renamed ASAP before the new UI development approach gets widely adopted.

      https://www.npmjs.com/search?q=jenkins-cd

            Assignee:
            Tom FENNELLY
            Reporter:
            Oleg Nenashev
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: