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

Improve Console Output page

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Open (View Workflow)
    • Priority: Trivial
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Similar Issues:

      Description

      Many times I'm scrolling through a large page 4-5 screens long to see what happened in build and find the failure reason.

      We can group those messages according to step executed and also somehow collapse or extend them. This steps can me grouped based on the configuration steps inside the job or give the ability to the plugins how to group their output. Also at the end when we chain jobs and lunch another one we can have some info of what values, variables or Artifacts are passed.

        Attachments

          Activity

          Hide
          danielbeck Daniel Beck added a comment -

          I wonder whether this can't just be done in a plugin to begin with. The necessary extension points should exist. There are also plugins (Collapsing Console Sections Plugin) that support doing this manually.

          Show
          danielbeck Daniel Beck added a comment - I wonder whether this can't just be done in a plugin to begin with. The necessary extension points should exist. There are also plugins (Collapsing Console Sections Plugin) that support doing this manually.
          Hide
          pkleanthous Pavlos Kleanthous added a comment -

          Yes this can be made through a plugin.
          I was wondering if we can use the same methods as we will use to configure jenkins jobs. (As demonstrated in Jenkins 2.0)

          Show
          pkleanthous Pavlos Kleanthous added a comment - Yes this can be made through a plugin. I was wondering if we can use the same methods as we will use to configure jenkins jobs. (As demonstrated in Jenkins 2.0)
          Hide
          danielbeck Daniel Beck added a comment -

          Pavlos Kleanthous Could you please be more specific as to what same methods you're referring to?

          Show
          danielbeck Daniel Beck added a comment - Pavlos Kleanthous Could you please be more specific as to what same methods you're referring to?
          Hide
          pkleanthous Pavlos Kleanthous added a comment -

          Daniel Beck as the configuration menus are going to become collapsible and those are sequence steps that Jenkins execute the job. Somehow (I don't know exactly) the same will happen at the console output, as you know where a step starts and where it finishes.

          Show
          pkleanthous Pavlos Kleanthous added a comment - Daniel Beck as the configuration menus are going to become collapsible and those are sequence steps that Jenkins execute the job. Somehow (I don't know exactly) the same will happen at the console output, as you know where a step starts and where it finishes.
          Hide
          vsiakka Vasiliki Siakka added a comment - - edited

          I am also very interested in being able to configure collapsing log sections on a job bases with job dsl. I haven't tried the collapsing sections plugin, but from its description it sounds like the configuration affects the whole Jenkins instance and you need to be an admin, which is not ideal for an org where different teams/users share a jenkins instance.
          It would be great if this could not only be configured with an expression for start and end, but also on a step bases, or in pipeline with a block syntax (eg similar to how you define stages).

          Edit: actually i think this is a dupe of JENKINS-27394 whose fix is in review

          Show
          vsiakka Vasiliki Siakka added a comment - - edited I am also very interested in being able to configure collapsing log sections on a job bases with job dsl. I haven't tried the collapsing sections plugin, but from its description it sounds like the configuration affects the whole Jenkins instance and you need to be an admin, which is not ideal for an org where different teams/users share a jenkins instance. It would be great if this could not only be configured with an expression for start and end, but also on a step bases, or in pipeline with a block syntax (eg similar to how you define stages). Edit: actually i think this is a dupe of  JENKINS-27394 whose fix is in review

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            pkleanthous Pavlos Kleanthous
            Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated: