[
https://issues.apache.org/jira/browse/HBASE-13081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329826#comment-14329826
]
Enis Soztutar commented on HBASE-13081:
---------------------------------------
bq. IMHO we should always be checking the "wipe the workspace" option on every
ASF job configuration
I thought we were doing that already. That is why the test-patch.sh code does
not do {{git pull}}, but just checks out a branch. Jenkins first finds the git
revision, then checks out that revision without bothering with branches at all.
Let me see whether we can do it that way.
> Branch precommit builds are not updating to branch head before patch
> application
> --------------------------------------------------------------------------------
>
> Key: HBASE-13081
> URL: https://issues.apache.org/jira/browse/HBASE-13081
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Enis Soztutar
>
> See for example
> https://builds.apache.org/job/PreCommit-HBASE-Build/12922//console
> {noformat}
> git checkout 0.98
> Previous HEAD position was 03d8918... HBASE-13069 Thrift Http Server returns
> an error code of 500 instead of 401 when authentication fails (Srikanth
> Srungarapu)
> Switched to branch '0.98'
> Your branch is behind 'origin/0.98' by 48 commits, and can be fast-forwarded.
> (use "git pull" to update your local branch)
> git status
> On branch 0.98
> Your branch is behind 'origin/0.98' by 48 commits, and can be fast-forwarded.
> (use "git pull" to update your local branch)
> Untracked files:
> (use "git add <file>..." to include in what will be committed)
> patchprocess/
> nothing added to commit but untracked files present (use "git add" to track)
> {noformat}
> Because the local tree is 48 commits behind the head of the 0.98 branch, the
> contributor's patch based on the head of 0.98 branch cannot cleanly apply.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
