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
Rebuild with latest sources #7457
Comments
Generally, I would think you can implement such a thing with a scheduler for your specific configuration, especially if this is a configuration you use often. Such schedulers can be trigger when code is updated on a branch, or at specific times. Our config is at least one force scheduler for a builder, then for each product branch a scheduler that trigger within minutes of new commits, and another that trigger once a day, for a set of builders. Each builder have properties defined that specify things like target cpu, OS, and features. One thing Buildbot is currently missing is manual triggering of a Nightly type schedulers via the WebGUI, see #4082 , but that can be created using a dashboard |
That's the problem, the configuration is different each time. We have a special configuration we want to test, so we build and rebuild with this configuration. But once it has passed, we will never again use the same configuration... |
In such cases I would perhaps use a branch that is hardcoded with that configuration, and have one or more scheduler for that branch, then remove the scheduler later. Alternatively, the scheduler (which can be added/removed with a buildbot manager refresh, a restart is not needed) could also be used to configure the settings, instead of hardcoding in the source. |
It happens that we want to trigger a build with some specific properties. And of course, it does not succeed on the first trial, and we have to push some fixes and trigger the same build again.
It would be useful if there was a button like "Rebuild" but to trigger the same build with the latest source, for instance "Rebuild latest" or "Build again with latest"...
The text was updated successfully, but these errors were encountered: