opensafely-core / opensafely-core/opensafely-cli
Consider making Docker image IDs more visible in the logs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 5
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 4
Description
In some debugging cases, knowing which Docker images were used for a specific project run is very useful.
I'm trying to help a user who is having problems with their project, but it's tricky to try and reproduce a "good" state as seen on previous GitHub Actions runs.
The metadata logs have this information, but:
- in GitHub Actions, we only see the output log, and can't access the metadata logs
- if a run is stopped (either by a user interactively locally when testing on their computer, or by a GitHub Actions timeout), I don't believe we would have the metadata logs anyway (but I could be wrong)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No implementation file or test is named. Start by locating where Docker image metadata and normal output logs are produced, then compare local runs with GitHub Actions and interrupted runs. The work is done when the image IDs needed to identify a project run are available in the output logs in the cases described.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github-actions, python
- Domain
- ci-cd, cli, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100