Upgrade ci.linaro.org, android-build.linaro.org to latest LTS
Bug #1199710 reported by
Paul Sokolovsky
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Linaro Android Infrastructure |
Won't Fix
|
High
|
Unassigned | ||
Bug Description
android-
| Changed in linaro-android-infrastructure: | |
| importance: | Undecided → Critical |
| status: | New → Confirmed |
Revision history for this message
| Paul Sokolovsky (pfalcon) wrote | #1 |
| Changed in linaro-android-infrastructure: | |
| importance: | Critical → High |
| status: | Confirmed → Triaged |
Revision history for this message
| Milo Casagrande (milo) wrote | #2 |
| Changed in linaro-android-infrastructure: | |
| assignee: | nobody → Paul Sokolovsky (pfalcon) |
| summary: |
- Upgrade ci.linaro.org, android-build.linaro.org to Precise + Upgrade ci.linaro.org, android-build.linaro.org to latest LTS |
| description: | updated |
Revision history for this message
| Milo Casagrande (milo) wrote | #3 |
| Changed in linaro-android-infrastructure: | |
| status: | Triaged → Won't Fix |
| assignee: | Paul Sokolovsky (pfalcon) → nobody |
To post a comment you must log in.
I looked into upgrading a-b during LCE13, but turns out, that Maverick EC2 is completely gone by now, i.e. it's not possible to upgrade it to Natty, etc. So, the only scalable solution would be to re-setup it from scratch. Another possible solution is to hunt for possible mirrors and archives of Maverick/Natty package repos, but that's somewhat of monkey work and firefighting. That time instead can be invested into developing proper deployment management for a-b, to make redeployments a breeze.