Make it easier to collect environment when integration tests fail in PR #648
Comments
|
Files identified in the description: If these files are inaccurate, please update the |
ansibullbot
added
feature
|
The CI uses the last git branches. So you can just write something like |
|
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 |
abikouo
pushed a commit
to abikouo/amazon.aws
that referenced
this issue
Oct 24, 2023
Add keys_attr parameter to aws_kms_info SUMMARY Move the kms_info return value from "keys" (which conflicts with keys()) to kms_keys. Add a parameter to support the old version Fixes ansible-collections#597 ISSUE TYPE Feature Pull Request COMPONENT NAME aws_kms_info ADDITIONAL INFORMATION Reviewed-by: Markus Bergholz <[email protected]> Reviewed-by: None <None>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: