Skip to content

Help with failing build needed (Neos/Flow) #2623

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
kdambekalns opened this issue Jan 30, 2017 · 4 comments
Closed

Help with failing build needed (Neos/Flow) #2623

kdambekalns opened this issue Jan 30, 2017 · 4 comments

Comments

@kdambekalns
Copy link

Details

Expected Result

I'd like to see the documentation build just fine.

Actual Result

The build fails, as shown at the build URL.

The problem is: I have no clue what is going on there and how we could fix this from our side, if we actually could fix it.

We have the same issue with "our other project" as can be seen at https://readthedocs.org/projects/neos/builds/

On top of that, the message looks like a hint to me, not like an error… so is this actually the cause for the error?

@ericholscher
Copy link
Member

ericholscher commented Feb 7, 2017

You have an invalid conf.py specified in your project: TYPO3.Flow/Documentation/conf.py. You can change it in your project's Admin > Advanced Settings.

@kdambekalns
Copy link
Author

Ah, dang… completely forgot about that. That's what you get when a service runs for such a long time without issues… ;) Thanks!

(Could I have seen that from the log output I has access to?)

Problem now solved after a little detour: We did some juggling in the project so the documentation is at a different place in two branches, than it used to be. Can we set that per branch somehow? Because leaving it empty to have it found might as well pick up other conf.py files that should not be used. Hm…

For the record, here's how I solved it: since we split our mono-repo into multiple smaller ones, I changed the setup to point to a split repo and could point rftd.org to just Documentation/conf.py, eliminating the issue.

@ericholscher
Copy link
Member

We're trying to move more of our config over to a YAML file (http://docs.readthedocs.io/en/latest/yaml-config.html) -- but currently we haven't ported the conf.py setting. That's what would need to happen to get it working per branch.

There was an error in our reporting that hid how the missing conf.py file error. I've pushed #2634 to fix it.

@kdambekalns
Copy link
Author

Thanks!

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

No branches or pull requests

2 participants