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.

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

Automate documentation testing with a PR #248

Closed
duvivier opened this issue Nov 20, 2018 · 9 comments
Closed

Automate documentation testing with a PR #248

duvivier opened this issue Nov 20, 2018 · 9 comments

Comments

@duvivier
Copy link
Contributor

We want to integrate test building of documentation for any PR that has modifications to the /doc/ directory (or just any pull request)? Possible ways of doing this include possibly using a probot or incorporating it into the Travis CI tests.

@phil-blain
Copy link
Member

This is a planned feature of readthedocs, apparently coming this year !
readthedocs/readthedocs.org#1340

@duvivier
Copy link
Contributor Author

This is great news. It might just be worth the wait of holding out to see what they come up with instead of inventing the wheel ourselves.

@phil-blain
Copy link
Member

See also the project board https://github.com/orgs/readthedocs/projects/8

Apparently the feature is ready to beta test: https://blog.readthedocs.com/building-docs-for-pull-requests/ @duvivier if you want to try it out.

@apcraig
Copy link
Contributor

apcraig commented Aug 22, 2019

We just received early access to the PR capability with readthedocs and I have turned on the webhook for readthedocs in both Icepack and CICE to "pull request" as directed by readthedocs folks. We'll have to see what happens. My hope is with the next pull request, we get a new link in the PR pointing to the readthedocs documentation build. We'll see.

@apcraig
Copy link
Contributor

apcraig commented Sep 17, 2019

This seems to be working now in both Icepack and CICE. I will close this for now. If we need to reopen or need to open a new issue if something comes up, we can.

@apcraig apcraig closed this as completed Sep 17, 2019
@phil-blain
Copy link
Member

Just to document, what was missing to make it work ?

@apcraig
Copy link
Contributor

apcraig commented Sep 17, 2019

This is a good question. The final piece of the puzzle was to go into my personal settings, under applications, authorized OAuth apps, click on readthedocs, then make sure readthedocs was authorized in the CICE-Consortium.

The permissions thing is something I still don't totally understand. I have to do things in my personal settings under github and readthedocs to allow the CICE-Consortium Project to interact between github and readthedocs. I guess this is because I have some admin permissions, but it would make more sense if I set something in the CICE-Consortium settings in github and readthedocs as an admin to set the permissions.

The other thing that had to be done was in the github CICE-Consortium Icepack repo settings, make sure the webhook for readthedocs had Pull Requests turned on.

Finally, something was done on the readthedocs side outside my control because this was a beta feature. So it had to be turned on for the cice-consortium. I assume once this is formally supported in readthedocs, it will be "on" for all projects.

As I said, it's working and I understand what I did. But I'm still fuzzy how it all works.

@duvivier
Copy link
Contributor Author

@apcraig Thanks so much for ironing out these details. Do you happen to know if anyone with the admin settings for the consortium (Elizabeth for example) could also make the changes to allow this? Or did it have to be you?

@apcraig
Copy link
Contributor

apcraig commented Sep 17, 2019

I'm pretty sure anyone with the same permissions as I can do the same thing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants