Github user ApacheBahir commented on the issue:

    https://github.com/apache/bahir/pull/31
  
    Hi Luciano,
    
    the Pull Request Builder now does the following:
    
          when a new PR gets created by a non-admin user then Jenkins will use
          the ApacheBahir user to post "Can one of the admins verify this
          patch?" for which I will receive an email notification
                admin users are determined by a Jenkins setting with list of
                GitHub user names, current admins are you, Alan and myself
          if an admin creates a new PR, Jenkins will start a build right away
          once a build completes the ApacheBahir user will post that the build
          is finished and post a link to the build results
          an admin can whitelist the PR creator
          admins or whitelisted users can trigger (re)builds with the standard
          phrases like "ok to test" or "retest this please"
          new commits pushed to a previously tested PR trigger rebuilds
    
          things that still don't work:
                including the build status (Success, Failure, Error) in the
                posted comment
                posting build logs or build log portions (i.e. the last 20
                lines of the maven build output)
    
    Best regards,
    Christian Kadner
    
--------------------------------------------------------------------------------------
    
    Software Developer, IBM Spark Technology Center
    [email protected], (415) 979-1236
    
--------------------------------------------------------------------------------------
    
    
    
    From:       Luciano Resende <[email protected]>
    To: apache/bahir <[email protected]>
    Cc: Apache Bahir <[email protected]>, Comment
                <[email protected]>
    Date:       01/06/2017 10:35 PM
    Subject:    Re: [apache/bahir] Update NOTICE for 2017 (#31)
    
    
    
    @ckadner @akchinSTC Can we get a link to the build results as well ?
    
    
    —
    You are receiving this because you commented.
    Reply to this email directly, view it on GitHub, or mute the thread.
    
    
    
    
    



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---

Reply via email to