awslabs / awslabs/aws-codebuild-jenkins-plugin
Incomplete logs due to log line being too long
- Dominant language
- Java
- Stars
- 156
- Forks
- 130
- PR merge metrics
- No merged PRs in 30d
Description
I am facing an issue where the final part of the log file is missing in jenkins, however when I open same build in AWS UX, the log lines are present. The whole build produces around 30k of log lines, however in jenkins I can see only first ~22k of lines. When I started looking into this further, the first line missing was exceptionally long - around 14k characters. Should the plugin handle this more gracefully and at least display whole log file instead of stopping at the point where it can not continue?
Contributor guide
Research direction
The issue describes a Jenkins/AWS CodeBuild log transfer failure but names no source file or test. Reproduce a build with a log line around 14,000 characters, compare the Jenkins log with the AWS CodeBuild view, and consider the work done when Jenkins displays the complete log, including content after that long line.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100