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

Log git version before cloning via CLI

    Details

    • Similar Issues:
    • Released As:
      git client plugin 3.3.2

      Description

      It would be helpful for debugging/troubleshooting purposes if the Git plugin logged the version of git being used (i.e., the output of git --version) to the console before starting the cloning process. Additionally, if the version of git being used is not supported by the plugin, a warning should be logged to the console.

      One practical application of this would be a situation like JENKINS-62534. We were not aware that our Jenkins master agent was still running git 1.8.

      Possible Solution (modeled after GitHub Webhooks Warning)

      When alerts are needed for unexpected global conditions in the git plugin, it could be done through a similar user interface technique as is used by GitHub webhooks. A number appears in the top right of the Jenkins interface. When that number is clicked, a dialog appears that includes a "View" button that would open a page that lists all the problems of that type. The "Dismiss" button would clear the contents of the page that lists all the problems of that type.

        Attachments

          Issue Links

            Activity

            Hide
            markewaite Mark Waite added a comment - - edited

            This is another good place to apply the alert system that Jenkins uses for global warnings. See JENKINS-62583 for a description of other cases where the Jenkins administrator would benefit by having a "monitor" (alert) appear when an unexpected condition is detected.

            In this example, the unexpected conditions might include:

            • Command line git older than 2.7 on an agent
            • Command line git older than 2.15 with git lfs installed (see JENKINS-59139)

            Each of them should allow a warning per agent that the administrator may choose to ignore or completely disable the check.

            Show
            markewaite Mark Waite added a comment - - edited This is another good place to apply the alert system that Jenkins uses for global warnings. See JENKINS-62583 for a description of other cases where the Jenkins administrator would benefit by having a "monitor" (alert) appear when an unexpected condition is detected. In this example, the unexpected conditions might include: Command line git older than 2.7 on an agent Command line git older than 2.15 with git lfs installed (see JENKINS-59139 ) Each of them should allow a warning per agent that the administrator may choose to ignore or completely disable the check.
            Hide
            markewaite Mark Waite added a comment -

            Released as git client plugin 3.3.2 July 30, 2020

            Show
            markewaite Mark Waite added a comment - Released as git client plugin 3.3.2 July 30, 2020

              People

              • Assignee:
                Unassigned
                Reporter:
                rittneje Jesse Rittner
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: