Linking multiple projects to the same repo causing significant version problems

[mradamcox]

I'll preface this by saying that having two projects built from the same repo is not ideal, but it seemed like a clean workaround for not being able to do a full domain redirect from one (the original docs) to the new one.

Details

• Project URL: arches.readthedocs.org
• Project URL: arches4.readthedocs.org
• Build URL (if applicable):
• Read the Docs username (if applicable): mradamcox

Expected Result

I'm having trouble with two projects: arches used to be pointed at a bitbucket repo, and arches4 points to the current code base: https://github.com/archesproject/arches. I want both projects to be identical, now building from a new repo where I have consolidated all documentation into one place, with branches for each release: https://github.com/archesproject/arches-docs.

Actual Result

The problem is that even after I change the URL to the new repo, deactivate all of versions (and wipe them), disable any previous github integrations, and make new webhooks, the tag release SHAs are still associated with many versions in each repo. Most strangely, the new project arches now has versions designated for the tags from the original code base, from which that project was never built in the first place. This causes a failed build on stable like this https://readthedocs.org/projects/arches/builds/6867530/ because in reality that SHA does not exist in the arches-docs repo.

It seems to me that this may be related to #3743, because ultimately what I really need is to just wipe all of the version-related metadata (SHA, name, etc) in both of these projects and start brand new. Based on this ticket #3192 I have deleted and recreated the webhooks (and waited a day) but the weirdness remains.

[stsewd]

mmm, I think this is related to #3729 and #3714, both users were able to solve this recreating the rtd project.

@humitos probably a bug caused by a recently regression or just coincidence? Three similar reports this week.

[mradamcox]

Deleting and recreating the projects solved the problems I was having. I'll leave closing this ticket up to others, as I'm not sure if it actually points to a new or known bug.

[stsewd]

I think this was because of this bug #3887.

[humitos]

Great! I'm closing this one since the original issue is already fixed and we have a fix proposal for the general rule. Thanks for reporting and help us to debug!

[mradamcox]

Yup, reading the conversation on 3887 it seems that this issue will be fixed whenever the other bug is addressed. Thanks for keeping up with this!