Opened 8 years ago

Closed 16 months ago

#5618 closed project (fixed)

Set up buildbots to create nightly builds for all our packages

Reported by: karsten Owned by: erinn
Priority: Medium Milestone:
Component: Applications/Tor bundles/installation Version:
Severity: Normal Keywords: SponsorZ, needs-triage
Cc: erinn, Sebastian Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

This is another potential sponsor F year 3 item that came out of a discussion with Roger on #tor-dev yesterday: can we have nightly builds for all our packages?

How far away are we from that? We had erinn working on #4459 to make nightly builds of the Windows bundles. We have Sebastian working on automating TBB builds and on creating an index page for buildbot statuses, right? What's left to do? And what else should we know before optimistically proposing this project to a sponsor?

Child Tickets

Change History (8)

comment:1 Changed 8 years ago by Sebastian

There might be harddisk issues, in case we want to archive the builds. There are some issues where VMs can't talk directly to each other which we'd have to fix. Both seem entirely fixable tho, and definitely with sponsor money. Other than that, we should be able to propose that to a funder.

comment:2 in reply to:  1 ; Changed 8 years ago by karsten

Replying to Sebastian:

There might be harddisk issues, in case we want to archive the builds.

How long would we want to keep a nightly build? Wouldn't it be sufficient to keep it until the next build is there?

There are some issues where VMs can't talk directly to each other which we'd have to fix.

Can you explain why VMs have to talk directly to each other for nightly builds? Which VMs are these, and what do you think is the problem? Would we want to wait to fix this until we have funding for nightly builds, or is this something we should fix anyway?

Both seem entirely fixable tho, and definitely with sponsor money. Other than that, we should be able to propose that to a funder.

Okay.

comment:3 in reply to:  2 Changed 8 years ago by Sebastian

Replying to karsten:

Replying to Sebastian:

There might be harddisk issues, in case we want to archive the builds.

How long would we want to keep a nightly build? Wouldn't it be sufficient to keep it until the next build is there?

At least a few weeks, until we've had the chance to check out what was actually wrong with it when we get a bug report

There are some issues where VMs can't talk directly to each other which we'd have to fix.

Can you explain why VMs have to talk directly to each other for nightly builds? Which VMs are these, and what do you think is the problem? Would we want to wait to fix this until we have funding for nightly builds, or is this something we should fix anyway?

Well, the build VMs don't have a webserver for obvious reasons, but they need to be able to get the packages to a place that can sign them, and then they need to be able to get them to a place with a webserver. Without that, we would build nightlies, but not do anything with them.

comment:4 Changed 7 years ago by arma

#1869 sure looks related here (and abandoned).

comment:5 Changed 7 years ago by karsten

Keywords: SponsorZ added
Milestone: Sponsor Z: March 1, 2013

Switching from using milestones to keywords for sponsor deliverables. See #6365 for details.

comment:6 Changed 5 years ago by erinn

Keywords: needs-triage added

comment:7 Changed 3 years ago by cass

Severity: Normal

This ticket is tagged SponsorZ, but it looks like progress stalled two years ago---and possibly the need has been covered in other ways.

Is this still a thing that needs funding?

comment:8 Changed 16 months ago by gk

Resolution: fixed
Status: newclosed

We have nightly builds for all of our Tor Browser stuff over at: http://f4amtbsowhix7rrf.onion

Note: See TracTickets for help on using tickets.