Documentation Deployment Automation

Registered by Monty Taylor on 2011-07-15

A set of various things that need to be done for Documentation automation

Blueprint information

Status:
Started
Approver:
Jay Pipes
Priority:
High
Drafter:
Monty Taylor
Direction:
Approved
Assignee:
Monty Taylor
Definition:
Approved
Series goal:
None
Implementation:
Started
Milestone target:
milestone icon diablo-4
Started by
Jay Pipes on 2011-07-18

Related branches

Sprints

Whiteboard

Work Items:
Anne: See bug requesting automated builds to a docs staging server, https://bugs.launchpad.net/openstack-ci/+bug/968781
Anne: See mailing list http://<email address hidden>/msg09232.html asking for having Jenkins raise a doc bug if a new flag
has been added (when Jenkins merges a branch), or the flag comment or default has changed.
Offer a way for devs to tag an incoming review as "DocImpact" meaning either there are docs to be reviewed or the code means changes for the doc.https://bugs.launchpad.net/openstack-ci/+bug/1003152
Use git review to edit docs on web: https://bugs.launchpad.net/openstack-ci/+bug/1003153 - Offer a way for readers to edit a page in a lightweight web-based editor, then use git-review in the background to submit a review to Gerrit.
Move docs.openstack.org to cloud server (Anne: I don't consider this as a requirement to the overall goal of having a staging server?): TODO
Finish install/reorg of doc dirs: TODO
Deploy incubation docs: DONE
Split docs webserver from wiki webserver: TODO
Switch to nginix for docs webserver: TODO
Sync live doc DB content back to staging db: TODO
Automate openstack.org code rollout: TODO

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.