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

          Tom FENNELLY added a comment -

          So what org name should we use?

          "jenkins-ci" and "jenkins" were gone and that's why I picked "jenkins-cd". Good news is that "jenkinsci" seems to be available.

          Really though ... is this such a big issue? If you can gather together enough support for changing it then we can see about doing it.

          Tom FENNELLY added a comment - So what org name should we use? "jenkins-ci" and "jenkins" were gone and that's why I picked "jenkins-cd". Good news is that "jenkinsci" seems to be available. Really though ... is this such a big issue? If you can gather together enough support for changing it then we can see about doing it.

          Oleg Nenashev added a comment - - edited

          I think "jenkins" would be the best option. Or maybe "jenkins-js"

          > Really though ... is this such a big issue? If you can gather together enough support for changing it then we can see about doing it.

          IMHO it's really important. The migration to jenkins-cd has been done without wide discussion within the community IIRC, so that's why the problem arised now.

          Oleg Nenashev added a comment - - edited I think "jenkins" would be the best option. Or maybe "jenkins-js" > Really though ... is this such a big issue? If you can gather together enough support for changing it then we can see about doing it. IMHO it's really important. The migration to jenkins-cd has been done without wide discussion within the community IIRC, so that's why the problem arised now.

          Tom FENNELLY added a comment -

          As I said ... "jenkins" is not an option (becuse the name is already taken) and I don't get how "jenkins-js" is all that better than "jenkins-cd".

          Anyway ... in the end I don't mind. If it's something that's super important to you guys then we can change it ... you just need to find a name that works and isn't silly.

          Tom FENNELLY added a comment - As I said ... "jenkins" is not an option (becuse the name is already taken) and I don't get how "jenkins-js" is all that better than "jenkins-cd". Anyway ... in the end I don't mind. If it's something that's super important to you guys then we can change it ... you just need to find a name that works and isn't silly.

          Daniel Beck added a comment -

          Who/what uses jenkins and jenkins-ci? Is it possible to contact them?

          Daniel Beck added a comment - Who/what uses jenkins and jenkins-ci? Is it possible to contact them?

          Oleg Nenashev added a comment - - edited

          "jenkins" is being owned by Silas Sewell: https://github.com/silas
          Usage: node.js client for Jenkins: https://www.npmjs.com/package/jenkins

          Oleg Nenashev added a comment - - edited "jenkins" is being owned by Silas Sewell: https://github.com/silas Usage: node.js client for Jenkins: https://www.npmjs.com/package/jenkins

          Daniel Beck added a comment -

          Ugh, so package name collides with org name?

          jenkinsci while "ci" would be consistent with GitHub, Twitter, mailing lists…?

          Daniel Beck added a comment - Ugh, so package name collides with org name? jenkinsci while "ci" would be consistent with GitHub, Twitter, mailing lists…?

          Oleg Nenashev added a comment -

          > jenkinsci while "ci" would be consistent with GitHub, Twitter, mailing lists…?

          Yes... I'd prefer just "jenkins" in such case, but jenkinsci also has a good justification.
          Maybe the maintainer of this JS package agrees to rename it

          Oleg Nenashev added a comment - > jenkinsci while "ci" would be consistent with GitHub, Twitter, mailing lists…? Yes... I'd prefer just "jenkins" in such case, but jenkinsci also has a good justification. Maybe the maintainer of this JS package agrees to rename it

          Michael Neale added a comment -

          tfennelly I think we can close this, it isn't going to happy any time. 

          Michael Neale added a comment - tfennelly I think we can close this, it isn't going to happy any time. 

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

              Created:
              Updated:
              Resolved: