Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-35177

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Critical Critical
    • core, js-builder, js-modules
    • None
    • Jenkins 2

      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

          [JENKINS-35177] Jenkins Javascript modules should not use the "jenkins-cd" organization

          Oleg Nenashev created issue -
          Oleg Nenashev made changes -
          Component/s New: core [ 15593 ]
          Oleg Nenashev made changes -
          Summary Original: Jenkins Javascript modules structure uses "jenkins-cd" organization New: Jenkins Javascript modules should not use the "jenkins-cd" organization
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 171400 ] New: JNJira + In-Review [ 184297 ]
          Michael Neale made changes -
          Resolution New: Won't Fix [ 2 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            tfennelly Tom FENNELLY
            oleg_nenashev Oleg Nenashev
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: