•  
     
    story #3078 spike documentation build system for tuleap
Summary
developer
spike documentation build system for tuleap
the team can estimate the work to do
- define git workflow (github / tuleap / readthedocs / doc.tuleap.net)
- how to configure jenkins to build documentation and push to doc.tuleap.net
- build in 2 languages
- When I commit on master, it's "development" version of the doc that is updated on tuleap.net
- When I tag or branch, it updates doc.tuleap.net in the relevant "stable" location
- Decided if we use tag or branch
- Build documentation RPM and integrate it to the delivery
Empty
Empty
Status
Empty
Done
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#3078
Manuel Vacelet (vaceletm)
2013-04-29 10:00
2013-04-15 12:06
1702

References
Referencing story #3078

Artifact Tracker v5

epic #2060 Documentation

Follow-ups