[jira] [Commented] (OOZIE-3637) Find out why the the pre-commit build is not started when a new patch is available on a Jira

["Dénes Bodó (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/OOZIE-3637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17438660#comment-17438660 ] 

Dénes Bodó commented on OOZIE-3637:
-----------------------------------

I could not reproduce the issue, build starts when Jira is in PATCH AVAILABLE state and there is a patch uploaded with name like OOZIE-1234-001.patch

> Find out why the the pre-commit build is not started when a new patch is available on a Jira
> --------------------------------------------------------------------------------------------
>
>                 Key: OOZIE-3637
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3637
>             Project: Oozie
>          Issue Type: Bug
>            Reporter: Dénes Bodó
>            Assignee: Dénes Bodó
>            Priority: Critical
>              Labels: infrastructure
>         Attachments: OOZIE-3637-001.patch
>
>
> *Symptom*:
> When I upload a new diff/patch file to an OOZIE-XYZ Jira ticket and then push the "Patch available" button the pre-commit build does not start automatically: [https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build]
>  
> *Task*:
> Find out what causes this and fix the problem.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)