Allow SCMSource implementations to expose merge and origin of change request heads

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

      Acceptance criteria

      • Change requests as implemented in the SCM API expose to consumer code
        • the merge strategy
        • the origin
        • the origin branch name
      • In order to retain binary compatibility, some of this information may only be available / correct when the corresponding SCM API implementation plugin has been updated.
      • The Branch API plugin has been updated with tests of any new significant code paths relating to branch discovery
      • The Branch API plugin exposes the origin and origin branch name when such information is provided by the corresponding SCM API implementation plugin.
      • The GitHub Branch Source plugin has been updated to expose the new change request information.
        • Upgrading from the 2.x.y series of the GitHub Branch Source shall not trigger a rebuild storm.
        • Upgrading from the 1.x series of the GitHub Branch Source should make best effort not to trigger a rebuild storm.
      • The Bitbucket Branch Source plugin has been updated to expose the new change request information
        • Upgrading from the 2.x.y series of the Bitbucket Branch Source shall not trigger a rebuild storm.
        • Upgrading from the 1.x series of the Bitbucket Branch Source should make best effort not to trigger a rebuild storm.
      • The SCM API's implementer guide has been updated to reflect the new recommendations for implementing change requests.

            Assignee:
            Stephen Connolly
            Reporter:
            Stephen Connolly
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: