Page MenuHomePhabricator

Implement a buildbot for master
Closed, ResolvedPublic

Description

The buildbot must :

  • Run the full test suite on master on a regular basis.
  • Bissect test failure to find the root cause.
  • Report the test to the person who made the diff.

Alternatively, if the test is flaky, we may want to report to the test owner.

Event Timeline

deadalnix created this task.Jun 14 2017, 23:16

Do we specifically want to use buildbot? Or is that being used loosely? How many different build configurations do we need?

I can think of something ultra-simple that meets these requirements:

Write some scripts that integrate with Travis and just auto-pull new diffs out and submit them to travis (a little fuzzy on the particulars of what travis's API is like.. but I am pretty sure it's doable).

Does that sound evil/stupid/good/doable/reasonable/crazy?

In T38#1292, @schancel wrote:

Do we specifically want to use buildbot? Or is that being used loosely? How many different build configurations do we need?

Good questions. @deadalnix?

deadalnix added a comment.EditedAug 24 2017, 21:59

I don't care what we use as long as it works. I think the best option for us is to have some homebrew thing on a machine somewhere. Starting a container and building in it isn't too hard and we can have it do whatever we want with it.

Using travis is another option if API allows.

schancel claimed this task.Nov 9 2017, 22:58
schancel added a subscriber: mbhinder.

@mbhinder This is what I'm working on right after T104

schancel closed this task as Resolved.Jan 17 2018, 23:42