Details

    • Similar Issues:
    • Epic Link:

      Description

      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. 

       

       

        Attachments

          Issue Links

            Activity

            Hide
            michaelneale Michael Neale added a comment -

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

            Show
            michaelneale Michael Neale added a comment - Cliff Meyers Keith Zantow  not sure at what point this should be tackled, but after some changes (linked) I think at a time that suits. 
            Hide
            kzantow 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? Michael Neale

            Show
            kzantow 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? Michael Neale
            Hide
            michaelneale Michael Neale added a comment -

            Keith Zantow 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). 

            Show
            michaelneale Michael Neale added a comment - Keith Zantow 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). 
            Hide
            michaelneale Michael Neale added a comment -

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

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

              People

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

                Dates

                • Created:
                  Updated: