• Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Minor Minor
    • git-plugin
    • None

      When using multiple git repositories in a pipeline, the git plugin adds a sumary for each built repository that looks something like

      <git image> Revision: <sha1 of built revision>

      • a branch
      • another branch
        ...
      • another branch

      (Usually only one branch, but some cases show more).

      This summary could benefit from adding the repository URL or a human readable name, so that users can quickly see which revision belongs to what repository. Especially true when there are multiple repositories in a single build.

      Before the change

      Before the change in PR-1067, the UI looked like this:

      After the change

      After the change in PR-1067, the UI now looks like this:

          [JENKINS-38676] git summary should show the repository URL

          Jacob Keller added a comment -

          Note that this has a workaround in that you can set a "Custom SCM Name" extension. This is probably good enough for now, though it's not intuitive that you need to set a "custom" name to have any name at all.

          Jacob Keller added a comment - Note that this has a workaround in that you can set a "Custom SCM Name" extension. This is probably good enough for now, though it's not intuitive that you need to set a "custom" name to have any name at all.

          What if you can add an option (checkbox) to display just repo URL or not?
          Why do I have to enter "special" name to every repository I use?

          Primož Prislan added a comment - What if you can add an option (checkbox) to display just repo URL or not? Why do I have to enter "special" name to every repository I use?

          "Custom SCM Name" is deprecated and is not (no longer?) available in multi-branch pipelines. Especially when also using shared libraries git revision relations become fully unclear. IMHO the information on the build page makes no sense in the current design:

          Christoph Vogtländer added a comment - "Custom SCM Name" is deprecated and is not (no longer?) available in multi-branch pipelines. Especially when also using shared libraries git revision relations become fully unclear. IMHO the information on the build page makes no sense in the current design:

            markewaite Mark Waite
            jekeller Jacob Keller
            Votes:
            2 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: