-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Build is not working #3223
Comments
If I pull this git-project to existing "readthedocs-projects" by changing the "git url", then it is working fine. But, build is not working for the newly created "ReadTheDoc-projects" for the same git-project |
Auto-trigger from github is working now... |
It is the problem with all the newly-created ReadTheDocs-projects.
|
Brand new user here, but the problem persists. I have a new project, never built, I click "build" from the website and I get "This API endpoint is deprecated" |
Go to admin and press submit. It will build your project at this moment. |
Thanks, @Mekrip! I've run into the same problem and this workaround is great. I hope RTD fixes whatever is causing this problem, though. |
@agjohnson - any thoughts or update on this issue? We're experiencing it as well. |
i kinda tracked the problem down to the fairly new code:
@agjohnson what is it doing? Why is it breaking RTDs build button for new projects? |
I was even able to fix it on my self hosted instance: But im still wondering why new projects are broken by default - BUG! |
@kakulukia read #3260 and #3309 |
so looks like its fixed now and can be closed (@Mekrip) .. but this also means i should better not update my instance or i will loose my cron-checks-for-new-commits-and-starts-a-build feature because of this :) |
It doesn't look like it's fixed on readthedocs.org. My builds are still not building: |
its only fixed in the sites repo - i dont know how fast they are pushing their code to the live site and since tey are not using tags or branches (in a recognizable manner) somebody else has to say how up to date the live site is |
and for anyone feeling responsible for the branches like @humitos - have a cup of coffee and read this: https://railsware.com/blog/2014/08/11/git-housekeeping-tutorial-clean-up-outdated-branches-in-local-and-remote-repositories/ |
Manual-Build is working fine. But the automatic-triggering from the GitHub/Bitbucket is not working for the Build. |
I'm a bit lost here. @Mekrip so, original problem is solved? If you are experimenting a different problem from the original, please close the ticket and create a new one for the new issue. Thanks! |
No, original problem still the same, "build is not working automatically".
But, we have solution to manage it manually.
I am not experimenting with it. I am just providing details of the problem.
Meher Krishna Patel
The University of Auckland
email: mekrip@gmail.com
Blog: http://pythondsp.readthedocs.io/
…On Fri, Dec 1, 2017 at 8:30 AM, Manuel Kaufmann ***@***.***> wrote:
I'm a bit lost here.
@Mekrip <https://github.com/mekrip> so, original problem is solved?
If you are experimenting a different problem from the original, please
close the ticket and create a new one for the new issue. Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3223 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AY9h69_Txh7ZOpmHEYzDuvFI7B3P5IDUks5s7wJkgaJpZM4QQX7W>
.
|
This seems to be the original problem:
and the same description of the issue, you mentioned a workaround. I'm going to close this since the Please, feel fre to create a new issue for "build is not working automatically" using the template and exaplaining what it's happening to you. Thanks! |
Details
Project URL: http://verilog-guide.readthedocs.io/en/latest/index.html
Build URL (if applicable): https://readthedocs.org/projects/verilog-guide/builds/
Read the Docs username (if applicable): PythonDSP
Expected Result
A description of what you wanted to happen
When the 'Button Version' is pressed, the following error is shown
"This API endpoint is deprecated"
Actual Result
A description of what actually happened
Also, if I change something in the settings e.g. Python2.x to Python3.x, then automatic-cloning starts and update the document correctly.
I tried using both GitHub and Bitbucket. The problem is the same.
The text was updated successfully, but these errors were encountered: