Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update PROW CI developer documentation #1455

Open
mateusoliveira43 opened this issue Jul 10, 2024 · 2 comments
Open

Update PROW CI developer documentation #1455

mateusoliveira43 opened this issue Jul 10, 2024 · 2 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@mateusoliveira43
Copy link
Contributor

Update

### Update Go version
To update the Go version used in CI jobs of a branch:
- Update the image used in `build_root` instruction of ALL jobs of that branch.
> **Note:** images referenced in `build_root` instruction ([which creates `root` image, that is tagged into `src`](https://docs.ci.openshift.org/docs/internals/)) of the config files, are defined in [here](https://github.com/openshift-eng/ocp-build-data/tree/main), under the specific branch. For example, `openshift-4.14` images are defined [here](https://github.com/openshift-eng/ocp-build-data/blob/openshift-4.14/streams.yml). The OCP version of this images do NOT have to be the same as the OCP version that the job is being tested against. We only care about the `Go` version in these images. But we DO have to use the same image between the jobs of the same branch, for consistency.
**TODO automate this process**

As it is not valid anymore after openshift/release#52892 (comment)

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 9, 2024
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

3 participants