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

RTD not loading new versions from branches #2491

Closed
robredpath opened this issue Nov 8, 2016 · 4 comments
Closed

RTD not loading new versions from branches #2491

robredpath opened this issue Nov 8, 2016 · 4 comments
Labels
Needed: more information A reply from issue author is required

Comments

@robredpath
Copy link
Contributor

robredpath commented Nov 8, 2016

Details

Expected Result

I've created a new branch in my docs repo - https://github.com/openreferral/specification/tree/inline-docs . I pushed about 12 hours ago, and the new branch hasn't appeared as a version in RTD, which I was expecting to happen automatically.

Actual Result

The 'versions' page in RTD admin shows 4 versions:
screen shot 2016-11-08 at 08 18 09 ,

which doesn't reflect the current branches:

screen shot 2016-11-08 at 08 18 43

UPDATE 2016-11-08 17:45 UTC: Branches have now appeared; I'm not sure if that's due to this issue being opened. My immediate problem is fixed, but my expected result of seeing new branches fairly quickly and actual result of it taking 24h are still different.

@stsewd
Copy link
Member

stsewd commented Jan 3, 2018

See related comment here #1822 (comment).

I'm not sure about this use case, but I think is unnecessary to have to build the last docs in order to get the new branch, (probably this one is going to be build too). Having a webhook to do this seems reasonable to me. I going to see the code if this is easily possible.

@stsewd
Copy link
Member

stsewd commented Jan 5, 2018

If we want to add this feature, we need to pass all the tags or branches (we can get this data from the cloned repo), Or we can implement a patch endpoint for only add branches.

Should we implement all the crud for versions? When a branch or tag is created or deleted on the repo, we have to update this on the project.

Or... we could call the build process when a new branch is created, this will resync all the versions.

@stsewd
Copy link
Member

stsewd commented Apr 9, 2018

I think this can be also solved with #1375

@stsewd stsewd added the Needed: more information A reply from issue author is required label May 10, 2018
@stsewd
Copy link
Member

stsewd commented May 10, 2018

Closing this as the user hasn't responded or given more information, feel free to reopen with more information if you are still having this problem :).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needed: more information A reply from issue author is required
Projects
None yet
Development

No branches or pull requests

2 participants