[
https://issues.apache.org/jira/browse/HIVE-25378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17417547#comment-17417547
]
Zoltan Haindrich commented on HIVE-25378:
-----------------------------------------
the jenkins/githuib plugin has the ability to discover and retire old build
periodically; but the the discover mechanism will re-discover existing PRs if
the content is changed.
currently; we use "merge PR with target branch" strategy; which is good: we
test the PR against the latest available master.
However: in case a new commit lands on the master - with the above strategy
that will mean that we should re-run the tests on all existing branches again.
To avoid re-running the tests on all the PRs periodically - one way this could
be solved is by moving the master/PR merge point from the jenkins plugin into
the job itself; so the system will only discover and check the the PR's commit
hash.
> Enable removal of old builds on hive ci
> ---------------------------------------
>
> Key: HIVE-25378
> URL: https://issues.apache.org/jira/browse/HIVE-25378
> Project: Hive
> Issue Type: Sub-task
> Reporter: Zoltan Haindrich
> Assignee: Zoltan Haindrich
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> We are using the github plugin to run builds on PRs
> However to remove old builds that plugin needs to have periodic branch
> scanning enabled - however since we also use the plugins merge mechanism;
> this will cause to rediscover all open PRs after there is a new commit on the
> target branch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
