[
https://issues.apache.org/jira/browse/BEAM-8422?focusedWorklogId=335471&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-335471
]
ASF GitHub Bot logged work on BEAM-8422:
----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Oct/19 10:36
Start Date: 29/Oct/19 10:36
Worklog Time Spent: 10m
Work Description: lgajowy commented on issue #9816: [BEAM-8422] Notify
builds@ on ABORTED job final state
URL: https://github.com/apache/beam/pull/9816#issuecomment-547357873
@kkucharc could you take a look as well?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 335471)
Time Spent: 40m (was: 0.5h)
> Send emails to builds@ when job ends with state "ABORTED"
> ---------------------------------------------------------
>
> Key: BEAM-8422
> URL: https://issues.apache.org/jira/browse/BEAM-8422
> Project: Beam
> Issue Type: Improvement
> Components: testing
> Reporter: Lukasz Gajowy
> Priority: Minor
> Time Spent: 40m
> Remaining Estimate: 0h
>
> I noticed that timeouting jobs end up in an ABORTED state (black dot on the
> Jenkins dashboard). No email is sent to the builds@ list when this happens.
> It reduces the visibility of a problem - if one relies on builds@ they won't
> see that Jenkins job takes too much time.
>
> At the time of writing, 5 jobs are affected:
> beam_PostCommit_Java11_ValidatesRunner_Dataflow_PR
> beam_PostCommit_Java11_ValidatesRunner_PortabilityApi_Dataflow
> beam_PostCommit_Java_PVR_Spark_Batch
> beam_PostCommit_Python37_PR
> beam_sonarqube_report
>
> I propose changing this behavior and send emails to builds@ when job ends
> with ABORTED state.
> The drawback of this solution is that every time someone aborts the job
> manually the email will be sent too - there's no way to distinguish those
> two situations. However, IMO we should not allow timeouts to be unnoticed and
> manual job aborting does not happen very often (even committers cannot do
> that now in Jenkins).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
