Manually build code in source repositories  |  Cloud Build Documentation  |  Google Cloud (2024)

Console

To create a manual trigger:

1. Open the Triggers page:

   Open the Triggers page

2. Select your project from the top of the page and click Open.

3. Click Create trigger.

4. Enter the following trigger settings:

   • Name: A name for your trigger.

   • Region: Select the region for your trigger.

     • If you select global as the region,Cloud Build uses the defaultpool to run your build.
     • If you select a non-global region and thebuild config file associated with the triggerspecifies a private pool, Cloud Build uses the privatepool to run your build. In this case, the region you specify in your trigger must match the region where you created your private pool.
     • If you select a non-global region and thebuild config file associated with the triggerdoes not specify a private pool,Cloud Build uses the defaultpool to run your build in the same regionas your trigger.

   • Description (Optional): A description for your trigger.

   • Event: Select Manual invocation to set up your trigger so that buildsonly run when the trigger is manually invoked.

     See Also

     Jenkins Tutorial - Part 8 - Triggering Pipeline | Kubedemy

   • Source: Select the repository to build when the manual trigger runs. You can specify 1st generation or 2nd generation as your source.

   • Revision: Select the branch or tag to build when the manual triggerruns.

   • Branch: Set a trigger to build on this branch.You must specify a literal value. Regular expressions are not currentlysupported.

   • Tag: Set a trigger to build on this tag. You must specify a literalvalue. Regular expressions are not currently supported.

   • Configuration: Select the build config file located inyour remote repository or create an inline build config file touse for your build.

     • Type: Select the type of configuration to use for your build.
       • Cloud Build configuration file (yaml or json):Use a build config file for your configuration.
       • Dockerfile: Use a Dockerfile for your configuration.

     • Location: Specify the location for your configuration.

       • Repository: If your config file is located in yourremote repository, provide the location of yourbuild config file, the Dockerfiledirectory, or the buildpacks directory. If your build configtype is a Dockerfile or a buildpack, you will need to providea name for the resulting image and optionally, a timeout for yourbuild. When you've provided the Dockerfile or buildpackimage name, you'll see a preview of the docker build orpack command that your build will execute.
       • Inline: If you selectedCloud Build configuration file (yaml or json) as your configuration option, you can specify your build config inline. Click Open Editor to write your build config file in the Google Cloud console using YAML or JSON syntax. Click Done to save your build config.

5. Click Create to create your manual trigger.

gcloud

For a complete list of flags, see the gcloud reference for how to create manual triggers.

Console

To run a manual trigger using Google Cloud console:

1. Open the Triggers page in the Google Cloud console.

   Open the triggers page

2. Locate your trigger in the list.

3. Click Run trigger.

   After clicking Run trigger, you will see the Run trigger window paneon the right side. If you specified fields such as a branch name, tagname, or substitution variables, you will be able to override these fieldsat invocation time.

   If you specified new variable values for your substitution, click Run triggerto execute your build.

   To run manual triggers on schedule, seeScheduling builds.

gcloud

To run a manual trigger using the gcloud command-line tool, run the followingcommand:

 gcloud builds triggers run TRIGGER_NAME \ --region=REGION \ --branch=BRANCH_NAME \ --substitutions=SUBSTITUTION_VAR=SUBSTITUTION_VALUE

Where:

• TRIGGER_NAME is the name of your trigger.
• REGION is the region for your trigger.
• BRANCH_NAME is the name of your branch. You canalso specify a tag using --tag or a commit ID using --sha.
• [Optional]SUBSTITUTION_VAR is the variable name for your substitution value.
• [Optional] SUBSTITUTION_VALUE is the value associated with your substitution variable.

To run manual triggers on schedule, see Scheduling builds.