ansibullbot
ansibullbot copied to clipboard
ansible
Bot for management of Ansible issues and PRs on GitHub.
We could notify all involved parties of an issue when a pull request was made that fixes a specific issue. So if PR X reports it fixes issues Y, the...
https://github.com/ansible/ansible/pull/57302
incorrect caching: classified PR as new_module even though the module it modifies was merged earlier
I today merged a new module (ansible/ansible#50622), then rebased two PRs to current `devel`, and included modifications for these new modules as well. Afterwards, ansibot adds `new_module` and `new_plugin` labels...
See ansible/ansible#53894 When doing `rebuild_merge`, ansibot restarted CI and merged at the same time. (Merge was done at 9:42 UTC, CI started at 9:42 UTC, and needed 6 minutes, so...
I understand the need for presenting more information to (new) users, but having multiple comments added in close succession is a bit too much. Each comment induces another mail. Example:...
e.g. `team_e-spirit`. ``` Traceback (most recent call last): File "/home/ansibot/ansibullbot/triage_ansible.py", line 42, in main() File "/home/ansibot/ansibullbot/triage_ansible.py", line 38, in main AnsibleTriage().start() File "/home/ansibot/ansibullbot/ansibullbot/triagers/ansible.py", line 225, in __init__ gitrepo=gitrepo File "/home/ansibot/ansibullbot/ansibullbot/utils/file_tools.py",...
In ansible/ansible#48044, ansibot claims the PR contains a new module. The module this PR affects, `acme_certificate`, was moved from `lib/ansible/modules/web_infrastructure/` to `lib/ansible/modules/crypto/acme/` after `stable-2.6` was branched from `devel`. Maybe this...
When `rebuild_merge` fails (say, because of some random test failure totally unrelated to the PR), there doesn't seem to be a way to trigger another CI run. Sending the `rebuild_merge`...
I think having a quick way to enable/disable certain code paths based on a toggle and a rollout percentage is essential to having stable bot in production. This could also...
Originally, https://github.com/ansible/ansible/issues/50015 had a component listed with path separators using non-unix slashes. The bot should be able to normalize the slashes before trying to figure out the component to use.
