Ubuntu CI Engine

Cache juju-deployer charm branches

Bug #1289806 reported by Evan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu CI Engine
Triaged
Undecided
Unassigned
Ubuntu CI Engine backlog

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

Tags: airline
Chris Johnston (cjohnston)
Changed in uci-engine:
milestone: none → backlog
Evan (ev)
no longer affects: ubuntu-ci-services-itself
Revision history for this message
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
Revision history for this message
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  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.