[JIRA] (JENKINS-58224) Jenkins Job Build, Changes does not show COMMITS from Bitbucket.

0 views
Skip to first unread message

omar.velazquez@softtek.com (JIRA)

unread,
Jun 26, 2019, 4:45:03 PM6/26/19
to jenkinsc...@googlegroups.com
Omar Velazquez created an issue
 
Jenkins / Improvement JENKINS-58224
Jenkins Job Build, Changes does not show COMMITS from Bitbucket.
Issue Type: Improvement Improvement
Assignee: Mark Waite
Attachments: Current.JPG, Original.JPG
Components: git-plugin
Created: 2019-06-26 20:44
Labels: jenkins change
Priority: Minor Minor
Reporter: Omar Velazquez

Our users reports that their jobs are not displaying the commit information into Build page (please see screenshots), they consider that was a really useful behavior in previous Jenkins versions.

Current Jenkins Version: 2.164.2

We really appreciate your help.

Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

mark.earl.waite@gmail.com (JIRA)

unread,
Jun 27, 2019, 12:21:02 AM6/27/19
to jenkinsc...@googlegroups.com
Change By: Mark Waite
Status: Open Fixed but Unreleased
Resolution: Won't Fix

mark.earl.waite@gmail.com (JIRA)

unread,
Jun 27, 2019, 12:21:02 AM6/27/19
to jenkinsc...@googlegroups.com
Mark Waite assigned an issue to Unassigned
Change By: Mark Waite
Assignee: Mark Waite

mark.earl.waite@gmail.com (JIRA)

unread,
Jun 27, 2019, 12:21:02 AM6/27/19
to jenkinsc...@googlegroups.com
Mark Waite commented on Improvement JENKINS-58224
 
Re: Jenkins Job Build, Changes does not show COMMITS from Bitbucket.

That output likely means that you are running a version of command line git which is not supported by the Jenkins git plugin. The git plugin supports command git versions 1.7.10 and later, and full support for all features requires command line git 1.9 or later. Since command line git 1.7 release 9 years ago and 1.9 released 5 years ago, I think it is reasonable to upgrade to a newer version of command line git. Command line git has improved significantly in those many intervening years. You'll benefit significantly by using a newer version.

If you're running CentOS 6 or Red Hat 6, then you will need to install a newer version of command line git in order to see those changes. If you're running CentOS 7 or Red Hat 7, you may also need to install a newer version of command line git. A bug fix for line truncation behavior made the conscious choice to use command line git options which require one of the supported versions of command line git.

mark.earl.waite@gmail.com (JIRA)

unread,
Jun 27, 2019, 12:22:02 AM6/27/19
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Improvement JENKINS-58224
That output likely means that you are running a version of command line git which is not supported by the Jenkins git plugin.  The git plugin supports command git versions 1.7.10 and later, and full support for all features requires command line git 1.9 or later.  Since command line git 1.7 release released 9 years ago and 1.9 released 5 years ago, I think it is reasonable to upgrade to a newer version of command line git.  Command line git has improved significantly in those many intervening years.  You'll benefit significantly by using a newer version.   Look at 1.22.0 for the latest features.

If you're running CentOS 6 or Red Hat 6, then you will need to install a newer version of command line git in order to see those changes.  If you're running CentOS 7 or Red Hat 7, you may also need to install a newer version of command line git.  A bug fix for line truncation behavior made the conscious choice to use command line git options which require one of the supported versions of command line git.

mark.earl.waite@gmail.com (JIRA)

unread,
Jun 27, 2019, 12:22:02 AM6/27/19
to jenkinsc...@googlegroups.com
Mark Waite edited a comment on Improvement JENKINS-58224
That output likely means that you are running a version of command line git which is not supported by the Jenkins git plugin.  The git plugin supports command git versions 1.7.10 and later, and full support for all features requires command line git 1.9 or later.  Since command line git 1.7 released 9 years ago and 1.9 released 5 years ago, I think it is reasonable to upgrade to a newer version of command line git.  Command line git has improved significantly in those many intervening years.  You'll benefit significantly by using a newer version.  Look at 1 2 .22.0 for the latest features.


If you're running CentOS 6 or Red Hat 6, then you will need to install a newer version of command line git in order to see those changes.  If you're running CentOS 7 or Red Hat 7, you may also need to install a newer version of command line git.  A bug fix for line truncation behavior made the conscious choice to use command line git options which require one of the supported versions of command line git.

omar.velazquez@softtek.com (JIRA)

unread,
Jun 27, 2019, 5:59:03 PM6/27/19
to jenkinsc...@googlegroups.com

Fixed, I really appreciate your quick response

Best regards

mark.earl.waite@gmail.com (JIRA)

unread,
Jun 30, 2019, 11:45:03 AM6/30/19
to jenkinsc...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages