Cache juju-deployer charm branches

Bug #1289806 reported by Evan on 2014-03-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu CI Engine
Undecided
Unassigned

Bug Description

we can probably shave off some time by putting the juju-deployer charm branches into a cached location, with deploy.py doing --overwrite

9:56 AM <vila> we have ./branches just for that

Changed in uci-engine:
milestone: none → backlog
Evan (ev) on 2014-03-31
no longer affects: ubuntu-ci-services-itself
Celso Providelo (cprov) wrote :

This is currently done by using deployment 'working-dir's, instructing `deploy.py` prepare deployment configurations (populated templates, local and external charms) in a specific location.

Changed in uci-engine:
status: New → Fix Released
Vincent Ladeuil (vila) wrote :

> This is currently done by using deployment 'working-dir's,

No, this bug is one level up: acquiring and caching the charm branches *before* deploy.py copy them.

Changed in uci-engine:
status: Fix Released → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers