Many organizations have adopted a CI/CD (continuous integration/continuous delivery) pipeline to maintain coding efficiency. Cloud Functions work well in a CI/CD environment and can be implemented as such through a Google Cloud service, Cloud Build. In this hands-on lab, you’ll gain the practical experience of setting up the Cloud Source Repository, Cloud Functions, and Cloud Build services to implement a CI/CD pipeline.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Enable APIs
- From the Google Cloud console’s main navigation, visit APIs & Services > Library to enable the following services:
- Cloud Functions
- Source Repositories
- Cloud Build
- Cloud Resource Manager API
- From the Google Cloud console’s main navigation, visit APIs & Services > Library to enable the following services:
- Create a Google Cloud Source Repository
Activate a Cloud Shell.
Create a Source Repository:
gcloud source repos create gcpro_repoClone the repository to the shell:
gcloud source repos clone gcpro_repoClone repository from GitHub:
git clone https://github.com/linuxacademy/content-gcpro-developerCopy files to shell repo:
cp content-gcpro-developer/cicd-lab/* gcpro_repocd gcpro_repo
- Move Files to Source Repository
Use the following commands to commit the files in the shell repo to the newly created Source Repository:
git remote add google https://source.developers.google.com/p/[PROJECT_ID]/r/gcpro_repo git add . git config --global user.email "[EMAIL_ADDRESS]" git config --global user.name "[NAME]" git commit -m "Initial Commit" git push --all googleVisit the Source Repositories dashboard and click
gcpro_repoto confirm the files.
- Create Cloud Function
- From the main navigation, go to Cloud Functions.
- Choose Create function.
- Configure your function with the following values:
- Environment: 1st gen
- Name: repo-function-1
- Trigger: HTTP
- Authentication: Allow unauthenticated invocations
- Click Save
- Under Runtime, build, connections and security settings:
- Maximum number of instances: 1
- Click Next
- Source Code: Cloud Source repository
- Runtime: Python 3.7
- Repository: gcpro_repo
- Entry point: greetings_http
- Leave all other fields with their default values and click Deploy.
- Once the function spins up, click to open it.
- Select the Trigger tab, and click the listed URL. It will open a new window with the default greeting.
- Back in the GCP console, click the Testing tab.
- In the Triggering window, enter
{"name":"<YOUR_NAME>"} - Click Test the function.
- In the Output box, note the results.
- Set IAM Permissions
- From the navigation, go to Cloud Build > Settings.
- In the Service Account Permissins section, change the status of the Cloud Functions Developer role to Enabled.
- In the Additional steps may be required dialog, choose Grant Access to All Service Accounts.
- Note that the status of the Service Account User role has changed to Enabled.
- Define a Cloud Build Trigger
- From the side navigation of the Cloud Build console, go to Triggers.
- Click Create trigger.
- Set the following values:
- Repository: gcpro_repo.
- Name: trigger-1
- Build configuration: Cloud Build configuration file (yaml or json)
- Make sure Cloud Build configuration file location autopopulates with / cloudbuild.yaml.
- Leave all other fields with their default values, and click Create.
- Verify Trigger
- From the Cloud Build Triggers page, click the Run Trigger option associated with the newly defined trigger.
- Test the trigger by using the Cloud Shell editor to alter the
main.pyfile and pushing to the Source Repository. - Visit Cloud Build > History and, if necessary, refresh the page to confirm the new build.
