Buildbot: automated build for every pull request #44

Open
opened 2023-02-27 18:04:28 +01:00 by Brecht Van Lommel · 1 comment

Currently developers can manually trigger builds with blender-bot, but ideally this would be automated so that fewer mistakes slip through and contributors can fix things before a reviewer has to get involved.

We can incrementally do a few things:

  • Add a lint builder that can quickly and safely run on all pull requests. This would check make format passes, and potentially other checks like clang-tidy.
  • Auto run builds for all PRs by authors with write access. This likely requires more machines on the buildbot to handle the load.
  • Auto run builds also for other contributors. This requires better isolation of the workers for security reasons.
  • Auto build GPU for changes to intern/cycles/kernel.
Currently developers can manually trigger builds with blender-bot, but ideally this would be automated so that fewer mistakes slip through and contributors can fix things before a reviewer has to get involved. We can incrementally do a few things: * [x] Add a lint builder that can quickly and safely run on all pull requests. This would check `make format` passes, and potentially other checks like `clang-tidy`. * [ ] Auto run builds for all PRs by authors with write access. This likely requires more machines on the buildbot to handle the load. * [ ] Auto run builds also for other contributors. This requires better isolation of the workers for security reasons. * [ ] Auto build GPU for changes to `intern/cycles/kernel`.
Brecht Van Lommel added the
buildbot
label 2023-02-27 18:53:10 +01:00

Not sure if we have this level of control but any pulls for cycles should be building the GPU kernels, I know extra load, but with that many kernels, best to find out if a specific one has build issues sooner rather than later.

Not sure if we have this level of control but any pulls for cycles should be building the GPU kernels, I know extra load, but with that many kernels, best to find out if a specific one has build issues sooner rather than later.
Sign in to join this conversation.
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infrastructure/blender-projects-platform#44
No description provided.