llvm dev - Dec 2016 - LLVM Documentation - How does it get updated?

Just a suggestion: Setting up the documentation build up as a buildbot (or
jenkins) job would make it transparent what happens and what errors are occuring
on the build machine...

- Matthias
> On Dec 13, 2016, at 10:21 AM, Renato Golin via llvm-dev <llvm-dev at
lists.llvm.org> wrote:
> 
> On 13 December 2016 at 18:03, Zachary Turner <zturner at google.com>
wrote:
>> If I look at the PDB documentation now (which is rooted here) it's
all
>> consistent with a certain point in time (again, I'd have to find
the exact
>> CL), but nothing after that point in time ever made it in.
> 
> I'm betting it was around the time we made GCC 4.8 the minimum
requirement... :)
> 
> Generating makefiles
> CMake Error at cmake/modules/CheckCompilerVersion.cmake:12 (message):
>  Host GCC version must be at least 4.8!
> Call Stack (most recent call first):
>  cmake/config-ix.cmake:14 (include)
>  CMakeLists.txt:582 (include)
> 
> However, the GCC on that machine is 4.9.4, so I have no idea why the
error...
> 
> Unfortunately, we don't have a good way to capture errors with the
> docs builds, so it ends up as "whoever notices first".
> 
> I'll speak to Anton and Tanya about this.
> 
> cheers,
> --renato
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev

There is already a bot that builds documentation.  Turns out it was down
for a while, but I contacted the owner and got it back up a few weeks ago.
That buildbot is working fine, it just doesn't upload anything, only builds.

On Tue, Dec 13, 2016 at 2:00 PM Matthias Braun <mbraun at apple.com>
wrote:
> Just a suggestion: Setting up the documentation build up as a buildbot (or
> jenkins) job would make it transparent what happens and what errors are
> occuring on the build machine...
>
> - Matthias
>
> > On Dec 13, 2016, at 10:21 AM, Renato Golin via llvm-dev <
> llvm-dev at lists.llvm.org> wrote:
> >
> > On 13 December 2016 at 18:03, Zachary Turner <zturner at
google.com> wrote:
> >> If I look at the PDB documentation now (which is rooted here)
it's all
> >> consistent with a certain point in time (again, I'd have to
find the
> exact
> >> CL), but nothing after that point in time ever made it in.
> >
> > I'm betting it was around the time we made GCC 4.8 the minimum
> requirement... :)
> >
> > Generating makefiles
> > CMake Error at cmake/modules/CheckCompilerVersion.cmake:12 (message):
> >  Host GCC version must be at least 4.8!
> > Call Stack (most recent call first):
> >  cmake/config-ix.cmake:14 (include)
> >  CMakeLists.txt:582 (include)
> >
> > However, the GCC on that machine is 4.9.4, so I have no idea why the
> error...
> >
> > Unfortunately, we don't have a good way to capture errors with the
> > docs builds, so it ends up as "whoever notices first".
> >
> > I'll speak to Anton and Tanya about this.
> >
> > cheers,
> > --renato
> > _______________________________________________
> > LLVM Developers mailing list
> > llvm-dev at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20161213/b3b053da/attachment.html>

On 13 December 2016 at 22:02, Zachary Turner <zturner at google.com>
wrote:
> There is already a bot that builds documentation.  Turns out it was down
for
> a while, but I contacted the owner and got it back up a few weeks ago. 
That
> buildbot is working fine, it just doesn't upload anything, only builds.
Those bots are only doing validation, not pushing the docs anywhere.
The process that updates the docs is completely separate.

This is a really fragile publishing mechanism and one that is giving
us headaches for a long time. I think we need to sit down and fix
this.

My initial proposal is to have the buildbot on the same machine as the
docs, and to have a very small cloud machine as our docs front-end.
But that'll depend on how the foundation is handling this already.

I started a discussion about this on the llvm-admin list, lets see how it goes.

cheers,
--renato