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

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

                Author: ASF GitHub Bot
            Created on: 11/Oct/18 19:59
            Start Date: 11/Oct/18 19:59
    Worklog Time Spent: 10m 
      Work Description: swegner commented on issue #6660: [BEAM-5719] Use gcs 
rsync and validate that a valid baseUrl is specified
URL: https://github.com/apache/beam/pull/6660#issuecomment-429097510
 
 
   R: @akedin @alanmyrvold 

----------------------------------------------------------------
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: 153673)
    Time Spent: 20m  (was: 10m)

> Misconfigured GCS staging jobs can nuke entire top-level bucket
> ---------------------------------------------------------------
>
>                 Key: BEAM-5719
>                 URL: https://issues.apache.org/jira/browse/BEAM-5719
>             Project: Beam
>          Issue Type: Sub-task
>          Components: build-system, website
>            Reporter: Scott Wegner
>            Assignee: Scott Wegner
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> See: https://github.com/apache/beam/pull/6655#issuecomment-429037632
> A bug in the Website_Stage_GCS job was causing the Jenkins job to wipe out 
> the top-level GCS bucket used to stage and serve the website from. This ends 
> up blocking all future runs of the job and takes manual effort to recreate 
> and configure the bucket.
> The linked PR should fix the immediate issue, but it's still the case that a 
> bug in the job/configuration could potentially wipe it out again. We should 
> refactor the job or modify the command so that there is no longer danger of 
> wiping it out.



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

Reply via email to