Skip to content

Head of build log is not useful in failures #343

Open

Description

@timja

Looks like https://ci.jenkins.io/job/Tools/job/bom/job/master/1751/ failed at the infrastructure level. Unfortunately https://plugins.jenkins.io/github-checks/ (unlike https://docs.cloudbees.com/docs/cloudbees-ci/latest/scm-integration/enabling-scm-reporting#_cloudbees_scm_reporting_feature_benefits) includes the head rather than the tail of a failed shell step’s log, which is usually useless, and does not link to the execution/node/*/log/ for the build-terminating error.

Originally posted by @jglick in jenkinsci/bom#2121 (comment)

Activity

  1. tabletenniser commented on Feb 1, 2025

    @tabletenniser

    @timja Is this something the Jenkins maintainers can help implement or are you open for community contribution for this? I assume we just need to change

    Output output = new Output(
    checksOutput.getTitle().orElseThrow(
    () -> new IllegalArgumentException("Title of output is required but not provided")),
    checksOutput.getSummary(MAX_MESSAGE_SIZE_TO_CHECKS_API).orElseThrow(
    () -> new IllegalArgumentException("Summary of output is required but not provided")))
    .withText(checksOutput.getText(MAX_MESSAGE_SIZE_TO_CHECKS_API).orElse(null));
    and put it behind a config somewhere? Or do you think we can make a non-backward compatible change to show the last part of the log for everyone?

  2. timja commented on Feb 1, 2025

    @timja
    MemberAuthor

    Open to community contribution, I think we can just change it for everyone

  3. sarahdeitke commented on Feb 5, 2025

    @sarahdeitke

    Hi @timja hoping you can review the PR I just opened for this topic ^

  4. sarahdeitke commented on Feb 14, 2025

    @sarahdeitke

    Hi @timja when you get a moment I opened a follow up pr on this issue. Let me know if you want to change anything. jenkinsci/checks-api-plugin#272

    cc: @tabletenniser

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions