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

Sent email to author participants of a Pull Request

XMLWordPrintable

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major Major
    • plugin-proposals
    • None
    • Jenkins 2.46.2
    • 2.88

      It is possible to send email to DevelopersRecipientProvider, etc.

      It should also be possible to send email to GitHub Pull Request participants.

      Use case: developer submits Pull Request. Later he merges master to feature branch and waits for tests to be passed to merge Pull Request. It should be possible to notify Pull Request participants only when testing is finished. (DevelopersRecipientProvider would notify all the authors of commits merged from master)

          [JENKINS-44198] Sent email to author participants of a Pull Request

          Alex Earl added a comment -

          This would either need to be a separate plugin, or incorporated as part of whatever GH plugin you are using. email-ext provides an extension point (RecipientProvider) that other plugins can implement to provide their own recipient providers.

          Alex Earl added a comment - This would either need to be a separate plugin, or incorporated as part of whatever GH plugin you are using. email-ext provides an extension point (RecipientProvider) that other plugins can implement to provide their own recipient providers.

          Alex Earl added a comment -

          I believe this is now implemented as the ContributorMetadataRecipientProvider. You can use contributor() is pipeline scripts to get to the creator of the PR. Released in 2.88.

          Alex Earl added a comment - I believe this is now implemented as the ContributorMetadataRecipientProvider. You can use contributor() is pipeline scripts to get to the creator of the PR. Released in 2.88.

            Unassigned Unassigned
            vorobievalex Alexander Vorobiev
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: