[JIRA] (JENKINS-61769) git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist

[krishnaprasadp@hotmail.com (JIRA)]

krishna prasad updated an issue

Jenkins / JENKINS-61769 git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist Change By: krishna prasad Summary: git-parameter-plugin in declarative pipeline producing showing origin1 and origin as remote branches but actually did'nt exist Add Comment

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

[krishnaprasadp@hotmail.com (JIRA)]

krishna prasad edited a comment on JENKINS-61769

Re: git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist Hi Boguslaw Kilmas, Yes I am already using use-repository option.   so that it will select appropriate branches before the Jenkins build start . In this case I am confused since origin1 remote branch is not existing in repository as you can see in the above comments . So how this is getting populated in the parameter branch list.

Add Comment

[krishnaprasadp@hotmail.com (JIRA)]

krishna prasad commented on JENKINS-61769

Re: git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist

Hi Boguslaw Klimas, Is it related to plugin issue ? I there any way to debug this.

Add Comment

[krishnaprasadp@hotmail.com (JIRA)]

krishna prasad edited a comment on JENKINS-61769

Re: git-parameter-plugin in declarative pipeline showing origin1 and origin as remote branches but actually did'nt exist

Hi Boguslaw Kilmas [~klimas7] ,

Yes I am already using use-repository option. so that it will select appropriate branches before the Jenkins build start . In this case I am confused since origin1 remote branch is not existing in repository as you can see in the above comments . So how this is getting populated in the parameter branch list.

Add Comment