[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

JIRA noreply@jenkins-ci.org
Issue Type: Bug Bug
Assignee: Nicolas De Loof
Attachments: multi-git.png
Components: git
Created: 12/Mar/14 8:55 AM
Description:

I want to specify remote repository's branch when I set multi remote repository in a git repository like attachment image.
But Jenkins Git plugin always checkout latest commit when it set multi remote repository.

Environment: Windows Server 2008
Project: Jenkins
Priority: Major Major
Reporter: kompiro
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

JIRA noreply@jenkins-ci.org
Mark Waite commented on Bug JENKINS-22144

Alexander Link just added some improved help for the branch selection field. That may help you see how you need to specify the branch name in order to achieve the result you want.

Refer to https://github.com/jenkinsci/git-plugin/commit/48583bf82e8f563cd5368e1567b11e4190959eae for the details. I believe the key change needed for that improvement is included in git-client-plugin 1.6.4, and is not available in git-client-plugin versions prior to 1.6.4.

The behavior you observe (aaa/master is not treated any differently than origin/master) is an expected behavior that we didn't want to change, lest it break compatibility with existing user jobs. Alexander added the ability to provide a more precise specification of the branch name, while still retaining the older behavior for simpler branch names.

Can you review his comments and try them with git-client-plugin 1.6.4 to see if they resolve your issue?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
kompiro commented on Bug JENKINS-22144

Thanks your comment.

I added "remotes/" to "Branch Specifier" like "remotes/aaa/master", Git Plugin 2.0.4 couldn't verify the format.
I updated Git Plugin to 2.0.5-SNAPSHOT and git-client-plugin 1.6.5-SNAPSHOT,
the plugin could verify the format. But it couldn't checkout the specified remote branch.

Does Jenkins Git plugin team work in progress about this feature?

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Mark Waite commented on Bug JENKINS-22144

kompiro yes, there is a pending commit to complete the work. I had missed there another commit was needed, but the author of the commit detected the gap and has submitted a proposed change.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Mark Waite commented on Bug JENKINS-22144

kompiro yes, there is a pending commit to complete the work. I had missed there another commit was needed, but the author of the commit detected the gap and has submitted a proposed change.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Mark Waite commented on Bug JENKINS-22144

The change is now available as part of git-client-plugin 1.7.0 and git-plugin 2.1.0. Could you try them now to see if they better meet your needs? The help is now available for the "Branch Specifier" field, and hopefully that will clarify the forms which are allowed and how they are interpreted.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

[JIRA] [git] (JENKINS-22144) Can't specify remote repository's branch to build

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
Mark Waite commented on Bug JENKINS-22144

I've attempted an experiment or two and was not successful trying to checkout a branch from a second repository with the syntax "refs/remotes/somename/somebranch". More investigation is needed.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
For more options, visit https://groups.google.com/d/optout.