geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (Jira)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-7281) Ensure that UpdatePassingTokens only moves forward in Git
Date Tue, 22 Oct 2019 23:14:00 GMT

    [ https://issues.apache.org/jira/browse/GEODE-7281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16957403#comment-16957403
] 

ASF subversion and git services commented on GEODE-7281:
--------------------------------------------------------

Commit addaebcb799b926a2a088202ad07a74367095453 in geode's branch refs/heads/feature/GEODE-7258
from Robert Houghton
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=addaebc ]

GEODE-7281: UpdatePassingTokens only moves git sha forward. (#4134)

* GEODE-7281: UpdatePassingTokens only moves git sha forward.

Use `git merge-base --is-ancestor <old> <new>` to check that the SHA we
publish as 'passing' is moving forward in git history.

* force git behavior in attach-sha-to-branch


> Ensure that UpdatePassingTokens only moves forward in Git
> ---------------------------------------------------------
>
>                 Key: GEODE-7281
>                 URL: https://issues.apache.org/jira/browse/GEODE-7281
>             Project: Geode
>          Issue Type: Task
>          Components: ci
>            Reporter: Robert Houghton
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> During concourse migration, or during a fan-in from parallel tasks, it may happen that
Geode SHAs get through the pipeline out-of-order. Ensure that we do not 'move backwards' in
git history when this occurs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message