• Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major Major
    • blueocean-plugin
    • None

      A few core infra components are now getting long in the tooth. Moving to nodejs/npm newer versoins wouldn't hurt. A react upgrade could be on the cards in preparation for v16. 

       

       

          [JENKINS-44592] Upgrade nodejs, npm

          Michael Neale created issue -
          Michael Neale made changes -
          Epic Link New: JENKINS-35749 [ 171790 ]
          Michael Neale made changes -
          Link New: This issue is blocked by JENKINS-42602 [ JENKINS-42602 ]

          Michael Neale added a comment -

          cliffmeyers kzantow not sure at what point this should be tackled, but after some changes (linked) I think at a time that suits. 

          Michael Neale added a comment - cliffmeyers kzantow  not sure at what point this should be tackled, but after some changes (linked) I think at a time that suits. 
          Michael Neale made changes -
          Sprint New: Blue Ocean 1.3 [ 296 ]

          Keith Zantow added a comment - - edited

          I think a 1.2 target for this stuff is good to me, rather do it sooner than later; the v16 react upgrade could be more problematic, and depending on the timing, maybe 1.3 for that? michaelneale

          Keith Zantow added a comment - - edited I think a 1.2 target for this stuff is good to me, rather do it sooner than later; the v16 react upgrade could be more problematic, and depending on the timing, maybe 1.3 for that? michaelneale

          Michael Neale added a comment -

          kzantow sounds good - will adjust ticket/stuff accordingly. npm changes likely lower risk so that makes sense. 

           

          On react - we can be proactive and go to 15.5 in preparation for 16, or wait. I think we can probably allow for one upgrade a year of react (the issue really is about plugins, and there are some breaking changes around Properties that would mean plugins need small changes, or monkey patching, to work). 

          Michael Neale added a comment - kzantow sounds good - will adjust ticket/stuff accordingly. npm changes likely lower risk so that makes sense.    On react - we can be proactive and go to 15.5 in preparation for 16, or wait. I think we can probably allow for one upgrade a year of react (the issue really is about plugins, and there are some breaking changes around Properties that would mean plugins need small changes, or monkey patching, to work). 
          Michael Neale made changes -
          Summary Original: Upgrade nodejs, npm and possibly react versions New: Upgrade nodejs, npm
          Michael Neale made changes -
          Sprint Original: Blue Ocean 1.3 [ 296 ] New: Blue Ocean 1.2 [ 326 ]

          Michael Neale added a comment -

          ok reworked, and moved react to: https://issues.jenkins-ci.org/browse/JENKINS-44593 for 1.3 

          Michael Neale added a comment - ok reworked, and moved react to: https://issues.jenkins-ci.org/browse/JENKINS-44593  for 1.3 

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

              Created:
              Updated: