• Adapt to JENKINS-68249

      We have a responsibility to our users to perform due diligence when making breaking changes to the ecosystem. When making such changes, it is incumbent on us to enumerate the affected plugins and, for each one:

      • If the plugin is actively maintained, ensure a pull request has been created and ensure the pull request is merged and released prior to shipping the LTS.
      • If the plugin is not actively maintained, make a conscious decision to leave it behind, ideally also filing an update-center2 PR to formally mark the plugin as deprecated in the Update Center.

      This process has been followed for many other transitions, including JEP-227 and JEP-233.

      The presence of JENKINS-68250, JENKINS-68022, JENKINS-67737, and JENKINS-67176 (two of which remain in the "Open", rather than "In Review" or "Resolved", state at the time of current writing) indicate that such due diligence was not fully performed at the time of integration of JENKINS-68249.

      A systematic search should be done across sources and binaries for all currently supported (non-deprecated) plugins to see if they are affected by the changes introduced in JENKINS-68249. This ticket should be used to track the process of ensuring that each affected plugin gets released prior to shipping the LTS or gets (explicitly) left behind by a conscious decision.

          [JENKINS-68251] Adapt to SVG icon removal from JENKINS-68249

          Basil Crow created issue -
          Basil Crow made changes -
          Link New: This issue is caused by JENKINS-68249 [ JENKINS-68249 ]
          Basil Crow made changes -
          Description Original: The presence of JENKINS-68250, JENKINS-68022, JENKINS-67737, and JENKINS-67176 (two of which remain open at the time of current writing) indicate that due diligence was not fully performed at the time of integration of JENKINS-68249. A systematic search should be done across sources and binaries for all currently supported (non-deprecated) plugins to see if they are affected by the changes introduced in JENKINS-68249. If new issues are discovered, new tickets should be filed for each plugin. New: The presence of JENKINS-68250, JENKINS-68022, JENKINS-67737, and JENKINS-67176 (two of which remain in the "Open", rather than "In Review" or "Resolved", state at the time of current writing) indicate that due diligence was not fully performed at the time of integration of JENKINS-68249. A systematic search should be done across sources and binaries for all currently supported (non-deprecated) plugins to see if they are affected by the changes introduced in JENKINS-68249. If new issues are discovered, new tickets should be filed for each plugin.
          Basil Crow made changes -
          Description Original: The presence of JENKINS-68250, JENKINS-68022, JENKINS-67737, and JENKINS-67176 (two of which remain in the "Open", rather than "In Review" or "Resolved", state at the time of current writing) indicate that due diligence was not fully performed at the time of integration of JENKINS-68249. A systematic search should be done across sources and binaries for all currently supported (non-deprecated) plugins to see if they are affected by the changes introduced in JENKINS-68249. If new issues are discovered, new tickets should be filed for each plugin. New: We have a responsibility to our users to perform due diligence when making breaking changes to the ecosystem. When making such changes, it is incumbent on us to enumerate the affected plugins and, for each one:

           * If the plugin is actively maintained, ensure a pull request has been created and ensure the pull request is merged and released prior to shipping the LTS.
           * If the plugin is not actively maintained, make a conscious decision to leave it behind, ideally also filing an [update-center2 PR|https://github.com/jenkins-infra/update-center2] to formally mark the plugin as deprecated in the Update Center.

          This process has been followed for many other transitions, including [JEP-227|https://github.com/jenkinsci/jep/blob/master/jep/227/README.adoc] and [JEP-233|https://github.com/jenkinsci/jep/blob/master/jep/233/README.adoc].

          The presence of JENKINS-68250, JENKINS-68022, JENKINS-67737, and JENKINS-67176 (two of which remain in the "Open", rather than "In Review" or "Resolved", state at the time of current writing) indicate that such due diligence was not fully performed at the time of integration of JENKINS-68249.

          A systematic search should be done across sources and binaries for all currently supported (non-deprecated) plugins to see if they are affected by the changes introduced in JENKINS-68249. This ticket should be used to track the process of ensuring that each affected plugin gets released prior to shipping the LTS or gets (explicitly) left behind by a conscious decision.
          Basil Crow made changes -
          Epic Name New: Adapt to JENKINS-68249
          Epic Status New: To Do [ 10000 ]
          Issue Type Original: Bug [ 1 ] New: Epic [ 10001 ]
          Basil Crow made changes -
          Summary Original: Due diligence not fully performed for JENKINS-68249 (regression in 2.333) New: Adapt to JENKINS-68249
          Basil Crow made changes -
          Labels Original: regression ux New: ux
          Basil Crow made changes -
          Epic Child New: JENKINS-68250 [ 214876 ]
          Basil Crow made changes -
          Labels Original: ux New: svg-migration ux
          Basil Crow made changes -
          Epic Child New: JENKINS-68022 [ 214598 ]
          Basil Crow made changes -
          Epic Child New: JENKINS-67737 [ 214247 ]

            Unassigned Unassigned
            basil Basil Crow
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated: