Details
-
Type:
Story
-
Status: Done
-
Resolution: Done
-
Fix Version/s: None
-
Component/s: Stack Documentation and UX
-
Labels:
-
Story Points:0.2
-
Epic Link:
-
Team:SQuaRE
Description
Build warnings continue to creep into the Developer Guide:
/Users/jsick/lsst/dm_dev_guide/services/storage.rst:27: SEVERE: Unexpected section title or transition.
|
|
======
|
/Users/jsick/lsst/dm_dev_guide/services/storage.rst:37: SEVERE: Unexpected section title or transition.
|
|
-------------------------------------------------------------------------------------
|
/Users/jsick/lsst/dm_dev_guide/services/storage.rst:40: WARNING: Block quote ends without a blank line; unexpected unindent.
|
/Users/jsick/lsst/dm_dev_guide/services/storage.rst:40: SEVERE: Unexpected section title or transition.
|
|
--------------------------------------------------------------------------------------
|
/Users/jsick/lsst/dm_dev_guide/services/storage.rst:43: WARNING: Block quote ends without a blank line; unexpected unindent.
|
/Users/jsick/lsst/dm_dev_guide/services/storage.rst:43: SEVERE: Unexpected section title or transition.
|
|
-------------------------------------------------------------------------------------
|
looking for now-outdated files... none found
|
pickling environment... done
|
checking consistency... /Users/jsick/lsst/dm_dev_guide/services/ldf-resources.rst:: WARNING: document isn't included in any toctree
|
/Users/jsick/lsst/dm_dev_guide/services/ldf-tickets.rst:: WARNING: document isn't included in any toctree
|
/Users/jsick/lsst/dm_dev_guide/services/storage.rst:: WARNING: document isn't included in any toctree
|
done
|
preparing documents... done
|
writing output... [100%] work/project-planning
|
/Users/jsick/lsst/dm_dev_guide/cpp/style.rst:106: WARNING: undefined label: pipelines:source-install-redhat-legacy (if the link has no caption the label must precede a section header)
|
This ticket is to fix the existing syntax issues and then prevent future issues by enabling the "error on warnings" aka nitpick mode for Sphinx.
It might also be good to update the CONTRIBUTING documentation for the Developer Guide to point out how to find the Travis CI page.