baseBranch change shouldn't have happened #32536
Replies: 4 comments 5 replies
-
|
The problem occurred again. Same pattern. A MR with the target-branch The original MR doesn't have the context |
Beta Was this translation helpful? Give feedback.
-
|
The problem occurred again. We are using renovate version |
Beta Was this translation helpful? Give feedback.
-
|
The problem occurred again, but different. So a new merge-request was created by renovate for a current
What can we do? What is wrong with our renovate-bot configuration? |
Beta Was this translation helpful? Give feedback.
-
|
Hi there, The maintainers have labeled this discussion as a use case specific to "enterprise" users. Enterprise users typically self-host Renovate and have advanced requirements like custom certificates, HTTP proxies, private registries, air gapping, etc. Such cases usually need a lot of back-and-forth to resolve, because the problem is related to the user's environment. Usually the user's environment can not be reproduced publicly, which means that maintainer debugging is not possible. The maintainers decided their time is best spent on issues that help large numbers of users. This means enterprise-specific issues affecting one user (or a small number of users), are not a priority. If we can help you quickly, we will. But if you see this message, then a maintainer believes this is not a quick fix. The maintainers will not actively work on this issue, unless new information is found. If you are an enterprise user, please consider the following options:
If you choose to wait, then this discussion can remain open indefinitely. But please be patient, do not nudge or bump this discussion just to get attention. Thanks, the Renovate team |
Beta Was this translation helpful? Give feedback.
-
|
this is a renovate limitation. renovate adds the base branch to branches if there are two or more base branches. as workaround add an empty dummy base branch, so you always have at least two base branches. |
Beta Was this translation helpful? Give feedback.
-
|
@rarkins @secustor I think we should always add base branch when user configured base branches length is greater than zero |
Beta Was this translation helpful? Give feedback.
-
|
The reason for NOT doing that originally was that if the user supply switches the one default branch which renovate uses, eg from main to dev, then we keep the same simple branches |
Beta Was this translation helpful? Give feedback.
-
|
related to |
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for the updates. I added a dummy branch {
"$schema": "https://docs.renovatebot.com/renovate-schema.json",
"extends": [
"config:recommended"
],
"baseBranches": [
"$default",
"renovate-bot-dummy-branch",
"/^hotfeat\\/.*/"
],
...
}Now renovate-bot adds the base branch as context to the merge requests:
Thanks again. |
Beta Was this translation helpful? Give feedback.
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
GitLab
Please tell us more about your question or problem
Hi,
we are running renovate-bot self-hosted (GitLab) in version renovate/renovate:38.142.5@sha256:cd3fca30ca12ff9abf3bfc444dc5e5d6ccb876ac8def26a757e2e01c17900627
We use renovate bot for updates with multiple managers (docker, maven, npm, ...) on the project's default branch
develop(configured GitLab). Additional base branches are temporary and are only present, when we have to provide a hotfix. For hotfix branches we have configured that they require an approval via renovate-bot's dependency issue in GitLab. The following happened in this setup:developwas present.develop. Since we did not manage to resolve them, they were left open.hotfixbranch for an upcoming hotfix-release.The situation is best visible via the comments renovate-bot added to the MR.
Step 4 was unexpected.
The following listing shows an excerpt of our renovate-bot configuration.
What do we miss?
Best regards
Jörg Liebig
Logs (if relevant)
Logs
I extracted the relevant sections from the renovate-bot run. "..." denote additional lines before, between, and after relevant sections. Dependency "mapstruct" is an example (maven-package), but other managers are affected as well (e.g., npm).
Beta Was this translation helpful? Give feedback.
All reactions