This was finally solved by doing* unshallow clone* of git repositories.
*Configure Multibranch Pipeline Job > Branch Sources > Behaviours > Add
> Advanced clone behaviours > uncheck shallow clone *
[image: image.png]
Thank you everyone for the help.
On Tue, Feb 16, 2021 at 2:26 AM Mark Waite
wro
The multibranch pipeline implementation on one or more of the branch
providers intentionally narrows the refspec of the repository while cloning
it into the workspace. The narrowed refspec usually includes only a single
branch so that git does not waste effort retrieving changes that are not
relat
Check if you have set git references on the job, IIRC the git plugin always
make a `git fetch —all`
El lunes, 15 de febrero de 2021 a las 10:49:21 UTC+1, Rishi Gautam escribió:
> anyone has any idea please
>
> On Wed, Feb 10, 2021 at 4:16 PM Gautam, Rishi
> wrote:
>
>> I was trying to carry ou
Am Mittwoch, den 10.02.2021, 16:16 +0545 schrieb Gautam, Rishi:
> I was trying to carry out git operations on any other branch than the
> PR source/destination branch in a jenkins multibranch pipeline.When I
> scanned the branches inside the PR build job, I didn't see any other
> branches. I only
anyone has any idea please
On Wed, Feb 10, 2021 at 4:16 PM Gautam, Rishi
wrote:
> I was trying to carry out git operations on *any other branch *than the
> PR source/destination branch in a jenkins multibranch pipeline.
> When I scanned the branches inside the PR build job, I didn't see any
> ot
I was trying to carry out git operations on *any other branch *than the PR
source/destination branch in a jenkins multibranch pipeline.
When I scanned the branches inside the PR build job, I didn't see any other
branches. I only got below branches on* git branch -a *command on pipeline:
* PR-2
r
