Skip to content

Commit

Permalink
Add details for submitting PRPQR without PR info
Browse files Browse the repository at this point in the history
  • Loading branch information
smg247 committed Feb 16, 2024
1 parent 3e53309 commit 206d3d8
Showing 1 changed file with 21 additions and 0 deletions.
21 changes: 21 additions & 0 deletions content/en/docs/release-oversight/payload-testing.md
Expand Up @@ -89,6 +89,11 @@ spec:
repo: kubernetes
```

{{% alert title="WARNING" color="warning" %}}
If multiple `pullRequests` entries are supplied for a single org/repo pair, the `baseRef` and `baseSHA` will be selected only from the first one in the list.
Therefore, it is not supported to have differing entries for these.
{{% /alert %}}

#### Supplying Multiple PRs from Component Repositories
The `ci-operator` can assemble a release payload by building and using images from multiple PRs in OCP component repos.
In order to do this, refs for each PR must be provided in the `PRPQR` spec:
Expand Down Expand Up @@ -146,3 +151,19 @@ spec:
tag: "4.13-2024-02-04-192545" # ImageStream name in the 'ocp' namespace to override to
...
```

#### Sourcing Components from Specific Base
A `PRPQR` can be submitted without referencing an open PR. This is useful to pin one or more component repos to a specific `baseRef` and `baseSHA` in order to test the state of things at that point.
Doing so requires manually applying the `PRPQR` CR:
```yaml
...
spec:
jobs:
...
pullRequests:
- baseRef: master
baseSHA: 270de19d62fc7275f22de22a7eca270bd77dd05d
org: openshift
repo: kubernetes
...
```

0 comments on commit 206d3d8

Please sign in to comment.