You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Robert Munteanu (JIRA)" <ji...@apache.org> on 2018/10/17 08:57:00 UTC
[jira] [Updated] (SLING-8031) Email notifications to dev@sling
should be opt-in for Jenkins jobs
[ https://issues.apache.org/jira/browse/SLING-8031?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Munteanu updated SLING-8031:
-----------------------------------
Description:
We have _many_ build jobs and some of them are failing from time to time. Additionally, INFRA issues mean that jobs can flip back and forth without an actionable task for us as developers.
Therefore I think that only a handful of jobs should actually send email notifications to dev@sling, namely:
- starter
- launchpad-testing
- launchpad-testing-war
I've also proposed this on dev@sling - https://lists.apache.org/thread.html/e50d345ab79d31c1790c0fe20470c437a9abee867e0d5db9a09dbd7a@%3Cdev.sling.apache.org%3E
> Email notifications to dev@sling should be opt-in for Jenkins jobs
> ------------------------------------------------------------------
>
> Key: SLING-8031
> URL: https://issues.apache.org/jira/browse/SLING-8031
> Project: Sling
> Issue Type: Improvement
> Components: Build and Source Control
> Reporter: Robert Munteanu
> Priority: Major
>
> We have _many_ build jobs and some of them are failing from time to time. Additionally, INFRA issues mean that jobs can flip back and forth without an actionable task for us as developers.
> Therefore I think that only a handful of jobs should actually send email notifications to dev@sling, namely:
> - starter
> - launchpad-testing
> - launchpad-testing-war
> I've also proposed this on dev@sling - https://lists.apache.org/thread.html/e50d345ab79d31c1790c0fe20470c437a9abee867e0d5db9a09dbd7a@%3Cdev.sling.apache.org%3E
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)