You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-dev@hadoop.apache.org by "Anu Engineer (Jira)" <ji...@apache.org> on 2019/11/20 19:13:00 UTC

[jira] [Resolved] (HDDS-2541) CI builds should use merged code state instead of the forked branch

     [ https://issues.apache.org/jira/browse/HDDS-2541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Anu Engineer resolved HDDS-2541.
--------------------------------
    Fix Version/s: 0.5.0
       Resolution: Won't Fix

Closing based on comments in the PR. Please re-open if needed.

> CI builds should use merged code state instead of the forked branch
> -------------------------------------------------------------------
>
>                 Key: HDDS-2541
>                 URL: https://issues.apache.org/jira/browse/HDDS-2541
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>          Components: build
>            Reporter: Marton Elek
>            Assignee: Marton Elek
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 0.5.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> As of now the github actions based CI runs uses the branch of the PR which is the forked repo most of the time.
> It would be better to force a rebase/merge (without push) before the builds to test the possible state after the merge not before.
> For example if a PR branch uses elek/hadoop-ozone:HDDS-1234 and request a merge to apache/hadoop-ozone:master then the build should download the HDDS-1234 from elek/hadoop-ozone AND *rebase/merge* to the apache/hadoop-ozone *before* the build.
> This merge is temporary just for the build/checks (no push at all).



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

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-dev-help@hadoop.apache.org