Closed Bug 1463308 Opened 7 years ago Closed 7 years ago

Setup appveyor private cloud

Categories

(Infrastructure & Operations :: RelOps: General, task)

Product:
Infrastructure & Operations
Component:
RelOps: General
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED INVALID

People

(Reporter: dividehex, Unassigned)

Details

During the relops work week Appveyor was determined to be one of the best options to setup the ISO to VHD build environment. Unfortunately, the build output (9GB) caused us to hit a outgoing networking limit on Appveyor's infrastucture. Appveyor has since enabled their private build cloud for us at no cost which allows us to tap into using Appveyor's build orchestration app while using our own ec2 and s3 resources within the Releng aws account. This would also be much faster since transferring the artifacts from the ec2 instance directly to s3 in the same region. https://github.com/mozilla-platform-ops/relops_appveyor
We need to re-evaluate using TaskCluster for this; pete made some good points, and as long as we're careful about our processes and having a solid rollback plan, it shouldn't be too much of a chicken&egg problem.

Rob, do you think we still need appveyor or are you moving in the taskcluster direction with this?

Flags: needinfo?(rthijssen)

atm we have a (somewhat) working solution in tc. the missing bits are to do with our own security considerations rather than technical barriers, so my preference would be to continue using the tc implementation (without appveyor).

Flags: needinfo?(rthijssen)

Sounds good to me :-) Marking invalid

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.