Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-38313

External Build Log storage for Jenkins

    XMLWordPrintable

Details

    • External Build Log storage for Jenkins

    Description

      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:

      Attachments

        Issue Links

          blocks

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-49327 Please show TOP of build log in console output - even when trimming

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open
          is blocked by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. JENKINS-38314 External Build Log storage for Jenkins. Prototype #1

          • Major - Major loss of function.
          • Resolved

          Task - A task that needs to be done. JENKINS-38381 [JEP-210] Optimize log handling in Pipeline and Durable Task

          • Critical - Crashes, loss of data, severe memory leak.
          • Resolved
          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-32444 Proposal: Move build logs off of Jenkins master

          • Major - Major loss of function.
          • Resolved
          is related to

          Bug - A problem which impairs or prevents the functions of the product. JENKINS-45150 large console logging can take Jenkins down or affecting performance

          • Major - Major loss of function.
          • Open

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-26545 Persist build(s) log(s) in MySQL (or similar)

          • Critical - Crashes, loss of data, severe memory leak.
          • Reopened
          relates to

          New Feature - A new feature of the product, which has yet to be developed. JENKINS-51229 Log Discarder to delete log files generated by Jenkins pipeline scripts, but keep build information

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Open

          Improvement - An improvement or enhancement to an existing feature or task. JENKINS-50291 Customize where AsyncPeriodicWork are logged

          • Minor - Minor loss of function, or other problem where easy workaround is present.
          • Resolved
          links to

          Web Link Core API: https://github.com/jenkinsci/jenkins/pull/3557/

          Web Link Design Document draft

          Web Link PoC Demo Slides

          Activity

            Ascending order - Click to sort in descending order
            View 4 older comments
            oleg_nenashev Oleg Nenashev added a comment -

            This EPIC is in progress again

            oleg_nenashev Oleg Nenashev added a comment - This EPIC is in progress again
            oleg_nenashev Oleg Nenashev added a comment -

            And... it was aborted again for some reasons out of my control...

            oleg_nenashev Oleg Nenashev added a comment - And... it was aborted again for some reasons out of my control...
            oleg_nenashev Oleg Nenashev added a comment -

            I have abandoned all tasks in this EPIC. As stated in https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ , csanchez and jglick can take over any tasks, PRs and JEPs related to this EPIC

            oleg_nenashev Oleg Nenashev added a comment - I have abandoned all tasks in this EPIC. As stated in https://groups.google.com/d/msg/jenkinsci-dev/uc6NsMoCFQI/AIO4WG1UCwAJ , csanchez and jglick can take over any tasks, PRs and JEPs related to this EPIC
            datadog Datadog HQ added a comment -

            Hi csanchez and jglick, we are wondering about the current status of this EPIC? We are interested in using this logging capability, and we would like to know if this is continued to be supported even in beta?

            datadog Datadog HQ added a comment - Hi  csanchez  and jglick , we are wondering about the current status of this EPIC? We are interested in using this logging capability, and we would like to know if this is continued to be supported even in beta?
            jglick Jesse Glick added a comment -

            datadog nothing is “supported” exactly, but https://plugins.jenkins.io/pipeline-cloudwatch-logs/ continues to work (AFAIK), and JEP-210 is open to other implementations (beta-level API). At a very high level, the main limitations are

            • There is no support for non-Pipeline projects.
            • Pending JENKINS-52165, an implementation needs to turn on a log streaming implementation for sh-like steps which does not otherwise get much testing.
            • Pending API changes to Jenkins core (incl. Stapler) and matching changes in Blue Ocean, in-Jenkins log display for running builds is inefficient. (Uses a byte offset cursor rather than an implementation-defined cursor that could be implemented efficiently.)
            jglick Jesse Glick added a comment - datadog nothing is “supported” exactly, but https://plugins.jenkins.io/pipeline-cloudwatch-logs/ continues to work (AFAIK), and JEP-210 is open to other implementations (beta-level API). At a very high level, the main limitations are There is no support for non-Pipeline projects. Pending JENKINS-52165 , an implementation needs to turn on a log streaming implementation for sh -like steps which does not otherwise get much testing. Pending API changes to Jenkins core (incl. Stapler) and matching changes in Blue Ocean, in-Jenkins log display for running builds is inefficient. (Uses a byte offset cursor rather than an implementation-defined cursor that could be implemented efficiently.)

            People

              Unassigned Unassigned
              oleg_nenashev Oleg Nenashev
              Votes:
              15 Vote for this issue
              Watchers:
              42 Start watching this issue

              Dates

                Created:
                Updated: