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

No way to email just a PR's owner

    XMLWordPrintable

Details

    • 2.88

    Description

      I can't seem to figure out any recipientProviders that contact just a (GitHub) PR's owner/author, in all cases.

      In simple cases, where somebody creates a PR and pushes a few patches, developers seems like the right target.  But as soon as the PR owner merges with master, that becomes every patch owner in the merge also, correct?

      Is there an option I am missing here to achieve what I am looking for?

      Attachments

        Issue Links

          duplicates

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-62074 Send build failure email to approver of pull request

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-44198 Sent email to author participants of a Pull Request

          • Major - Major loss of function.
          • Closed
          relates to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-11759 Allow single user with multiple usernames, therefore allowing same person to be identified

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-62080 PR owner information in Pipeline?

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved

          Activity

            Ascending order - Click to sort in descending order
            View 9 older comments
            kon Kalle Niemitalo added a comment -

            ContributorMetadataAction is defined in scm-api-plugin, and instantiated by gitlab-branch-source-plugin, p4-plugin, bitbucket-branch-source-plugin, and github-branch-source-plugin. A RecipientProvider implementation that reads ContributorMetadataAction would cover all of these. I don't think github-branch-source-plugin would be a good place for it.

            kon Kalle Niemitalo added a comment - ContributorMetadataAction is defined in scm-api-plugin, and instantiated by gitlab-branch-source-plugin, p4-plugin, bitbucket-branch-source-plugin, and github-branch-source-plugin. A RecipientProvider implementation that reads ContributorMetadataAction would cover all of these. I don't think github-branch-source-plugin would be a good place for it.
            kon Kalle Niemitalo added a comment -

            The Email Extension plugin already has a transitive required dependency on the SCM API plugin:

            email-ext -> junit-api -> workflow-api -> scm-api

            kon Kalle Niemitalo added a comment - The Email Extension plugin already has a transitive required dependency on the SCM API plugin: email-ext -> junit-api -> workflow-api -> scm-api
            slide_o_mix Alex Earl added a comment -

            Sorry, I misunderstood your first comment. I agree this should work well.

            slide_o_mix Alex Earl added a comment - Sorry, I misunderstood your first comment. I agree this should work well.
            slide_o_mix Alex Earl added a comment -

            See https://github.com/jenkinsci/email-ext-plugin/pull/361

            slide_o_mix Alex Earl added a comment - See https://github.com/jenkinsci/email-ext-plugin/pull/361
            basil Basil Crow added a comment -

            Fixed in jenkinsci/email-ext-plugin#361. Released in 2.88.

            basil Basil Crow added a comment - Fixed in jenkinsci/email-ext-plugin#361 . Released in 2.88 .

            People

              slide_o_mix Alex Earl
              brianjmurrell Brian J Murrell
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: