aRustyDev / aRustyDev/gh

[CONSIDER] Custom alternative to docker-logs

Open
#9 0 comments 0 reactions 0 assignees View on GitHub
new-action
Dominant language
Shell
Stars
0
Forks
0
PR merge metrics
No merged PRs in 30d

Description

## 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.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.