[
https://issues.apache.org/jira/browse/BEAM-6011?focusedWorklogId=166393&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-166393
]
ASF GitHub Bot logged work on BEAM-6011:
----------------------------------------
Author: ASF GitHub Bot
Created on: 15/Nov/18 11:32
Start Date: 15/Nov/18 11:32
Worklog Time Spent: 10m
Work Description: lgajowy commented on issue #7021: [BEAM-6011] Phrase
triggering nexmark
URL: https://github.com/apache/beam/pull/7021#issuecomment-439009924
I think developers can compare the results of PR triggered job printed to
the job console output with graphs
[here](https://apache-beam-testing.appspot.com/dashboard-admin), am I right?
This may require some logs searching though (might be cumbersome).
Another idea that I have is to copy the plots for periodic jobs but add
another line (set of datapoints) in different color on them for PR jobs.
Invalid results would be then super visible on the plots. We could also think
of ways of displaying this stuff in the PR directly (I don't know yet how,
though)...
What do you all think about this?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 166393)
Time Spent: 3h 40m (was: 3.5h)
> 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
> Time Spent: 3h 40m
> Remaining Estimate: 0h
>
> 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)
