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

Re-Configure renovate bot for devfile/registry #1660

Open
2 tasks
thepetk opened this issue Dec 16, 2024 · 4 comments
Open
2 tasks

Re-Configure renovate bot for devfile/registry #1660

thepetk opened this issue Dec 16, 2024 · 4 comments
Labels
area/ci area/registry Devfile registry for stacks and infrastructure

Comments

@thepetk
Copy link
Contributor

thepetk commented Dec 16, 2024

Which area is this issue related to?

/area ci
/area registry

Issue Description

After our onboarding to konflux we are receiving a slightly bigger number of PRs opened by the konflux bot. We might want to configure the new bot in a way that brings less noise with new updates

Acceptance Criteria

  • The old redhat renovate bot has been removed
  • The konflux renovate bot follow the same configuration with the old bot
@openshift-ci openshift-ci bot added area/ci area/registry Devfile registry for stacks and infrastructure labels Dec 16, 2024
@thepetk thepetk moved this to Refinement in Devfile Project Dec 16, 2024
@thepetk
Copy link
Contributor Author

thepetk commented Dec 17, 2024

Regarding the case that the new bot creates two PRs for the same image, I noticed it was coming from two different bots. Example:

@michael-valdron
Copy link
Member

Regarding the case that the new bot creates two PRs for the same image, I noticed it was coming from two different bots. Example:

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v9 registry#517](https://github.com/devfile/registry/pull/517)

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v1-1733173511 registry#519](https://github.com/devfile/registry/pull/519)

@thepetk First one is renovate bot, second one is Konflux bot

@thepetk
Copy link
Contributor Author

thepetk commented Dec 17, 2024

Regarding the case that the new bot creates two PRs for the same image, I noticed it was coming from two different bots. Example:

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v9 registry#517](https://github.com/devfile/registry/pull/517)

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v1-1733173511 registry#519](https://github.com/devfile/registry/pull/519)

@thepetk First one is renovate bot, second one is Konflux bot

yeap exactly!

@michael-valdron
Copy link
Member

Regarding the case that the new bot creates two PRs for the same image, I noticed it was coming from two different bots. Example:

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v9 registry#517](https://github.com/devfile/registry/pull/517)

* [chore(deps): update registry.access.redhat.com/ubi9/python-39 docker tag to v1-1733173511 registry#519](https://github.com/devfile/registry/pull/519)

@thepetk First one is renovate bot, second one is Konflux bot

yeap exactly!

What's interesting is that the Konflux bot change seems more what I'd expect, the renovate bot one is trying to leap to a much higher version tag 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/ci area/registry Devfile registry for stacks and infrastructure
Projects
Status: Refinement
Development

No branches or pull requests

2 participants