Tracks changes to repo projects.
This is not an official Google product.
Define a new resource type for your pipeline:
resource_types:
- name: repo
type: registry-image
source:
repository: docker.io/<dockerhub-username>/repo-resource
-
manifest_url
: Required. The URL of the repo manifest repository. (See:--manifest-url
inrepo init --help
.) -
manifest_name
: The name of the manifest file to use. (See:--manifest-name
inrepo init --help
.) -
manifest_branch
: The name of the manifest repository branch. (See:--manifest-branch
inrepo init --help
.) -
groups
: An array of manifest group names to use. (See:--groups
inrepo init --help
.) -
init_options
andsync_options
: A map ofrepo init
orrepo sync
option names (full names only, without--
) to option values. Values may be strings, numbers, or booleans (wheretrue
represents setting a valueless flag option andfalse
represents unsetting an option). These options will override any other option, including hardcoded defaults. Be careful! This is an advanced feature that can break the resource! (See:repo init --help
andrepo sync --help
.)
repo init
and repo sync
are called with the provided options. repo manifest
is used to take a snapshot of the state of the repositories, which is
used as the resource version.
repo init
and repo sync
are called with the provided options, using the
provided version as the manifest. This results in a snapshot of the project
repositories.
This resource does not implement out
.
resource_types:
- name: repo
type: registry-image
source:
repository: docker.io/<dockerhub-username>/repo-resource
resources:
- name: example-repo
type: repo
source:
manifest_url: https://source.example.com/manifest.git
groups:
- tests
jobs:
- name: example-ci
plan:
- get: example-repo
trigger: true
- task: example-ci
file: example-repo/testing/ci.yml