-
Epic
-
Resolution: Unresolved
-
Major
-
External Build Log storage for Jenkins
-
Jenkins' logging system is one of potential scalability bottlenecks on big Jenkins instances. System logging can be redirected via JUL log appenders (or other such solutions), but there is no OOTB solution for build logs.
It would be great to have such solution. Top-level requirements:
- All or almost all build/task logging is moved from Jenkins filesystem to External Build Log Storage
- Minimize log traffic between Jenkins agents and the master, logs should be reported from slaves directly when it is possible
- External Build Log Storage has an extensible and pluggable architecture
- At least 2 reference implementations:
- File-system-based storage (current implementation)
- One external build log storage based on the open-source stack. Preference - Elasticsearch-Logstash-Kibana
- Jenkins Pipeline is supported out of the box
- Old logs should be browseable after changing the storage engine (Migration or parallel engines)
Design document:
- blocks
-
JENKINS-49327 Please show TOP of build log in console output - even when trimming
- Open
- is blocked by
-
JENKINS-38314 External Build Log storage for Jenkins. Prototype #1
- Resolved
-
JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task
- Resolved
- is duplicated by
-
JENKINS-32444 Proposal: Move build logs off of Jenkins master
- Resolved
- is related to
-
JENKINS-45150 large console logging can take Jenkins down or affecting performance
- Open
-
JENKINS-26545 Persist build(s) log(s) in MySQL (or similar)
- Open
- relates to
-
JENKINS-51229 Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information
- Open
-
JENKINS-50291 Customize where AsyncPeriodicWork are logged
- Resolved
- links to