Epic Goal

• Rename ci-artifacts
• Update / refactor ci-artifacts documentation
  • Should be "easy" for a new team member to read the docs and understand what is needed to write a new test.
• Continue on recent work to evolve the project to be focused on RHODS test automation, removing obsolete pieces.
• Make it as easy as possible to run ci-artifacts tests and toolbox commands from anywhere with podman build / run.

• • Document necessary env vars and secrets that need to be passed to the container for different tests / roles

Why is this important?

• We need to have a clear repository or set of repositories that contains the automation and tests we are running, which we can point stakeholders to.

Scenarios

1. TODO

Acceptance Criteria

• ci-artifacts has a more descriptive name
• ci-artifacts documentation is up-to-date (even if it is not in depth)
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. There has been tons of past / ongoing work by kpouget2 to get ci-artifacts to where it is today, with a wealth of useful automation

Open questions::

1. …