[
https://issues.apache.org/jira/browse/BEAM-11312?focusedWorklogId=519185&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-519185
]
ASF GitHub Bot logged work on BEAM-11312:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Dec/20 18:28
Start Date: 02/Dec/20 18:28
Worklog Time Spent: 10m
Work Description: y1chi commented on pull request #13399:
URL: https://github.com/apache/beam/pull/13399#issuecomment-737412745
> Would it be possible to mention that caching is used when it is rather
when it is not? Or perhaps add a generic info message along the lines of:
`Staging pipeline dependencies into a prebuilt container image. To optimize
build time, build steps will be cached.`
>
> Also do you know if a user can tell Kaniko to clean the cache manually?
Whether cache is used in the docker build will be apparent in the build log
and I think it will be more accurate than what we can log in beam workflow, see:
- use cache:
https://pantheon.corp.google.com/cloud-build/builds/8ee579d4-aa86-4c40-bb98-59d65160e223?project=beam-cloud-build-test
- no cache layer found:
https://pantheon.corp.google.com/cloud-build/builds/89f57168-b6e5-4327-a574-82e0767b4600?project=beam-cloud-build-test
I don't know if user can tell directly clean the cache but caching can
always be avoided if user specifies a more specific docker registry push url.
(the caching scoped to push url for example if user pushes to
gcr.io/project/sdk_container_version_1/beam_python_prebuilt_sdk:tag, the cache
will only exist if user build container with the same
`gcr.io/project/sdk_container_version_1` docker_registry_push_url)
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 519185)
Time Spent: 3h (was: 2h 50m)
> When prebuilding workflow on CloudBuild fails, we should tell the user where
> to look for build logs, ideally a link, or a pointer where the build logs are.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: BEAM-11312
> URL: https://issues.apache.org/jira/browse/BEAM-11312
> Project: Beam
> Issue Type: Improvement
> Components: sdk-py-core
> Reporter: Valentyn Tymofieiev
> Assignee: Yichi Zhang
> Priority: P2
> Time Spent: 3h
> Remaining Estimate: 0h
>
> Current error does not have context:
> ...
> /apache_beam/runners/portability/sdk_container_builder.py", line 242, in
> invoke_docker_build_and_push
> result = operation.result()
> File
> "/usr/local/google/home/valentyn/.pyenv/versions/py37prebuild/lib/python3.7/site-packages/google/api_core/future/polling.py",
> line 134, in result
> raise self._exception
> google.api_core.exceptions.Unknown: None Build failed;
> check build logs for details
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
