[
https://issues.apache.org/jira/browse/BEAM-5719?focusedWorklogId=153672&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-153672
]
ASF GitHub Bot logged work on BEAM-5719:
----------------------------------------
Author: ASF GitHub Bot
Created on: 11/Oct/18 19:58
Start Date: 11/Oct/18 19:58
Worklog Time Spent: 10m
Work Description: swegner opened a new pull request #6660: [BEAM-5719]
Use gcs rsync and validate that a valid baseUrl is specified
URL: https://github.com/apache/beam/pull/6660
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.
This change ensures that a valid baseUrl is provided before running
gsutil commands, and uses rsync instead of gsutil rm && gsutil cp. This
is both safer and more efficient.
------------------------
Follow this checklist to help us incorporate your contribution quickly and
easily:
- [ ] Format the pull request title like `[BEAM-XXX] Fixes bug in
ApproximateQuantiles`, where you replace `BEAM-XXX` with the appropriate JIRA
issue, if applicable. This will automatically link the pull request to the
issue.
- [ ] If this contribution is large, please file an Apache [Individual
Contributor License Agreement](https://www.apache.org/licenses/icla.pdf).
It will help us expedite review of your Pull Request if you tag someone
(e.g. `@username`) to look at it.
Post-Commit Tests Status (on master branch)
------------------------------------------------------------------------------------------------
Lang | SDK | Apex | Dataflow | Flink | Gearpump | Samza | Spark
--- | --- | --- | --- | --- | --- | --- | ---
Go | [](https://builds.apache.org/job/beam_PostCommit_Go_GradleBuild/lastCompletedBuild/)
| --- | --- | --- | --- | --- | ---
Java | [](https://builds.apache.org/job/beam_PostCommit_Java_GradleBuild/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Apex_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Flink_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Gearpump_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Samza_Gradle/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Spark_Gradle/lastCompletedBuild/)
Python | [](https://builds.apache.org/job/beam_PostCommit_Python_Verify/lastCompletedBuild/)
| --- | [](https://builds.apache.org/job/beam_PostCommit_Py_VR_Dataflow/lastCompletedBuild/)
</br> [](https://builds.apache.org/job/beam_PostCommit_Py_ValCont/lastCompletedBuild/)
| [](https://builds.apache.org/job/beam_PostCommit_Python_VR_Flink/lastCompletedBuild/)
| --- | --- | ---
----------------------------------------------------------------
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: 153672)
Time Spent: 10m
Remaining Estimate: 0h
> 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: 10m
> 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)
