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

Usability problem finding cause of build failure via web

XMLWordPrintable

      A recent checkin caused a build failure, so I went to a URL like:

      http://jenkins.example.com:8080/job/ProjectName/253/

      which is what got emailed out.

      That page reports: Jenkins ver. 1.467

      My goal in going to this page is to find the output from the actual build job, so I can diagnose and fix the failure. We have two platforms for ProjectName, i686 and x86_64.

      The correct way to do this is to click on i686, then either "Console Output" or "[raw]" in the menu on the left. This is not intuitive, and failed several times to find this and had to email a co-worker for help.

      I had tried clicking Console Output first; that log is not useful.

      That Console Output page has i686 links in the body text; but that brings me to the Jenkins configuration page for that architecture:
      http://jenkins.example.com:8080/job/ProjectName/ARCH=i686/

      I then tried clicking "i686" from the first page, but the resulting page was obviously not helpful. It was not intuitive that the "Console Output" link on the left would take me anywhere different from this page than it did from the previous page.

      Perhaps universally linking to the sub-logs from that universal menu would be the easiest way to solve the problem. Better direct linking from the first page might also help, but that's not necessarily the starting point that everyone who uses Jenkins would be coming from?

      I don't know if the component I have chosen for this ticket is correct. "Unknown" is not an option, so I had to choose somewhat randomly.

            Unassigned Unassigned
            beland Christopher Beland
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: