-
Notifications
You must be signed in to change notification settings - Fork 503
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
Rebulid OBS packages only if sources are changed #3220
Comments
Is changing the trigger to |
I'm currently not working on this |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
I noticed that all packages in all OBS build projects suddenly got rebuilt today. Turns out that this is expected because OBS automatically triggers package rebuilds if any (direct or transitive) dependency is upgraded in the operating system that's used for building packages. For example, we had this situation today:
This is actually not much useful to us because we use prebuilt binaries in packages instead of building binaries inside OBS. Moreover, this can interfere with our release process and tooling. I think that we should disable this behavior and only rebuild packages if sources are updated.
References:
/assign
/priority important-soon
The text was updated successfully, but these errors were encountered: