[CONSIDER] Custom alternative to docker-logs

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

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
docker, github-actions, shell
Domain
ci-cd, devops, tooling

Research direction

Start by reviewing e2e-tests.yml and how jwalton/gh-docker-logs@v2 is used for failed end-to-end tests. The issue does not define custom formatting, filtering, integrations, or a replacement scope, so clarify those requirements before implementation; completion criteria are not currently specified.

Written by the indexing model from the issue text.

Description

new-action

Context

Using third-party action for dumping Docker logs on CI failure in aRustyDev/timesketch.

Third-Party Action Chosen

  • Repository: jwalton/gh-docker-logs@v2
  • Version: v2
  • Purpose: Dump all docker container logs when workflow fails
  • Stars: ~150
  • Last updated: 2024
Why Third-Party
  • Simple, focused functionality
  • Well-maintained
  • No alternatives with more features needed

Alternatives Evaluated

Action Repository Pros Cons
Manual docker logs N/A No dependency Verbose workflow code
jwalton/gh-docker-logs jwalton/gh-docker-logs Simple, focused Third-party

Currently Used In

Repository Workflow Purpose
aRustyDev/timesketch e2e-tests.yml Dump logs on e2e test failure

Build Custom If

  • Third-party becomes unmaintained (no commits 6+ months)
  • Need custom formatting or filtering
  • Want to integrate with other logging services

Notes

Low priority - current action works well. Deferred for future review.

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

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.

More from aRustyDev/gh

All issues in aRustyDev/gh

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.