bahir-reviews mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ckadner <...@git.apache.org>
Subject [GitHub] bahir issue #32: Update NOTICE
Date Mon, 09 Jan 2017 21:39:45 GMT
Github user ckadner commented on the issue:

    https://github.com/apache/bahir/pull/32
  
    @lresende -- The Pull Request Builder now does the following:
    
    - when a new PR gets created by non-admin user then Jenkins will use the new `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 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)


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message