[SLING-7551] Summarize CI and PR activity in a weekly email

• Type: Task
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: Build and Source Control
• Assignee: Unassigned
• Reporter: Robert Munteanu
• Created: 20/Mar/18 15:14
• Updated: 20/Mar/18 15:28

Description

With 250+ repos and Jenkins jobs we are getting a lot of noise related to build failures, PR comments, and it gets easy to forget what is failing and what needs attention. I propose sending weekly emails for:

• Failing CI Jobs
• Open PRs

The emails would go on [e-mail], for maximum visibility.

Failing CI Jobs

The email would include all jobs that

• have failed at least once last week or
• have failed at least once and last status is not successful

The output would be plain-text and include a simple ASCII representation of the last 10 builds, e.g.

1. sling-ide-tooling-1.8
[...!..!!!!]
More: https://builds.apache.org/job/sling-ide-tooling-1.8/

Where '.' is a successful build and '!' is an unstable/failing one.

Open PRs

The email would include all open pull requests.

For each repository we would have a simple plain-text listing of all pull requests, e.g.:

1. sling-site:

PR #2: Update manipulating-content-the-slingpostservlet-servlets-post.md
Age: 41 days
https://github.com/apache/sling-site/pull/2

PR #4: Do something else with the site
Age: 12 days
https://github.com/apache/sling-site/pull/4

edit: formatting