Topic 1 Question 165
Your company’s corporate policy states that there must be a copyright comment at the very beginning of all source files. You want to write a custom step in Cloud Build that is triggered by each source commit. You need the trigger to validate that the source contains a copyright and add one for subsequent steps if not there. What should you do?
Build a new Docker container that examines the files in /workspace and then checks and adds a copyright for each source file. Changed files are explicitly committed back to the source repository.
Build a new Docker container that examines the files in /workspace and then checks and adds a copyright for each source file. Changed files do not need to be committed back to the source repository.
Build a new Docker container that examines the files in a Cloud Storage bucket and then checks and adds a copyright for each source file. Changed files are written back to the Cloud Storage bucket.
Build a new Docker container that examines the files in a Cloud Storage bucket and then checks and adds a copyright for each source file. Changed files are explicitly committed back to the source repository.
ユーザの投票
コメント(5)
- 正解だと思う選択肢: A
A is the answer.
https://cloud.google.com/build/docs/configuring-builds/pass-data-between-steps#passing_data_using_workspaces To pass data between build steps, store the assets produced by the build step in /workspace and these assets will be available to any subsequent build steps.
👍 3zellck2022/12/16 - 正解だと思う選択肢: B
B is the answer.
https://cloud.google.com/build/docs/configuring-builds/pass-data-between-steps#passing_data_using_workspaces To pass data between build steps, store the assets produced by the build step in /workspace and these assets will be available to any subsequent build steps.
👍 1zellck2022/12/16 - 👍 1TNT872022/12/22
シャッフルモード