How can you implement a custom Cloud Build step that triggers on each source commit to validate the presence of a copyright comment at the beginning of source files and automatically add one if missing, in compliance with your company's policy?

Exam-Like

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.

65.9%

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.

11.4%

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.

11.4%

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.

11.4%

Google Professional Cloud Developer

Get started today

Comments

How can you implement a custom Cloud Build step that triggers on each source commit to validate the presence of a copyright comment at the beginning of source files and automatically add one if missing, in compliance with your company's policy?