Select {{ $ctrl.namespaceTitle }}

Please select the {{ $ctrl.namespaceTitle }} under which the repository lives

	{{ $ctrl.namespaceTitle }}	Importance
	{{ namespace.id }}

No matching {{ $ctrl.namespaceTitle }} found.

Try expanding your filtering terms.

Retrieving {{ $ctrl.namespaceTitle }}s

has been granted access to read and view these {{ $ctrl.namespaceTitle }}s.

Don't see an expected {{ $ctrl.namespaceTitle }} here? Please make sure third-party access is enabled for under that {{ $ctrl.namespaceTitle }}.

Select Repository

Select a repository in {{ $ctrl.local.selectedNamespace.id }}

	Repository Name	Last Updated	Description
	{{ repository.name }}		{{ repository.description }} (None)

No matching repositories found.

Try expanding your filtering terms.

Retrieving repositories

A webhook will be added to the selected repository in order to detect when new commits are made.

Don't see an expected repository here? Please make sure you have admin access on that repository.

Configure Trigger

Configure trigger options for {{ $ctrl.local.selectedNamespace.id }}/{{ $ctrl.local.selectedRepository.name }}

Trigger for all branches and tags (default)

Build a container image for each commit across all branches and tags

Trigger only on branches and tags matching a regular expression

Only build container images for a subset of branches and/or tags.

Regular Expression:

Examples: heads/master, tags/tagname, heads/.+

Retrieving repository refs

Do you want to build a new container image for commits across all branches and tags, or limit to a subset?

For example, if you use release branches instead of master for building versions of your software, you can configure the trigger to only build images for these branches.

All images built will be tagged with the name of the branch or tag whose change invoked the trigger

Select Dockerfile

Please select the location of the Dockerfile to build when this trigger is invoked

Retrieving Dockerfile locations

Please select the location containing the Dockerfile to be built.

Select Context

Please select the context for the docker build

Retrieving Dockerfile locations

Please select a docker context.

Verification Error

There was an error when verifying the state of {{ $ctrl.local.selectedNamespace.id }}/{{ $ctrl.local.selectedRepository.name }} {{ $ctrl.local.triggerAnalysis.message }}

Verification Warning

Ready to go!

Choose an optional robot account below or click "Continue" to complete setup of this build trigger Click "Continue" to complete setup of this build trigger

Robot Account Required

The selected Dockerfile in the selected repository depends upon a private base image

A robot account with access to the base image is required to setup this trigger, but you are not the administrator of this namespace.

Administrative access is required to continue to ensure security of the robot credentials.

	Robot Account	Has Read Access
		Can Read Read access will be added if selected

No matching robot accounts found.

Try expanding your filtering terms.

In order for the to pull a private base image during the build process, a robot account with access must be selected.

If you know that a private base image is not used, you can skip this step.

Robot accounts that already have access to this base image are listed first. If you select a robot account that does not currently have access, read permission will be granted to that robot account on trigger creation.