Jenkins automatic deployment of trunk to 'testing' site
Bug #1179565 reported by
Allan LeSage
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Helipad |
Fix Released
|
Medium
|
Chris Johnston | ||
Bug Description
Create a sub-job and/or fabric.py utility to auto-deploy our latest trunk to a 'testing' site. This testing site could be on port 82, e.g. (see existing fabric.py 'staging' site for an example).
Revision history for this message
| Chris Johnston (cjohnston) wrote | #1 |
| Changed in helipad: | |
| assignee: | nobody → Chris Johnston (cjohnston) |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
| status: | Confirmed → Triaged |
| Changed in helipad: | |
| status: | Triaged → In Progress |
| Changed in helipad: | |
| status: | In Progress → Fix Committed |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Once we get your code working with the dashboard, this will be automagic.