[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches

[krishnaprasadp@hotmail.com (JIRA)]

krishna prasad created an issue

Jenkins / JENKINS-61769 git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches Issue Type: Bug Assignee: Boguslaw Klimas Attachments: image-2020-04-01-21-41-34-429.png Components: git-parameter-plugin Created: 2020-04-01 16:12 Priority: Minor Reporter: krishna prasad I have configured Jenkins git parameter plugin for selecting appropriate branches before building a job. I am using two repositories for building a single job. For one of the repositories its showing two remote sever as origin and origin1 but actually it has only one it is origin. I have checked the repository and given the result as below   $ git ls-remote --heads origin d8c63b4c1f1a87cba2b5065d3c2018193079fb80        refs/heads/XXXX 3b390cec5ede9ec4dede3b83dc8d05969a286b70        refs/heads/XXXX ea0908b790a8491584bfe0f7e7ba459ee6307cb0        refs/heads/XXXX a1225d5a8f1a24ef4c65384b6833224358d30587        refs/heads/XXXX 74977aed5ed375d2afae0e35d3ec73fa214e63e1        refs/heads/XXXX 9e3e0fa0c93829b9dbb945f3d7788e77462f15c9        refs/heads/feature/scenario ff9af7bcd7d6c06cbb573656cf73abe2c0b26538        refs/heads/master   $ git ls-remote From https://github.developer.allianz.io/cta-crui/crui-data-model.git ff9af7bcd7d6c06cbb573656cf73abe2c0b26538        HEAD d8c63b4c1f1a87cba2b5065d3c2018193079fb80        refs/heads/XXXX 3b390cec5ede9ec4dede3b83dc8d05969a286b70        refs/heads/XXXX ea0908b790a8491584bfe0f7e7ba459ee6307cb0        refs/heads/XXXX a1225d5a8f1a24ef4c65384b6833224358d30587        refs/heads/XXXX 74977aed5ed375d2afae0e35d3ec73fa214e63e1        refs/heads/XXXX 9e3e0fa0c93829b9dbb945f3d7788e77462f15c9        refs/heads/feature/scenario ff9af7bcd7d6c06cbb573656cf73abe2c0b26538        refs/heads/master 7d3177956309ea27d828ea8e879084ee2c1a5344        refs/pull/1/head 27a27fe3d82c0fd867a54716b693e7173968b05b        refs/pull/2/head 9e3e0fa0c93829b9dbb945f3d7788e77462f15c9        refs/pull/3/head d8c63b4c1f1a87cba2b5065d3c2018193079fb80        refs/pull/4/head 3b390cec5ede9ec4dede3b83dc8d05969a286b70        refs/pull/5/head a1225d5a8f1a24ef4c65384b6833224358d30587        refs/pull/6/head 74977aed5ed375d2afae0e35d3ec73fa214e63e1        refs/pull/7/head 9564fdb879cc3b3ff15d66baf4d9a0cfafcda120        refs/pull/7/merge ff9af7bcd7d6c06cbb573656cf73abe2c0b26538        refs/tags/v0.1     But in jenkins job it showing like this     You can see both origin1 and origin are showing . Please provide us support regarding this issue    Add Comment

This message was sent by Atlassian Jira (v7.13.12#713012-sha1:6e07c38)

[klimas7@gmail.com (JIRA)]

Boguslaw Klimas commented on JENKINS-61769

Re: git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches Hi, Are you try used 'use-repository' option? https://github.com/jenkinsci/git-parameter-plugin#use-repository

Add Comment

[krishnaprasadp@hotmail.com (JIRA)]

krishna prasad commented on JENKINS-61769

Re: git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches

Hi Boguslaw Kilmas, Yes I am already using use-repository option.

Add Comment

[krishnaprasadp@hotmail.com (JIRA)]

krishna prasad updated an issue

Jenkins / JENKINS-61769

git-parameter-plugin in declarative pipeline producing origin1 and origin as remote branches

Change By: krishna prasad Priority: Minor Major

Add Comment