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

Republish all NPM packages into a "jenkins-cd" NPM scope

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major Major
    • js-modules

      (this isn't anything to do with "core" component, but nothing else is appropriate either)

      I already subscribed to capture the jenkins-cd organisation on the central registry ("jenkins-ci" was not available because of a username of the same).

      At the moment, all packages are published under my account (tfennelly), which is not what we want. This will allow me and others to publish packages under a community owned scope via this org.

      TODO

      • js-modules (done)
      • js-builder (done)
      • js-test (done)
      • js-samples
      • js-libs

          [JENKINS-32319] Republish all NPM packages into a "jenkins-cd" NPM scope

          Tom FENNELLY added a comment -

          I've done this for the following modules:

          • js-modules
          • js-builder
          • js-test

          Tom FENNELLY added a comment - I've done this for the following modules: js-modules js-builder js-test

          Keith Zantow added a comment -

          tfennelly I think you did this already, right?

          Keith Zantow added a comment - tfennelly I think you did this already, right?

          Tom FENNELLY added a comment -

          Yes, I think we can call this done for now anyway.

          Tom FENNELLY added a comment - Yes, I think we can call this done for now anyway.

            tfennelly Tom FENNELLY
            tfennelly Tom FENNELLY
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: