Page MenuHomeSoftware Heritage

Replace vcversioner with setuptools-scm
ClosedPublic

Authored by olasd on Jun 9 2020, 5:27 PM.

Details

Test Plan

tox should report a relevant version number, even when running on
this diff

Diff Detail

Repository
rDSCH Scheduling utilities
Branch
master
Lint
No Linters Available
Unit
No Unit Test Coverage
Build Status
Buildable 12726
Build 19354: Phabricator diff pipeline on jenkinsJenkins console · Jenkins
Build 19353: arc lint + arc unit

Event Timeline

Build is green

Patch application report for D3250 (id=11522)

Rebasing onto 14cd5bb5ad...

Current branch diff-target is up to date.
Changes applied before test
commit 28c5b8d479c22f93bfc87f0713a4090e77434a0b
Author: Nicolas Dandrimont <nicolas@dandrimont.eu>
Date:   Tue Jun 9 15:47:26 2020 +0200

    Replace vcversioner with setuptools-scm

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

And indeed, from the jenkins console log:

swh.scheduler @ file:///var/lib/jenkins/workspace/DSCH/tests-on-diff/.tox/.tmp/package/1/swh.scheduler-0.1.2.dev3%2Bg28c5b8d.zip

ardumont added a subscriber: ardumont.

Nice.

Thanks.

What does it imply for the debian packaging work (just a change in dependency from python3-vcversioner to python3-setuptools-scm)?

This revision is now accepted and ready to land.Jun 9 2020, 5:32 PM
This revision was automatically updated to reflect the committed changes.

What does it imply for the debian packaging work (just a change in dependency from python3-vcversioner to python3-setuptools-scm)?

Yes. I've done so as well.