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

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

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.

          [JENKINS-43433] Allow SCMSource implementations to expose merge and origin of change request heads

          Stephen Connolly created issue -
          Stephen Connolly made changes -
          Epic Link New: JENKINS-43426 [ 180671 ]
          Stephen Connolly made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Stephen Connolly made changes -
          Remote Link New: This issue links to "PR#35 (Web Link)" [ 15914 ]
          Stephen Connolly made changes -
          Description New: h1. Acceptance criteria
           * Change requests expose
           ** 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 
          Stephen Connolly made changes -
          Component/s New: bitbucket-branch-source-plugin [ 21428 ]
          Component/s New: branch-api-plugin [ 18621 ]
          Component/s New: github-branch-source-plugin [ 20858 ]
          Stephen Connolly made changes -
          Description Original: h1. Acceptance criteria
           * Change requests expose
           ** 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            		New: h1. Acceptance criteria
           * Change requests expose
           ** 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.
          Stephen Connolly made changes -
          Description Original: h1. Acceptance criteria
           * Change requests expose
           ** 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.           		New: h1. 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.
          Stephen Connolly made changes -
          Status Original: In Progress [ 3 ] New: In Review [ 10005 ]
          James Dumay made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Review [ 10005 ] New: Resolved [ 5 ]
          Stephen Connolly made changes -
          Status Original: Resolved [ 5 ] New: Closed [ 6 ]

            stephenconnolly Stephen Connolly
            stephenconnolly Stephen Connolly
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: