[
https://issues.apache.org/jira/browse/SLING-7551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Munteanu updated SLING-7551:
-----------------------------------
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 dev@sling.apache.org, 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.
{noformat}
1. sling-ide-tooling-1.8
[...!..!!!!]
More: https://builds.apache.org/job/sling-ide-tooling-1.8/
{noformat}
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.:
{noformat}
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
{noformat}
was:
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
** 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.
{noformat}
1. sling-ide-tooling-1.8
[...!..!!!!]
More: https://builds.apache.org/job/sling-ide-tooling-1.8/
{noformat}
** 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.:
{noformat}
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
{noformat}
> Summarize CI and PR activity in a weekly email
> ----------------------------------------------
>
> Key: SLING-7551
> URL: https://issues.apache.org/jira/browse/SLING-7551
> Project: Sling
> Issue Type: Task
> Components: Build and Source Control
> Reporter: Robert Munteanu
> Priority: Major
>
> 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 dev@sling.apache.org, 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.
> {noformat}
> 1. sling-ide-tooling-1.8
> [...!..!!!!]
> More: https://builds.apache.org/job/sling-ide-tooling-1.8/
> {noformat}
> 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.:
> {noformat}
> 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
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
