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

GUI for Maven builds can be confusing

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: In Progress (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: maven-plugin
    • Labels:
      None
    • Environment:
      Platform: All, OS: All
    • Similar Issues:

      Description

      I've been evaluating Hudson, and it looks great! There was just one area that
      left me quite bewildered until I worked out what was going on, so I thought I
      would propose some minor GUI changes that might make things a little clearer.

      First, I added a new job to build a simple single-module Maven 2 project. I then
      built the project, and had to play about with the goals that were being
      executed. I changed the goals, then found they didn't build as expected. I went
      back to the configuration, and it appeared to have lost my changes. And I got
      confused by the fact that sometimes when I went into the configuration, some of
      the options seemed to be missing.

      OK, I finally worked out that when you add a Maven project, it creates a
      top-level job to build the project as a whole, then a sub-entry to build each
      module. You can specify a different goal when executing the project as a whole
      and when executing an individual module, if I understand correctly.

      In hindsight this is reasonably obvious, but I hadn't noticed the different
      levels in the breadcrumb, and it did confuse me for a while. I would suggest the
      following the changes to the GUI:

      • For single module Maven projects, do not create sub-entries if there is only
        one module
      • If there are sub-entries for each module, clearly label them. For example, at
        the moment both would be labeled as "Project MyProject", instead of "Project
        MyProject" and "Module MyProject::MyProject" or something similar. You could
        take this further and clearly label each of the actions/configuration pages
        (e.g. "Project Configuration" vs. "Module Configuration".

      I hope you find these suggestions constructive..!

      Thanks, Alex.

        Attachments

          Activity

          alexmcmanus alexmcmanus created issue -
          Hide
          kohsuke Kohsuke Kawaguchi added a comment -

          I fully agree that there are a lot of UI problems in the native Maven support.

          > - If there are sub-entries for each module, clearly label them

          This part is done for 1.104.

          > - For single module Maven projects, do not create sub-entries if there is only
          one module

          This is clearly desirable, so hopefull we'll get to it later.

          Show
          kohsuke Kohsuke Kawaguchi added a comment - I fully agree that there are a lot of UI problems in the native Maven support. > - If there are sub-entries for each module, clearly label them This part is done for 1.104. > - For single module Maven projects, do not create sub-entries if there is only one module This is clearly desirable, so hopefull we'll get to it later.
          kohsuke Kohsuke Kawaguchi made changes -
          Field Original Value New Value
          Status Open [ 1 ] In Progress [ 3 ]
          ircbot Jenkins IRC Bot made changes -
          Component/s maven-plugin [ 16033 ]
          Component/s maven2 [ 15487 ]
          rtyler R. Tyler Croy made changes -
          Workflow JNJira [ 130575 ] JNJira + In-Review [ 185290 ]

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            alexmcmanus alexmcmanus
            Votes:
            2 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated: