New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timeout not used if specified in cr_build_yaml() #43
Comments
@dmoimpact what code are you using to try to generate the build? |
(I tried with, and without "" in the seconds.) |
Ok I think its about timeout not the option? In which case yes it currently doesn't respect the timeout if its in cr_build_make(cr_build_yaml(
cr_buildstep_docker("my-image"),
timeout = 500,
options = list(machineType = 'N1_HIGHCPU_8')),
timeout = 777)
#==CloudBuildObject==
#timeout: 777s
#steps:
#- name: gcr.io/cloud-builders/docker
# args:
# ... |
MarkEdmondson1234
changed the title
Check you can add option to create bigger build VM
timeout not used if specified in cr_build_yaml()
Mar 1, 2020
Should be fixed in latest version: cr_build_make(cr_build_yaml(cr_buildstep_docker("my-image"),
timeout = 500,
options = list(machineType = 'N1_HIGHCPU_8')))
# ==CloudBuildObject==
# timeout: 500s
# steps: |
Great, I will try it our. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This should work?
The text was updated successfully, but these errors were encountered: