-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dedup tests #2693
base: main
Are you sure you want to change the base?
Dedup tests #2693
Conversation
Note to Future Me: I'm betting this means that the |
I updated the ADR to reflect the agreement we would be making if/when we merge this PR. The change is still under discussion, though! |
@carolyncole is concerned about the maintenance burden in playbooks, and specifically about the possibility of drift between staging and production playbooks. This led to a conversation about the way the repo currently handles groups in the hosts file, group_vars, role variables, and playbooks. Can we have a single playbook per project, with both the target hosts and the variables determined at runtime (for example, something like |
providing the stage at playbook runtime seems fine to me. |
Recent changes to our CI have made improvements to this problem - see https://github.com/pulibrary/princeton_ansible/runs/6040136600?check_suite_focus=true for a run in which the |
What were the changes? |
…role; comments out dependency in meta/main.yml
Co-authored-by: Eliot Jordan <[email protected]>
Co-authored-by: Anna Headley <[email protected]>
First attempt / first steps toward streamlining Molecule tests as discussed in #2685.
This branch uses the
openjdk
role as a test case, because it's small, has only one dependency, and is used in several playbooks. This branch:common
role from theopenjdk/meta/main.yml
filecommon
role to every playbook that calls theopenjdk
rolecommon
role to the tests for theopenjdk
role