Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Build the manual in travis-ci #537

Closed
prjemian opened this issue Feb 21, 2017 · 5 comments
Closed

Build the manual in travis-ci #537

prjemian opened this issue Feb 21, 2017 · 5 comments
Assignees
@zjttoefs
Labels
low priority

Comments

@prjemian
Copy link
Contributor

Taking inspiration from a different GitHub project suite, can we build the NeXus manual as part of the travis-ci script, then push to GH pages for publishing?

This would duplicate the jenkins build and copy process currently running at nexusformat.org
@zjttoefs
Copy link
Contributor

We certainly can, I've done that for canSAS (I believe). It's also worth considering, but not before the web page has moved over (that currently gets published from a definitions build).
Even then it's a case of "never touch a running system": Once we need to make changes anyway, I'd be happy to do it.

@zjttoefs zjttoefs self-assigned this Feb 23, 2017
@zjttoefs zjttoefs changed the title Can we build the manual in travis-ci? Build the manual in travis-ci Feb 23, 2017
@prjemian prjemian mentioned this issue Jun 14, 2017
Closed
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 try *building* the manual if tests succeed
b1a052c
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 pre-processing step worked, try Sphinx next
bc0860f
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 sphinx is now a dependency
c683848
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 python3-ism
edeaf53
@prjemian
Copy link
Contributor Author

Great! Manual builds (no PDF for now, see #570) in py2 and py3.

Next step before this issue can be closed is to copy the built manual to our published site (presumably a GitHub pages site).

prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 prepare a tarball
7e065a2
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 need to study before proceeding with publishing
093ec7e
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 try again with corrected path
2de23e4
@prjemian
Copy link
Contributor Author

some one has written this up for us on StackOverflow

prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 can we access the tarball?
3d47de2
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 resolve py3 Sphinx warnings
fab9c64
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 location
7a9f596
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 try PDF manual now
fb19c53
@prjemian
Copy link
Contributor Author

No latexmk on travis-ci now, latexpdf failed

prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 skip PDF for now on travis-ci
80c1052
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 diagnose extra footnote cited in NXentry
02bf045
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 resolve footnote reference
263a2a3
prjemian added a commit that referenced this issue Jun 14, 2017
@prjemian
#537 indentation
d0c8920
@prjemian
Copy link
Contributor Author

Travis-ci needs to include support for building LaTeX documentation. Until then, travis-ci cannot be used to build both HTML and PDF versions of the NeXus documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zjttoefs zjttoefs

Labels
low priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zjttoefs @prjemian