The git plugin stopped trying to support versions older than 1.8.3 several
years ago. Once Centos 7 goes off support, the plugin will probably stop
trying to support versions older than 2.11
On Sat, May 1, 2021, 2:08 AM Sverre Moe wrote:
> I found out the reason for it.
> As we build on
Or enable JGit and use it. JGit does not have all the features of CLI git
and it does best with repos that are 50 MB or less.
On Sat, May 1, 2021, 2:08 AM Sverre Moe wrote:
> I found out the reason for it.
> As we build on different Linux distributions, we also are subject to
> different
I found out the reason for it.
As we build on different Linux distributions, we also are subject to
different versions of git installed.
The no branch was given on a Linux build agent with git-1.7 (yes a very old
Linux distribution, SLES 11).
Perhaps a solution here would be to use the Jenkins
BRANCH1
+ git branch
* (no branch)
BRANCH2
+ git branch
* (HEAD detached at 5abd860)
The same project, but one branch does not return any branches on `git
branch`.
Any clue as to why?
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To
