Stephen A. Imhoff
Stephen A. Imhoff
Separately a "get next version" command would be nice, but I want to enable more than just dealing with that.
I've done that before, yes, but was hoping to avoid rebuilds on a tag/bump-only commit (I've turned off file bumps, and only use SCM integration). I guess there's really two...
@Lee-W - what is it you're waiting for from me? In the absence of python hooks, this feature request was mostly about having a way to run hooks during dry-run.
WAT. That explains my issue.
You don't even have to manually create a logger, it effects any of them injected via DI as well.
Implementation concern: Podman maps in GPUs via a CDI-spec device line: `--device nvidia.com/gpu=gpu0` (the `--gpus` option is ignored). This isn't a device on the host (you can't `stat` it, for...
Another side note: Similar to #132 we likely need a way to make these optional or hard requirements.
How about a list of user groups to add? ```shell { "remoteUser": { ... "groups": ["audio", "video", "plugdev"] } } ```
There's at least one issue [asking them to support it](https://gitlab.com/gitlab-org/gitlab/-/issues/385277), so I don't think they implement the distribution spec. That said, I'm currently not able to publish to a private...
More concretely, what's failing is attempts to get login tokens to check for versions before publish (but after build/test/package). As near as I'm aware, there's no documentation around what's required...