1. tb3: using tinderboxes efficiently
Bjoern Michaelsen

2. tb3: using tinderboxes efficiently
Agenda
Status quo
Scoring
Trusting the client or not?
Keeping owners in control
Django Web UI
Missing Bits
tb3: using tinderboxes efficiently

3. Crowdsourcing code review
By US Navy and thus public domain

4. Status Quo: no coordination
bazillion mails
“Are we there yet?”/”Is it fixed yet?”
three linux tinderboxes might all test the same build …
… while other commits remain completely untested.
tb3: using tinderboxes efficiently

5. tb3: using tinderboxes efficiently
Stop right now!
Stop right there I gotta know right now before we go any further …
Let me sleep on it and I’ll give you an answer in the morning
– Paradise by the Dashboard Light, Bat out of Hell, Meat Loaf
We would love to bisect a breaker ASAP!
esp. on very slow platforms
But: We dont want to stop watching the head of the branch.
tb3: using tinderboxes efficiently

6. tb3: using tinderboxes efficiently
Why scoring?
Generic: a build scenario
Adaptable: By weighting
Comparable: describes relative urgency
thereby allows assigning and distributing resources:
to multiple platforms
to multiple strategies:
bisecting/building head/gerrit verification
to multiple branches: release branch and master
tb3: using tinderboxes efficiently

7. Coordination: building head
tb3: using tinderboxes efficiently

8. Coordination: bisecting
tb3: using tinderboxes efficiently

9. Coordination: never trust the client (mostly)
tb3: using tinderboxes efficiently

10. Coordination: never trust the client (mostly)
tb3: using tinderboxes efficiently

11. Coordination: never trust the client (mostly)
(mostly) comparable results
the strictness of this might differ by platform
(mostly) reliable reporting
(mostly) reliable turnaround times
tb3: using tinderboxes efficiently

12. Keeping the choice with the tinderbox owner
Scores are just proposals
Picking up the scores is no obligation to build a proposal
Thus:
tinderbox owners can do fancy reweighting voodoo of scores
tinderbox owners can track multiple scenarios and build what is most urgent
tinderbox owners can report one result to multiple platforms
tb3: using tinderboxes efficiently

13. Django Web-UI: repository overview
tb3: using tinderboxes efficiently

14. Django Web-UI: Branch overview
tb3: using tinderboxes efficiently

15. Django Web-UI: Repository builds
tb3: using tinderboxes efficiently

16. Django Web-UI: Branch builds
tb3: using tinderboxes efficiently

17. tb3: using tinderboxes efficiently
Django: Missing bits
RSS feeds
IRC bots/twitter feeds
log uploads
Web UI de-uglification
gitweb/cgit integration
gerrit builder integration
client side plumbing/production machine setup
tb3: using tinderboxes efficiently

18. tb3: using tinderboxes efficiently
Conclusion
tb3 allows to:
Coordinate multiple builders working on the same scenario/branch
Coordinate one tinderbox to work on multiple branches and scenarios as needed
Make tinderboxes bisect without loosing track of the head of a branch
Esp. helps with tests and builds that are painfully slow
tb3: using tinderboxes efficiently

19. tb3: using tinderboxes efficiently
Contact me
Sweetshark on #libreoffice-dev/#libreoffice-qa on freenode
Sweetshark1 on twitter
tb3: using tinderboxes efficiently