sameersbn / sameersbn/docker-gitlab
Gitlab backup operations logging unknown status
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Hi, noticed that sometimes backups fail. And no reason to investigate further, no any logs
The PR to add common logging by rake's output redirect to common file:
#2097
Contributor guide
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
Start by reviewing PR #2097 and locating the backup operation entry points it changes. Inspect how rake output is redirected to the common log, then verify that failed backups expose a useful reason there; done means backup failures are no longer silent.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, shell
- Domain
- devops, infrastructure, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100