Quantcast

[JIRA] Created: (JENKINS-9887) "Branches to build" doesn't respect repository name.

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] Created: (JENKINS-9887) "Branches to build" doesn't respect repository name.

JIRA noreply@jenkins-ci.org
"Branches to build" doesn't respect repository name.
----------------------------------------------------

                 Key: JENKINS-9887
                 URL: https://issues.jenkins-ci.org/browse/JENKINS-9887
             Project: Jenkins
          Issue Type: Bug
          Components: git
            Reporter: Tyler Bannister
            Assignee: abayer


I'm using two different repositories so I can isolate coding style, complexity, and other analysis to changed files.  Both repositories contain branches with identical names.  I need to check out only the branch from the first repository and ignore the second repository for analysis and testing purposes.  It only exists so that my build script can generate the list of files that have changed in REPO1/BRANCH_NAME since REPO2/BRANCH_NAME.  However, when I set "Branches to build" to REPO1/BRANCH_NAME it often checks out REPO2/BRANCH_NAME and runs my analysis on that branch instead.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] Commented: (JENKINS-9887) "Branches to build" doesn't respect repository name.

JIRA noreply@jenkins-ci.org

    [ https://issues.jenkins-ci.org/browse/JENKINS-9887?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=154069#comment-154069 ]

Uwe Stuehler commented on JENKINS-9887:
---------------------------------------

Did you try entering refs/remotes/REPO1/BRANCH_NAME in that field?

> "Branches to build" doesn't respect repository name.
> ----------------------------------------------------
>
>                 Key: JENKINS-9887
>                 URL: https://issues.jenkins-ci.org/browse/JENKINS-9887
>             Project: Jenkins
>          Issue Type: Bug
>          Components: git
>            Reporter: Tyler Bannister
>            Assignee: abayer
>
> I'm using two different repositories so I can isolate coding style, complexity, and other analysis to changed files.  Both repositories contain branches with identical names.  I need to check out only the branch from the first repository and ignore the second repository for analysis and testing purposes.  It only exists so that my build script can generate the list of files that have changed in REPO1/BRANCH_NAME since REPO2/BRANCH_NAME.  However, when I set "Branches to build" to REPO1/BRANCH_NAME it often checks out REPO2/BRANCH_NAME and runs my analysis on that branch instead.

--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-9887) "Branches to build" doesn't respect repository name.

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
evernat resolved Bug JENKINS-9887 as Incomplete

No response so closing as incomplete.

Change By: evernat (25/Oct/12 10:34 PM)
Status: Open Resolved
Resolution: Incomplete
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
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

[JIRA] (JENKINS-9887) "Branches to build" doesn't respect repository name.

JIRA noreply@jenkins-ci.org
In reply to this post by JIRA noreply@jenkins-ci.org
 
evernat edited a comment on Bug JENKINS-9887

No response from reporter so closing as incomplete.

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
Loading...