lowRISC / lowRISC/ot-sca

[podman] Add container to CI

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

Nobody has claimed this yet.

Priority:P1
Dominant language
Jupyter Notebook
Stars
43
Forks
34
PR merge metrics
No merged PRs in 30d

Description

As discussed with @vrozic , currently there is no CI job for testing the container. To ensure that future changes to the container infrastructure are working, adding a new CI job could be useful.

Contributor guide

Open the contributing guide

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

Inspect the repository's existing CI configuration and container setup first, since the issue names no specific files or tests. Run the current container-related checks and add a CI job that exercises the container; done means future container infrastructure changes are tested automatically.

Written by the indexing model from the issue text.

Assessment

Domain
ci-cd, devops
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.