Modify ↓
Opened 19 years ago
Closed 17 years ago
#89 closed defect (fixed)
Option to always build the newer revision
Reported by: | anonymous | Owned by: | cmlenz |
---|---|---|---|
Priority: | major | Milestone: | 0.6 |
Component: | Build master | Version: | 0.5 |
Keywords: | Cc: | ||
Operating System: |
Description
When configuring a build, it would be nice to have an option so that slaves only try to build the newer available revision.
This would be very useful for important project with lot of different revisions, with new Bitten slave popping up all the time. Currently it require manually modifying the build configuration to manually set the oldest revision each time a new slave pop up.
Attachments (0)
Change History (2)
comment:1 Changed 19 years ago by cmlenz
- Component changed from General to Build master
- Milestone set to 0.6
comment:2 Changed 17 years ago by cmlenz
- Resolution set to fixed
- Status changed from new to closed
This has been implemented some time ago, as the build_all option on the build master.
Note: See
TracTickets for help on using
tickets.
The current mode of building the entire history should be made an optional feature of the master.