Website builds are broken

[ArcEye]

The builds of the website have not worked since February 9th 2017.

The first problem, is the changes to machinekit-protobuf since this commit https://github.com/machinekit/machinetalk-protobuf/commit/e84a6e560fd2da300a9ddba2736e84891ab22940

cp "python/setup.py" "build/python/setup.py"
make[1]: *** No rule to make target 'build/python/machinetalk/__init__.py', needed by 'Makefile'.  Stop.

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

+ cd /var/lib/jenkins/workspace/website-production/output
+ git config user.email ci@machinekit.io
+ [ -d .git ]
+ git add .
+ git commit --amend -m Force updated by Jenkins build 1469
error: object file .git/objects/ee/30f70e7ace4c41a3d901a014acfe09d80ba58c is empty
error: object file .git/objects/ee/30f70e7ace4c41a3d901a014acfe09d80ba58c is empty
fatal: loose object ee30f70e7ace4c41a3d901a014acfe09d80ba58c (stored in .git/objects/ee/30f70e7ace4c41a3d901a014acfe09d80ba58c) is corrupt
Build step 'Conditional step (single)' marked build as failure
Stopping Docker container after build completion

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 2016 http://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 :smile:)

[ArcEye]

I will look at that, as I set the build up

That bit was simple, but alarming. 2 separate stages, package building and upload to the server are missing. The job is building the docs, but the scripts which do the rest have completely disappeared, with no obvious log trace.

[ArcEye]

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 https://github.com/machinekit/machinekit/pull/1181

[ArcEye]

Doh! I had a lightbulb moment last night and remembered that after static manual pages were moved out of the machinekit repo into the website, the build of manual pages was pulled from the Jenkins job for machinekit-manpage to the Jenkins website build and processed there. My scripts are right at the bottom of the config page.

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.

[ArcEye]

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