Check if we need to upload the payload before sending to swift
Bug #1287942 reported by
Evan
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu CI Engine |
Fix Released
|
High
|
Vincent Ladeuil | ||
| Ubuntu CI Services |
Fix Released
|
High
|
Vincent Ladeuil | ||
Bug Description
10:01 PM <ev> hm, perhaps we should sha1 the deployment payload and make that the filename for the upload to swift
10:02 PM <ev> that way we can do a swift list to see if we even need to upload anything
10:02 PM <ev> rather than pushing the payload up with every deployment
10:02 PM <plars> good idea
Related branches
lp://staging/~vila/ubuntu-ci-services-itself/12897942-sha1-payload
- Para Siva (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 12 lines (+1/-1)1 file modifiedjuju-deployer/deploy.py (+1/-1)
| Changed in ubuntu-ci-services-itself: | |
| assignee: | Evan Dandrea (ev) → Vincent Ladeuil (vila) |
| status: | New → Confirmed |
| importance: | Undecided → High |
| milestone: | backlog → phase-0 |
Revision history for this message
| Andy Doan (doanac) wrote | #1 |
Revision history for this message
| Vincent Ladeuil (vila) wrote | #2 |
Revision history for this message
| Vincent Ladeuil (vila) wrote | #3 |
| Changed in ubuntu-ci-services-itself: | |
| status: | Confirmed → In Progress |
| Changed in ubuntu-ci-services-itself: | |
| status: | In Progress → Fix Committed |
| Changed in ubuntu-ci-services-itself: | |
| status: | Fix Committed → Fix Released |
| Changed in uci-engine: | |
| assignee: | nobody → Vincent Ladeuil (vila) |
| importance: | Undecided → High |
| milestone: | none → phase-0 |
| status: | New → Fix Released |
To post a comment you must log in.
you really think this is a must-have for phase0?