Details

    • Type: Improvement
    • Status: Reopened
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: core
    • Labels:
      None
    • Environment:
      Platform: All, OS: All

      Description

      users without config privileges should be able to discover where the code for a
      job is being pulled from. Currently you cannot discover this unless the admin
      puts it in the comment field, which is duplication of data - and thus ugly.

        Activity

        Hide
        mdonohue mdonohue added a comment -

        can be resolved by looking at the config screen - see issue 3677

            • This issue has been marked as a duplicate of 3677 ***
        Show
        mdonohue mdonohue added a comment - can be resolved by looking at the config screen - see issue 3677 This issue has been marked as a duplicate of 3677 ***
        Hide
        lifeless lifeless added a comment -

        My point was that there should be a nice UI without dgging into the config, not
        that the config needed to be opened.

        Show
        lifeless lifeless added a comment - My point was that there should be a nice UI without dgging into the config, not that the config needed to be opened.
        Hide
        mdonohue mdonohue added a comment -

        It's not clear what you want then. JENKINS-3677 solves this nicely - it lets users see how the job is configured. Not only the SCM configuration, but the build steps as well.

        Show
        mdonohue mdonohue added a comment - It's not clear what you want then. JENKINS-3677 solves this nicely - it lets users see how the job is configured. Not only the SCM configuration, but the build steps as well.

          People

          • Assignee:
            Unassigned
            Reporter:
            lifeless lifeless
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: