Hi Paul, Paul Gevers, on 2025-11-07: > I recently learned that a lot of CI frameworks set the environmental > variable CI. Unfortunately for this bug report autopkgtest nor debci doesn't > do that, maybe either of them should. In the absence of a common variable, I > think this isn't unreasonable, and (minus the variable name) could even be > suggested upstream. Thinking a tiny bit further, if you want to propose this > upstream, you could use a more generic variable like CI and set the variable > in d/t/control or in the script you run to call the tests.
Thank you, this looks interesting, it's the first time I hear of the CI environment variable, but I vaguely recall of common variables conventions that were in use at least by Perl modules automation for autopkgtest[1]: >> The environment variables AUTOMATED_TESTING and >> NONINTERACTIVE_TESTING are set to 1 by default. AUTOMATED_TESTING feels both common and generic enough that I'd feel comfortable forwarding the change upstream, independently of the language. [1]: https://perl-team.pages.debian.net/autopkgtest.html#smoke Have a nice day, :) -- .''`. Étienne Mollier <[email protected]> : :' : pgp: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da `. `' sent from /dev/pts/1, please excuse my verbosity `- on air: Colin Tench Project - Something Old, Something…
signature.asc
Description: PGP signature
