[ 
https://issues.apache.org/jira/browse/BEAM-9250?focusedWorklogId=387008&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-387008
 ]

ASF GitHub Bot logged work on BEAM-9250:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Feb/20 00:59
            Start Date: 14/Feb/20 00:59
    Worklog Time Spent: 10m 
      Work Description: markflyhigh commented on issue #10772: [BEAM-9250] 
Re-structure python release candidate target.
URL: https://github.com/apache/beam/pull/10772#issuecomment-586046427
 
 
   Thank you for looking into release improvement! This gives people a lot more 
flexibility to (re)run single test.
   
   However, I have few concerns about split the split. Running 16 jobs add 
extra manual work for release manager in triggering and tracking. Also our 
Jenkins cluster has limited slots, run them at same time may increase the 
waiting queue, especially some mobile-gaming tests require 30+ mins. 
   
   I feel it's a really hard trade off. What do you think?
 
----------------------------------------------------------------
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:
us...@infra.apache.org


Issue Time Tracking
-------------------

    Worklog Id:     (was: 387008)
    Time Spent: 1h 40m  (was: 1.5h)

> Improve beam release script based on 2.19.0 release experience
> --------------------------------------------------------------
>
>                 Key: BEAM-9250
>                 URL: https://issues.apache.org/jira/browse/BEAM-9250
>             Project: Beam
>          Issue Type: Improvement
>          Components: testing
>            Reporter: Boyuan Zhang
>            Assignee: Boyuan Zhang
>            Priority: Major
>             Fix For: 2.20.0
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>




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

Reply via email to