[ 
https://issues.apache.org/jira/browse/BEAM-6011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lukasz Gajowy updated BEAM-6011:
--------------------------------
    Description: 
We need to enable Phrase Triggering (running Jenkins jobs from PR) for Nexmark 
jobs so that we could check if pull requests are not breaking anything before 
merging them. 

*Note*: Currently Nexmark jobs run post commit on master and publish their 
results to BigQuery database. In order not to pollute the results collected for 
master we should save the results for Pr-triggered jobs in some other 
tables/datasets or even not save them at all (turn off publishing to BQ).

  was:
We need to enable Phrase Triggering (running Jenkins jobs from PR) for Nexmark 
jobs so that we could check if pull requests are not breaking anything before 
merging them. 

Note: Currently Nexmark jobs run post commit on master and publish their 
results to BigQuery database. In order not to pollute the results collected for 
master we should save the results for Pr-triggered jobs in some other 
tables/datasets or even not save them at all (turn off publishing to BQ).


> Enable Phrase triggering in Nexmark jobs
> ----------------------------------------
>
>                 Key: BEAM-6011
>                 URL: https://issues.apache.org/jira/browse/BEAM-6011
>             Project: Beam
>          Issue Type: Bug
>          Components: testing
>            Reporter: Lukasz Gajowy
>            Assignee: Lukasz Gajowy
>            Priority: Critical
>
> We need to enable Phrase Triggering (running Jenkins jobs from PR) for 
> Nexmark jobs so that we could check if pull requests are not breaking 
> anything before merging them. 
> *Note*: Currently Nexmark jobs run post commit on master and publish their 
> results to BigQuery database. In order not to pollute the results collected 
> for master we should save the results for Pr-triggered jobs in some other 
> tables/datasets or even not save them at all (turn off publishing to BQ).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to