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

Make previous build chioce configurable #489

Merged
merged 1 commit into from Aug 11, 2012
Merged

Make previous build chioce configurable #489

merged 1 commit into from Aug 11, 2012

Conversation

jgonzalezmendez
Copy link
Contributor

When prioritizing build requests in an order other than arrival time,
builds' relative order might not always reflect the topological order of
the changes. This change makes the build order to be configurable such
that status transition modes are only sent out when a more recent
change affects the status of a less recent one, as opposed to relying
on the default chronological ordering of the builds.

When prioritizing build requests in an order other than arrival time,
builds' relative order might not always reflect the topological order of
the changes. This change makes the build order to be configurable such
that status transition modes are only sent out when a more recent
*change* affects the status of a less recent one, as opposed to relying
on the default chronological ordering of the builds.

Change-Id: I2009a8b1f4d093a23ef6eea869567aa54b7987b6
@djmitche djmitche merged commit 0f39575 into buildbot:master Aug 11, 2012
@djmitche
Copy link
Member

Thanks - merged!

@tomprince
Copy link
Member

It seems to me like it would be better to make buildbot smarter, rather than force everyone to configure things to work right for them.

@jgonzalezmendez
Copy link
Contributor Author

Indeed. The whole "configurability" of build requests can use a more cohesive API for users to provide a scheduling algorithm that the master rely on and use throughout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants