Opened 5 years ago

Last modified 6 weeks ago

#1281 reviewing change

Set up a build server — at Version 1

Reported by: fhd Assignee:
Priority: P2 Milestone:
Module: Infrastructure Keywords:
Cc: fhd, sergz, kvas Blocked By:
Blocking: Platform: Unknown
Ready: yes Confidential: no
Tester: Unknown Verified working: no
Review URL(s):

https://codereview.adblockplus.org/29325436/
https://codereview.adblockplus.org/29336742/

Description (last modified by fhd)

Background

We're currently running builds on the main server, in regular intervals. We should move that to a dedicated server.

And I'm pretty sure we want to use a CI server while we're at it, some reasons:

  1. It will handle build scheduling for us - we can build on push and/or in regular intervals, and we can chain dependent tasks (i.e. libadblockplus build and tests, Android build)
  2. We can run builds on several slaves (e.g. one for Linux, one for Windows)
  3. There's a UI we can use to see which builds failed when and for what reason, and which builds are currently in progress and in which stage

What to change

Migrating all the jobs we currently have is not something we should do in one go. I think the best way forward is to set up a build server that runs a single, relatively straightforward build: libadblockplus.

Buildbot seems like the best option:

  1. It is very popular
  2. The whole configuration is in Python - highly flexible

We should set up two nodes: One for the buildbot master and a single slave - that should suffice for now. Running master and slave on the same node will make things unnecessarily messy and harder to scale.

Change History (1)

comment:1 Changed 5 years ago by fhd

  • Description modified (diff)
Note: See TracTickets for help on using tickets.