[
https://issues.apache.org/jira/browse/YETUS-168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17206619#comment-17206619
]
Allen Wittenauer commented on YETUS-168:
----------------------------------------
After debugging YETUS-966, I'm very skeptical that this can actually be done.
Two reasons:
* need to update two branches instead of just one.
* since this was filed, support for robots has shown that different systems
leave the tree in different states
I'm tempted to close this as Won't Fix. While it could be argued that it is
expensive network-wise, there are likely bigger things in modern times that
need to get optimized first.
> update test-patch to do a single git fetch and a single rebase the test branch
> ------------------------------------------------------------------------------
>
> Key: YETUS-168
> URL: https://issues.apache.org/jira/browse/YETUS-168
> Project: Yetus
> Issue Type: Improvement
> Components: Precommit
> Reporter: Sean Busbey
> Priority: Minor
> Labels: beginner
>
> Right now getting to the current branch for testing involves
> * force checkout to default
> * pull --rebase to get updated remote refs as a side effect
> * changing to test branch
> * final pull --rebase to to move the test branch to the remote head
> simplify / clean things up to use a fetch to grab all refs and then do a
> rebase once we know what branch we're supposed to be on.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
