Make it easier to collect environment when integration tests fail in PR

[sebastien-rosset]

Summary

When opening a new bug, the bug template has fields which are supposed to be populated with the output of commands such as ansible --version. This does not work well when an issue is found while running PR tests in zuul.

For example, suppose I submit a PR for module X and a problem in module Y occurs, unrelated to my PR changes. The PR template does not work great because it's not clear how to obtain the data from the zuul logs. It's certainly possible to provide the link to the full zuul logs, though these logs seem to have limited retention, so they disappear after a while.

Issue Type

Feature Idea

Component Name

reporting of test environment.

Additional Information

Code of Conduct

• [X] I agree to follow the Ansible Code of Conduct

[ansibullbot]

Files identified in the description: None

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[goneri]

The CI uses the last git branches. So you can just write something like stable-2.11. But I agree, it would be nice to improve the field description.

[tremble]

We now have a separate "CI Bug Report" template https://github.com/ansible-collections/amazon.aws/blob/main/.github/ISSUE_TEMPLATE/ci_report.yml which can be used instead of the issues template