adoptium / adoptium/infrastructure

Split out parts of `Common` ansible role that are required for other roles

Open
#3,464 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
96
Forks
106
Avg merge
1d 23h
Merged PRs (30d)
13

Description

The Common role takes quite a while to run, so when working on other parts of the playbook it seems prudent to skip it. Unfortunately some of the other roles depend on things in there. It would be good if we could split out those so that all other roles can run if `Common` is skipped.
As an example, the Common role on windows has operations to create `C:\temp` and `C:\openjdk`. The latter should be done in the roles htat require it, but `C:\temp` should be part of a separate "bootstrap" role.

Contributor guide

Open the contributing guide

Research direction

Start by locating the Ansible Common role and its Windows operations for C:\temp and C:\openjdk. Trace which other roles depend on them, then separate the shared temporary-directory setup into a bootstrap role and keep JDK setup with the roles that require it; done means those roles run when Common is skipped.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible
Domain
devops, infrastructure
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.