From dev-return-87573-archive-asf-public=cust-asf.ponee.io@sling.apache.org Tue Mar 20 16:29:13 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 45D2518064A for ; Tue, 20 Mar 2018 16:29:13 +0100 (CET) Received: (qmail 94363 invoked by uid 500); 20 Mar 2018 15:29:07 -0000 Mailing-List: contact dev-help@sling.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@sling.apache.org Delivered-To: mailing list dev@sling.apache.org Received: (qmail 94352 invoked by uid 99); 20 Mar 2018 15:29:07 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 20 Mar 2018 15:29:07 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id D5CDE180DE1 for ; Tue, 20 Mar 2018 15:29:06 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.311 X-Spam-Level: X-Spam-Status: No, score=-110.311 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id gbby9XTgRGyf for ; Tue, 20 Mar 2018 15:29:04 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id EA70A5FBFE for ; Tue, 20 Mar 2018 15:29:02 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 83C49E0D93 for ; Tue, 20 Mar 2018 15:29:01 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 8A846214D1 for ; Tue, 20 Mar 2018 15:29:00 +0000 (UTC) Date: Tue, 20 Mar 2018 15:29:00 +0000 (UTC) From: "Robert Munteanu (JIRA)" To: dev@sling.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (SLING-7551) Summarize CI and PR activity in a weekly email MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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} _edit_: formatting 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 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} > 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} > _edit_: formatting -- This message was sent by Atlassian JIRA (v7.6.3#76005)