-
Notifications
You must be signed in to change notification settings - Fork 53
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
Website builds are broken #256
Comments
That bit was simple, but alarming. 2 separate stages, package building and upload to the server are missing. |
Thankfully I kept copies of the scripts I adapted from @mhaberler s mksocfpga ones. After some grey matter realignment, I have it back producing packages, now need to get the upload script into MK, so Jenkins can use it |
Doh! I am going to disable protobuf doc builds until machinekit-protobuf will build docs and try to find the error later in the build process. |
Disabling protobuf doc builds has restored the website generation and machinekit-manual-pages.deb generation When the machinekit-protobuf build works again, I will put it back |
The builds of the website have not worked since February 9th 2017.
The first problem, is the changes to machinekit-protobuf since this commit
machinekit/machinetalk-protobuf@e84a6e5
This did not arise immediately, because only when a complete rebuild is triggered will the protobuf docs be rebuilt from scratch.
@machinekoder can you see if you can get this working again.
As soon as the repo will build in isolation, the docs will get past that point
Further back in time there was another error, which appeared to be from a corrupt git SHA
but until the first error is fixed, cannot get far enough into the build to diagnose that one.
Also despite all the changes to instcomps since Jan 17th, a new build of
machinekit-manual-pages
package has not been triggered since 21st Dec 2016http://deb.machinekit.io/debian/pool/main/m/machinekit-manual-pages/machinekit-manual-pages_1.10292_all.deb
I will look at that, as I set the build up (if I can remember how 😄)
The text was updated successfully, but these errors were encountered: