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

Compatibility break: AbstractProject does not implement SCMedItem starting from 1.568

    Details

    • Similar Issues:

      Description

      If a external code uses SCMedItem interface to check that the instance has a SCM configuration, this method starts working improperly in 1.568. We have seen this issue in one of internal CloudBees product.

      It's caused by https://github.com/jenkinsci/jenkins/commit/98ee11a28903e3d3003d912f143150bcf1b37c55

        Attachments

          Issue Links

            Activity

            oleg_nenashev Oleg Nenashev created issue -
            oleg_nenashev Oleg Nenashev made changes -
            Field Original Value New Value
            Environment jenkins-1.568+
            oleg_nenashev Oleg Nenashev made changes -
            Priority Minor [ 4 ] Major [ 3 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels compatibility regression
            oleg_nenashev Oleg Nenashev made changes -
            Link This issue is related to JENKINS-29991 [ JENKINS-29991 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 166629 ] JNJira + In-Review [ 182432 ]
            oleg_nenashev Oleg Nenashev made changes -
            Labels compatibility regression compatibility newbie-friendly regression
            oleg_nenashev Oleg Nenashev made changes -
            Assignee Oleg Nenashev [ oleg_nenashev ]
            Hide
            allanc Allan C added a comment -

            Oleg Nenashev Hi Oleg. Should we close this issue? Thank you.

             

            Show
            allanc Allan C added a comment - Oleg Nenashev Hi Oleg. Should we close this issue? Thank you.  
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            We had a Jenkins 2.0 release in 2016, and I doubt anyone plans to fix it after several years. Better to close it indeed

            Show
            oleg_nenashev Oleg Nenashev added a comment - We had a Jenkins 2.0 release in 2016, and I doubt anyone plans to fix it after several years. Better to close it indeed
            oleg_nenashev Oleg Nenashev made changes -
            Status Open [ 1 ] Fixed but Unreleased [ 10203 ]
            Resolution Won't Fix [ 2 ]
            oleg_nenashev Oleg Nenashev made changes -
            Status Fixed but Unreleased [ 10203 ] Closed [ 6 ]
            Hide
            allanc Allan C added a comment -

            Oleg Nenashev Hi Oleg. Thank you for the fast response. I wonder if it is worth fixing. I am looking for a newbie-friendly issue to start with and wonder if this would be an easy and useful issue to work on?

            Show
            allanc Allan C added a comment - Oleg Nenashev Hi Oleg. Thank you for the fast response. I wonder if it is worth fixing. I am looking for a newbie-friendly issue to start with and wonder if this would be an easy and useful issue to work on?
            Hide
            oleg_nenashev Oleg Nenashev added a comment -

            Better to take something newer IMHO

            Show
            oleg_nenashev Oleg Nenashev added a comment - Better to take something newer IMHO

              People

              • Assignee:
                Unassigned
                Reporter:
                oleg_nenashev Oleg Nenashev
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: