E4S-Project / E4S-Project/e4s

Enhance CI with sanity checks for each of the container image layers

Open
#173 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
41
Forks
15
PR merge metrics
No merged PRs in 30d

Description

We should have sanity checks for each intermediate container image:

  • 1-runner
  • 2-gpu
  • 3-mpi
  • 4-spack
  • 5-release

For each layer, we should verify that what we expect to be in default PATH is there, that components installed show up where we expect them to be, etc.

CC @wspear

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the CI configuration and container definitions for the five layers: 1-runner, 2-gpu, 3-mpi, 4-spack, and 5-release. Define checks for expected PATH entries and installed components at each layer; the work is done when CI validates every intermediate image.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
ci-cd, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.