Cache juju-deployer charm branches
Bug #1289806 reported by
Evan
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu CI Engine |
Triaged
|
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 |
no longer affects: | ubuntu-ci-services-itself |
To post a comment you must log in.
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.