launchpad-reviewers team mailing list archive
-
launchpad-reviewers team
-
Mailing list archive
-
Message #27833
Re: [Merge] ~cjwatson/lpcraft:run-one into lpcraft:main
The selector approach was my first thought too, but after some experimentation I concluded that it couldn't work because you could equally well have something like this:
pipeline: [test]
jobs:
test:
matrix:
- environment:
PYTHON: python3.8
- environment:
PYTHON: python3.9
series: focal
architectures: amd64
run: tox
Not only do these have identical series and architectures, but also I don't really fancy having to encode complex structures onto the command line just in order to select a job.
The only other option I can think of would be to require that the config file author explicitly sets some kind of unique identifier for every (expanded) job, but I shied away from that because it seems like it could easily end up being annoying for config file authors.
--
https://code.launchpad.net/~cjwatson/lpcraft/+git/lpcraft/+merge/413081
Your team Launchpad code reviewers is requested to review the proposed merge of ~cjwatson/lpcraft:run-one into lpcraft:main.
References