Page MenuHomeSoftware Heritage

Use `branch` instead of `clone`
ClosedPublic

Authored by Alphare on Feb 9 2022, 2:54 PM.

Details

Summary

clone was introduced with Breezy 3.1.0. For our purposes, branch
will do just fine since we don't want to get colocated branches (but
only one branch per origin) and we can get the same "no tree" behavior
with a simple flag.

Diff Detail

Repository
rDLDBZR BZR loader
Branch
clone
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 26700
Build 41754: Phabricator diff pipeline on jenkinsJenkins console · Jenkins
Build 41753: arc lint + arc unit

Event Timeline

Build has FAILED

Patch application report for D7133 (id=25854)

Rebasing onto 078fb50296...

Current branch diff-target is up to date.
Changes applied before test
commit 5741ffd12c7830684303eb75d8d1176fea67e7ff
Author: Raphaël Gomès <rgomes@octobus.net>
Date:   Wed Feb 9 14:51:05 2022 +0100

    Use `branch` instead of `clone`
    
    `clone` was introduced with Breezy 3.1.0. For our purposes, `branch`
    will do just fine since we don't want to get colocated branches (but
    only one branch per origin) and we can get the same "no tree" behavior
    with a simple flag.

Link to build: https://jenkins.softwareheritage.org/job/DLDBZR/job/tests-on-diff/32/
See console output for more information: https://jenkins.softwareheritage.org/job/DLDBZR/job/tests-on-diff/32/console

Harbormaster returned this revision to the author for changes because remote builds failed.Feb 9 2022, 2:58 PM
Harbormaster failed remote builds in B26696: Diff 25854!

Build is green

Patch application report for D7133 (id=25858)

Rebasing onto 078fb50296...

Current branch diff-target is up to date.
Changes applied before test
commit 080db96f11900080399ec423d1b12b524b86c480
Author: Raphaël Gomès <rgomes@octobus.net>
Date:   Wed Feb 9 14:51:05 2022 +0100

    Use `branch` instead of `clone`
    
    `clone` was introduced with Breezy 3.1.0. For our purposes, `branch`
    will do just fine since we don't want to get colocated branches (but
    only one branch per origin). We can get the same "no tree" and directory
    reuse behaviors with a simple flag.

See https://jenkins.softwareheritage.org/job/DLDBZR/job/tests-on-diff/33/ for more details.

This revision is now accepted and ready to land.Feb 9 2022, 3:22 PM
This revision was automatically updated to reflect the committed changes.