Skip to content

Latest commit

 

History

History
 
 

transfigure

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
 
 
 
 
 
 
 
 
 
 
 
 

Transfigure.sh

Transfigure is deprecated in favor of Config Merger. See Migration for details

Transfigure is an image that generates a YAML TestGrid configuration from a Prow configuration and pushes it to be used on testgrid.k8s.io. It is used specifically for Prow instances other than the k8s instance of Prow.

Migration

Transfigure was made to let other Prow instances use TestGrid, but Config Merger can do the same thing without requiring periodic PR approval.

When switching from Transfigure to Config Merger, avoid missing or duplicate TestGrid entries in this way:

  1. Add your Configurator jobs (like this example) to your Prow instance.
  2. In the same PR, in this repository, add your instance to the mergelists and delete the gen-config.yaml file that Transfigure has been maintaining.
  3. Delete any leftover Transfigure jobs and close any leftover Transfigure PRs.

Arguments

transfigure.sh takes several arguments.

  • [github_token] : A GitHub personal access token that has been granted the repo access scope. This is usually a robot token mounted as a volume, as the example above illustrates. Ensure that this user has signed the CLA to contribute to this repository.
  • [prow_config]: Prow's* Config path
  • [prow_job_config]: Prow's* Job Config path
  • [testgrid_yaml]: TestGrid configuration directory or default file
  • [repo_subdir]: The subdirectory in /config/testgrids/... to push to. Usually <github_org> or <github_org>/<github_repository>.
  • (remote_fork_repo): Your user needs to have a fork of kubernetes/test-infra. If it does, but that fork isn't named test-infra, specify the name here. This is usually because your user already has a different repo as test-infra when kubernetes/test-infra was forked.

*"Prow" refers to your non-k8s Prow instance

Building

The gcr.io/k8s-prow/transfigure image is built and published automatically by post-test-infra-push-prow with the rest of the Prow components.

You can build the image locally and use it in Docker. Publish to a remote repository after building with docker push or build and push all Prow images at once with prow/push.sh.