#52766 closed enhancement (fixed)
buildbot: portwatcher should trigger portbuilder builds in predictable order
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | neverpanic (Clemens Lang) |
---|---|---|---|
Priority: | High | Milestone: | |
Component: | buildbot/mpbb | Version: | |
Keywords: | buildbot | Cc: | mojca (Mojca Miklavec) |
Port: |
Description
Currently, portwatcher triggers portbuilder builds in random order. (Well, they're triggered in alphabetical order, but buildbot then adds them to an unordered python dictionary from which they're pulled out in random order.)
Per a suggestion on the buildbot users mailing list, we should add a custom "priority" property to each triggered build, and then write a nextBuild function which determines which of the pending BuildRequests to build next by examining their "priority" properties.
Once this is working and causing builds to happen in alphabetical order, we can try to do the more complicated dependency order.
Change History (8)
comment:1 Changed 8 years ago by mojca (Mojca Miklavec)
Cc: | mojca added |
---|
comment:2 Changed 8 years ago by mojca (Mojca Miklavec)
Keywords: | buildbot added |
---|
comment:3 Changed 7 years ago by neverpanic (Clemens Lang)
Priority: | Normal → High |
---|
comment:4 Changed 7 years ago by neverpanic (Clemens Lang)
Component: | server/hosting → buildbot/mpbb |
---|
comment:5 Changed 7 years ago by mojca (Mojca Miklavec)
comment:6 Changed 7 years ago by neverpanic (Clemens Lang)
Owner: | changed from admin@… to neverpanic |
---|---|
Status: | new → assigned |
Thanks. Now we need to sort the output of list-subports in dependency order.
comment:7 Changed 7 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:8 Changed 7 years ago by jmroot (Joshua Root)
Note: See
TracTickets for help on using
tickets.
In bf29a890d45aea8c4627c01f289cf45e0f1eebf7/macports-infrastructure: