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

Blue Ocean SDK design document - extensibility improvements

    • 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.4 - beta 1, Blue Ocean 1.4 - beta 3, Blue Ocean 1.4 - beta 2, Blue Ocean 1.6 - beta 2, Blue Ocean - 1.6 - beta 4

      We want an SDK experience for developing Blue Ocean plugins, should document/research aims and goals

      Goals

      • Public API
      • Typed extension points
      • Improved module resolution
      • Improved module versioning (e.g. we don't have to keep bundling common libraries into Blue Ocean)
      • Write "javascript only" plugins without maven
      • Integration with maven-hpi-plugin
      • Typescript investigation
      • Use of tree API to avoid fetching unwanted actions

          [JENKINS-42173] Blue Ocean SDK design document - extensibility improvements

          James Dumay created issue -
          James Dumay made changes -
          Epic Link New: JENKINS-35756 [ 171764 ]
          James Dumay made changes -
          Priority Original: Minor [ 4 ] New: Major [ 3 ]

          Keith Zantow added a comment -

          jamesdumay impossible to write plugins without HPI, the rest of it looks awesome.

          Keith Zantow added a comment - jamesdumay impossible to write plugins without HPI, the rest of it looks awesome.

          James Dumay added a comment -

          kzantow "without maven" is possible

          James Dumay added a comment - kzantow "without maven" is possible
          James Dumay made changes -
          Description Original: We want an SDK experience for developing Blue Ocean plugins

          *Goals*
          * Public API
          * Typed extension points
          * Improved module resolution
          * Improved module versioning
          * Write "javascript only" plugins without maven-hpi-plugin toolchain
          * Integration with maven-hpi-plugin
          New: We want an SDK experience for developing Blue Ocean plugins

          *Goals*
          * Public API
          * Typed extension points
          * Improved module resolution
          * Improved module versioning
          * Write "javascript only" plugins without maven
          * Integration with maven-hpi-plugin
          James Dumay made changes -
          Description Original: We want an SDK experience for developing Blue Ocean plugins

          *Goals*
          * Public API
          * Typed extension points
          * Improved module resolution
          * Improved module versioning
          * Write "javascript only" plugins without maven
          * Integration with maven-hpi-plugin
          New: We want an SDK experience for developing Blue Ocean plugins

          *Goals*
          * Public API
          * Typed extension points
          * Improved module resolution
          * Improved module versioning (e.g. we don't have to keep bundling common libraries into Blue Ocean)
          * Write "javascript only" plugins without maven
          * Integration with maven-hpi-plugin
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Rank New: Ranked higher
          James Dumay made changes -
          Priority Original: Major [ 3 ] New: Critical [ 2 ]

            imeredith Ivan Meredith
            jamesdumay James Dumay
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: