google / google/turbinia

Optimize jenkins artifact extraction

Open
#402 2 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
Python
Stars
794
Forks
172
PR merge metrics
No merged PRs in 30d

Description

The jenkins analysis task is being fixed in #399, but the fix is kind of ugly because it requires traversing the entire filesystem in order to extract the right files. We should find a better solution and/or fix the upstream file globbing in Plaso (either the filter file syntax or the artifacts syntax).

Contributor guide

Open the contributing guide

Research direction

Start by reading the Jenkins analysis task and the fix referenced in issue #399. Investigate how Plaso file globbing handles its filter-file and artifacts syntax, then compare that with the current full-filesystem traversal. Done means artifact extraction avoids the broad traversal while still selecting the required files.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
security
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.