infrastructure/blender-bot
1
3
Fork 4
Code Pull Requests 1 Activity
Automation for Gitea
35 Commits 1 Branch 0 Tags 152 KiB
Python 98.9%
Shell 1.1%
main
Go to file
Alaska 2ba7f0e1d6 Update status label when reopening a report based on closed status (#6) 
When a report is reopened, the Blender bot can take a action.
The goal of this PR is to change the behavior of the build bot with
regard to setting labels when reopening a report.

- If a report is reopened, and a valid open status is set, then
the Blender bot will leave the status label alone.
- If a report is reopened, and the status label is "Resolved",
then the Blender bot will change the status to "Confirmed".
- Otherwise the Blender bot sets the status to "Needs Triage".

The reasoning behind reopening "Resolved" reports as "Confirmed"
is that the report was a valid bug, and a commit was made attempting
to resolve it (And this closed the report with the "Resolved" Status).
The primarily reason a Resolved report would be reopened would be that
the fix didn't work and the issue is still there, and so the report
should be reopened as "Confirmed" again.

Reviewed-on: #6
Reviewed-by: Bart van der Braak <bart@blender.org>
2024-10-01 12:39:43 +02:00
deploy Handle requests in background thread, to avoid missing events 2023-02-26 23:15:17 +01:00
.gitignore Improve deployment procedure 2023-02-05 21:28:16 +01:00
batch_update.py Cleanup: Use black for code formatting 2024-03-12 18:22:36 +01:00
blender_bot.py Cleanup: Use black for code formatting 2024-03-12 18:22:36 +01:00
commands.py Cleanup: Use black for code formatting 2024-03-12 18:22:36 +01:00
config.py Cleanup: Use black for code formatting 2024-03-12 18:22:36 +01:00
labels.py Update status label when reopening a report based on closed status (#6) 2024-10-01 12:39:43 +02:00
LICENSE Git notes to show which issues, PRs and commits mention a commit 2023-01-28 21:36:34 +01:00
notes.py Cleanup: Use black for code formatting 2024-03-12 18:22:36 +01:00
pyproject.toml Cleanup: Use black for code formatting 2024-03-12 18:22:36 +01:00
README.md Windows: Add ARM64 platform 2024-03-12 18:19:18 +01:00
setup.py Fix commits not being clickable in notes, and changes for master rename 2023-02-13 13:52:52 +01:00
utils.py Cleanup: Use black for code formatting 2024-03-12 18:22:36 +01:00

README.md

Blender Bot for Gitea

Commands

Blender developers with commit access can start builds by typing commands in comments on projects.blender.org.

  • @blender-bot build [flags] [platforms]: build current pull request. A notification about the build progress / result is shown in the list of commits that make up this pull request.
  • @blender-bot package [flags] [platforms]: build current pull request and make package for download. The bot will post the link in a comment on the pull request.
  • @blender-bot build-branch branch [flags] [platforms]: build the given branch. The bot will post a link to the build in a comment on the issue / pull request.
  • @blender-bot package-branch branch [flags] [platforms]: build branch and make package for download. The bot will post the link in a comment on the issue / pull request.

[platforms] is optional, and used to build for one or more platforms. Possible values:

  • windows macos linux (for brevity)
  • windows-amd64 windows-arm64 macos-x86_64 macos-arm64 linux-x86_64 (to be specific)

[flags]

  • +gpu build GPU binaries and run GPU tests

Other:

  • @blender-bot ping: test if blender-bot is online

Automation

  • When an issue is automatically closed or reopened through a commit, set the resolved and confirmed status.
  • When an issue is manually closed or reopened, set archived and confirmed or needs triage status, unless a valid closed or open status is already set.
  • Add git notes to commits to show issues, pull requests and commits that reference them.