Skip to content

Stable not updated to last tag #4435

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

Closed
jouvin opened this issue Jul 26, 2018 · 7 comments
Closed

Stable not updated to last tag #4435

jouvin opened this issue Jul 26, 2018 · 7 comments
Labels
Needed: more information A reply from issue author is required Support Support question

Comments

@jouvin
Copy link

jouvin commented Jul 26, 2018

Details

Expected Result

stable rebuilt with tag pan-10.7

Actual Result

stable is stucked with origin/10.4. Not sure how it happened as I don't thing it ever existed. I tried to wipe the build, disable the stable version and clicked on the 'Clean' button in the inactive version list... I didn't manage to fix the problem.

latest doesn't seem to suffer a similar problem.

@stsewd
Copy link
Member

stsewd commented Jul 26, 2018

Can you please try rebuilding latest or master? That way the versions are refreshed.

@stsewd stsewd added Support Support question Needed: more information A reply from issue author is required labels Jul 26, 2018
@jouvin
Copy link
Author

jouvin commented Jul 27, 2018

Unfortunatly, it doesn't help (https://readthedocs.org/projects/quattor-pan/builds/7550171/). The problem remains that in the version list, the associated branch/commit for stable remains origin/10-4, something that doesn't exist and it never gets updated...

@jrha
Copy link

jrha commented Jul 27, 2018

I fiddled around with this for a while thinking that perhaps our tag versions were not being parsed, but in the end I created the 10.4 branch it was referring to and that seems to have unstuck it.

@stsewd
Copy link
Member

stsewd commented Jul 27, 2018

@jouvin I can see that your stable version has the new commit now, were you able to solve the issue?

@jouvin
Copy link
Author

jouvin commented Jul 28, 2018

As said by @jrha we managed to fix the problem by creating the missing branch so that RTD managed to compile the stucked stable and after that it got updated as expected. May be worth an entry in the FAQ...

@jouvin jouvin closed this as completed Jul 28, 2018
@stsewd
Copy link
Member

stsewd commented Jul 28, 2018

oh, well. I think this was because rtd can't detect deleted branches at the time, so you need to wipe latest and build again, that way rtd have the updated versions. ¿How this happen? I think your project is in one of this cases described at #4258 and #4259

@jrha
Copy link

jrha commented Jul 30, 2018

@stsewd thanks, #4259 seems like precisely what we hit, I don't feel like trying to reproduce it again though!

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 Support Support question
Projects
None yet
Development

No branches or pull requests

3 participants