Exam Professional Cloud Developer topic 1 question 165 discussion

If a company policy states that every source code should have the copyright comment at the beginning of each file then for every build, we need to scan for each source code file and generate the copyright comments if not there, commit the updated files back to the repository. This is like a prebuild check.

A. 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. This option would allow you to create a custom step in Cloud Build that is triggered by each source commit, which would examine the source files in the /workspace directory, check for the presence of a copyright comment, and add one if not present. By committing the changed files back to the source repository, you ensure that the updated files with the added copyright comment are properly tracked and stored in the source control system.

the code changes must be put back in the workplace folder or the sub other sub-step won't have the changes.

https://cloud.google.com/build/docs/automating-builds/create-manage-triggers Answer 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.

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.