XMLWordPrintable

Details

    • Blue Ocean - 1.1-beta-1, Blue Ocean - 1.1-beta2, Blue Ocean 1.1-beta4, Blue Ocean 1.1, Blue Ocean 1.1

    Description

      Given the increasing tempo of build failures to to npm, the challenges with shrinkwrap and the inability to use mirrors, it may be time to evaluate the use of yarn as an alternative.

      Approach

      • General things to validate
        • Ensure "run scripts" still work with yarn
        • maven-frontend-plugin supports yarn natively, so we just need to switch this over.
        • Do local installs work nicely? (for rapid development). Can we obviate or at least better integrate w/ slink so rapid dev is more seamless? Check out "yarn link"
      • JDL Next
        • Need to determine if/how a Yarn-published module is able to freeze its dependencies when pulled in via npm (since there is no shrink, probably not, but maybe there's some magic)
        • Publish some beta JDL's and then pull them in via a blueocean-plugin PR to ensure ATH passes and things work, etc
      • blueocean-core-js
        • Do the same as above
        • At this point perhaps we add JDL as a peerDep and avoid the need to republish core-js each time new JDL is published (large pain point)
      • blueocean-web, dashboard and personalization
        • Port these over to yarn as well
      • Test with Artifactory

      Attachments

        Issue Links

          Activity

            jglick Jesse Glick added a comment -

            Yup, already linked above.

            jglick Jesse Glick added a comment - Yup, already linked above.
            cliffmeyers Cliff Meyers added a comment -

            Second PR that uses yarn to build blue ocean modules is here: https://github.com/jenkinsci/blueocean-plugin/pull/981

            cliffmeyers Cliff Meyers added a comment - Second PR that uses yarn to build blue ocean modules is here: https://github.com/jenkinsci/blueocean-plugin/pull/981
            cliffmeyers Cliff Meyers added a comment -

            This is on hold until new extensibility system lands. Both from a conflict standpoint, but also hopefully because a lot of our need to publish to npm registry may be obviated by it, and there are some pitfalls with publishing to npm/yarn registry when using a custom repo / mirror.

            cliffmeyers Cliff Meyers added a comment - This is on hold until new extensibility system lands. Both from a conflict standpoint, but also hopefully because a lot of our need to publish to npm registry may be obviated by it, and there are some pitfalls with publishing to npm/yarn registry when using a custom repo / mirror.
            jamesdumay James Dumay added a comment -

            Move this to backlog unit we can get Viveks time to unblock

            jamesdumay James Dumay added a comment - Move this to backlog unit we can get Viveks time to unblock
            jamesdumay James Dumay added a comment -

            Postponing. Looks like NPM is less crappy nowdays?

            jamesdumay James Dumay added a comment - Postponing. Looks like NPM is less crappy nowdays?

            People

              Unassigned Unassigned
              michaelneale Michael Neale
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: