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

Improve publishing and sharing of pure JS modules/libraries

XMLWordPrintable

    • Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2, Blue Ocean 1.1-beta4, Blue Ocean 1.1, Blue Ocean 1.1, Blue Ocean 1.2-beta1, Blue Ocean 1.2-beta2, Blue Ocean 1.2-beta3, Blue Ocean 1.2-beta4, Blue Ocean 1.3, Blue Ocean 1.4 - beta 1, Blue Ocean 1.4 - beta 2

      Publishing of npm modules like core-js and jdl is error prone. 

      This could be automated away via tooling, or an alternative mavenised way of delivering shared should be invested in to speed up development and improve sharing of code. 

      Impacts on extensibility and plugin development. 

       

      cc cliffmeyers kzantow if there are always going to be pure JS modules, then perhaps we should split this in 2 - one for modularity/shared code and one for better publishing of vanilla npm modules - thoughts? 

          [JENKINS-42602] Improve publishing and sharing of pure JS modules/libraries

          Michael Neale created issue -
          Michael Neale made changes -
          Epic Link New: JENKINS-35749 [ 171790 ]
          Michael Neale made changes -
          Rank New: Ranked higher
          Michael Neale made changes -
          Summary Original: Improve publishing of pure JS modules of shared code New: Improve publishing and sharing of pure JS modules/libraries
          Michael Neale made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]
          Michael Neale made changes -
          Description Original: Publishing of npm modules like core-js and jdl is error prone. 

          This could be automated away via tooling, or an alternative mavenised way of delivering shared should be invested in to speed up development and improve sharing of code. 

           

          cc [~cliffmeyers] [~kzantow] if there are always going to be pure JS modules, then perhaps we should split this in 2 - one for modularity/shared code and one for better publishing of vanilla npm modules - thoughts?            		New: Publishing of npm modules like core-js and jdl is error prone. 

          This could be automated away via tooling, or an alternative mavenised way of delivering shared should be invested in to speed up development and improve sharing of code. 

          Impacts on extensibility and plugin development. 

           

          cc [~cliffmeyers] [~kzantow] if there are always going to be pure JS modules, then perhaps we should split this in 2 - one for modularity/shared code and one for better publishing of vanilla npm modules - thoughts? 
          Cliff Meyers made changes -
          Link New: This issue relates to JENKINS-42601 [ JENKINS-42601 ]
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Epic Link Original: JENKINS-35749 [ 171790 ] New: JENKINS-35756 [ 171764 ]
          Michael Neale made changes -
          Link New: This issue blocks JENKINS-42601 [ JENKINS-42601 ]
          Michael Neale made changes -
          Link Original: This issue relates to JENKINS-42601 [ JENKINS-42601 ]

            kzantow Keith Zantow
            michaelneale Michael Neale
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: