Dear Debian gurus,
Lazy me would love to get automation going akin to the one in
conda-forge (see e.g. [1]) -- whenever a new upstream is released
(as could be detected with a run of uscan) the CI would
- would run uscan
- get new source {tarball}
- get new {uversion} (from uscan output/tarball)
- would run
gbp import-orig -- --pristine-tar --debian-branch=new-{uversion}/$(gbp config buildpackage.debian-branch) ...
i.e. import sources and prepare all 3 branches with dedicated prefix
new-{uversion}/
- might do some other automated/decided upon actions such as e.g.
"drop all debian/patches/00*" which were cherry-picked from upstream,
and were applied etc.
- push those branches into salsa repo and submit a merge request
against the debian-branch (while providing URLs for other two
branches).
- employ salsa-ci-team/pipeline (or alike) to build package from
those 3 branches
- maintainer then reviews/tunes up the MR and if merges, CI would
merge/push all the new-{uversion}/ branches into corresponding
one and delete them from CI.
If MR is closed, CI would just remove all those new-{uversion}
branches.
Is there any package/tool which already does something like that on CI?
Or may be you see some issues with such a procedure?
Thanks in advance!
[1] https://github.com/conda-forge/datalad-feedstock/pull/95
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
WWW: http://www.linkedin.com/in/yarik
Attachment:
signature.asc
Description: PGP signature