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

Add log API for Org scanning and MBP indexing

    XMLWordPrintable

Details

    Description

      Creation flow needs API to fetch log for organization folder scanning and multi-branch-pipeline indexing logs.

      cc: cliffmeyers

      Attachments

        Issue Links

          Activity

            vivek Vivek Pandey created issue -
            vivek Vivek Pandey made changes -
            Field Original Value New Value
            Epic Link JENKINS-36588 [ 172614 ]
            cliffmeyers Cliff Meyers made changes -
            Link This issue blocks JENKINS-41141 [ JENKINS-41141 ]
            jamesdumay James Dumay made changes -
            Sprint pannonian [ 211 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay added a comment -

            vivek cliffmeyers I saw this one hanging in the backlog - I assume you want this on the sprint?

            jamesdumay James Dumay added a comment - vivek cliffmeyers I saw this one hanging in the backlog - I assume you want this on the sprint?
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Priority Major [ 3 ] Critical [ 2 ]
            cliffmeyers Cliff Meyers added a comment -

            Yes, please.

            cliffmeyers Cliff Meyers added a comment - Yes, please.
            jamesdumay James Dumay added a comment - - edited

            vivek is it possible to also get the actual error that was thrown during Org Scanning or MBP indexing? I'd prefer if we could turn these into better error messages and only show the log if we fail to do that. (ping cliffmeyers tfennelly)

            jamesdumay James Dumay added a comment - - edited vivek is it possible to also get the actual error that was thrown during Org Scanning or MBP indexing? I'd prefer if we could turn these into better error messages and only show the log if we fail to do that. (ping cliffmeyers tfennelly )
            cliffmeyers Cliff Meyers added a comment -

            Per tfennelly and Jesse we can't really get more information from the event: https://github.com/jenkinsci/blueocean-plugin/pull/700#issuecomment-274851641

            So if we want a way to represent specific errors in the UI, the log API covered by this ticket perhaps needs some was for the client to express that it's looking for more detailed info about an error.

            cliffmeyers Cliff Meyers added a comment - Per tfennelly and Jesse we can't really get more information from the event: https://github.com/jenkinsci/blueocean-plugin/pull/700#issuecomment-274851641 So if we want a way to represent specific errors in the UI, the log API covered by this ticket perhaps needs some was for the client to express that it's looking for more detailed info about an error.
            vivek Vivek Pandey added a comment -

            jamesdumayBranchIndexing.run() or FolderComputation.run() does not have anything which can be used to get notified in case of error. Same goes for other Run classes, for example WorkflowRun, which is better than FolderComputation or BranchIndexing, here it notifies pipeline run lifecycle and even sets Result object but even there nothing there that sets build exceptions.

            I also noticed something in WorkflowRun,there I could call WorkflowRun.getExecutionPromise() that gives instance of SettableFuture, where WorkflowRun sets execution errors.

            cliffmeyers suggested an API for log file search that looks for given text (sort of like grep), but this has limited uses and won't work in all cases. Needs proper spec.

            Or maybe annotated log file, poc I did during Jenkins hackathon might be something we can take up to show logs in segments.

            vivek Vivek Pandey added a comment - jamesdumay BranchIndexing.run() or FolderComputation.run() does not have anything which can be used to get notified in case of error. Same goes for other Run classes, for example WorkflowRun, which is better than FolderComputation or BranchIndexing, here it notifies pipeline run lifecycle and even sets Result object but even there nothing there that sets build exceptions. I also noticed something in WorkflowRun,there I could call WorkflowRun.getExecutionPromise() that gives instance of SettableFuture, where WorkflowRun sets execution errors. cliffmeyers suggested an API for log file search that looks for given text (sort of like grep), but this has limited uses and won't work in all cases. Needs proper spec. Or maybe annotated log file, poc I did during Jenkins hackathon might be something we can take up to show logs in segments.
            jamesdumay James Dumay made changes -
            Sprint pannonian [ 211 ]
            jamesdumay James Dumay made changes -
            Sprint iapetus [ 216 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay made changes -
            Sprint iapetus [ 216 ] release candidate [ 171 ]
            jamesdumay James Dumay made changes -
            Rank Ranked lower
            jamesdumay James Dumay made changes -
            Sprint release candidate [ 171 ]
            jamesdumay James Dumay made changes -
            Rank Ranked higher
            jamesdumay James Dumay added a comment -

            Obsolete

            jamesdumay James Dumay added a comment - Obsolete
            jamesdumay James Dumay made changes -
            Resolution Postponed [ 6 ]
            Status Open [ 1 ] Resolved [ 5 ]

            People

              vivek Vivek Pandey
              vivek Vivek Pandey
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: