Buildbot: Skip Blender compilation for API docs #130

New Issue

Sergey Sharybin · 2024-11-11T10:05:19+01:00

Sergey Sharybin commented

2024-11-11 10:05:19 +01:00

Currently the API documentation builders are building Blender from sources. For example see the compile-code step.

This takes quite some time and complicates setup.

It should be possible to download builds from buildbot.blender.org and generate API from them.
he downside is that API will be generated a bit more delayed than it is currently. But it could actually be good since then the docs will be more aligned with the actual builds.

Would also need to disable incremental builds.

CC @mont29

Currently the API documentation builders are building Blender from sources. For example see the [compile-code](https://builder.blender.org/admin/#/builders/5/builds/18311) step. This takes quite some time and complicates setup. It should be possible to download builds from buildbot.blender.org and generate API from them. he downside is that API will be generated a bit more delayed than it is currently. But it could actually be good since then the docs will be more aligned with the actual builds. Would also need to disable incremental builds. CC @mont29

Sergey Sharybin added the

Service

Buildbot

label 2024-11-11 10:05:19 +01:00

Sergey Sharybin changed title from ~~Buildbot: Skip Blende compilation for API docs~~ to Buildbot: Skip Blender compilation for API docs

2024-11-11 10:05:44 +01:00

Bastien Montagne commented

2024-11-11 10:34:54 +01:00

Sounds reasonable to me.

If an update of API docs is really required outside of nightly builds, then one can simply rebuild/deliver blender builds first, and then run the API ones.

Not sure how to ensure that the API build only runs once the linux blender one has been delivered though? Worst case I guess we could run it like 5h or 6h after the daily builds?

Sounds reasonable to me. If an update of API docs is really required outside of nightly builds, then one can simply rebuild/deliver blender builds first, and then run the API ones. Not sure how to ensure that the API build only runs once the linux blender one has been delivered though? Worst case I guess we could run it like 5h or 6h after the daily builds?

Sergey Sharybin commented

2024-11-11 11:17:41 +01:00

Not sure how to ensure that the API build only runs once the linux blender one has been delivered though?

Poor man's solution: you space them out in time of schedule: for example, schedule code builder at 1am, schedule API builder at 5am. Similar to how we do it for the store deployment.

A smarter solution might be possible, someone would need to dig into an advanced buildbot configuration. Need to be careful about time investment: if the schedule-based approach works fine, why to spend weeks trying to make something more automatic? :)

> Not sure how to ensure that the API build only runs once the linux blender one has been delivered though? Poor man's solution: you space them out in time of schedule: for example, schedule code builder at 1am, schedule API builder at 5am. Similar to how we do it for the store deployment. A smarter solution might be possible, someone would need to dig into an advanced buildbot configuration. Need to be careful about time investment: if the schedule-based approach works fine, why to spend weeks trying to make something more automatic? :)

Sign in to join this conversation.