Re: Automatic batch-mode activation in popular CI environments

2020-07-13 Thread Romain Manni-Bucau
Le lun. 13 juil. 2020 à 21:57, Michael Osipov a écrit : > Am 2020-07-13 um 08:10 schrieb Romain Manni-Bucau: > > Le dim. 12 juil. 2020 à 22:13, Michael Osipov a > > écrit : > > > >> Am 2020-07-12 um 21:35 schrieb Maarten Mulders: > >>> Although no formal standards, many cloud-based CI environmen

Re: Automatic batch-mode activation in popular CI environments

2020-07-13 Thread Michael Osipov
Am 2020-07-13 um 08:10 schrieb Romain Manni-Bucau: Le dim. 12 juil. 2020 à 22:13, Michael Osipov a écrit : Am 2020-07-12 um 21:35 schrieb Maarten Mulders: Although no formal standards, many cloud-based CI environments agreed upon setting CI=true, and I think also Jenkins does that. It might b

Re: Automatic batch-mode activation in popular CI environments

2020-07-12 Thread Romain Manni-Bucau
Le dim. 12 juil. 2020 à 22:13, Michael Osipov a écrit : > Am 2020-07-12 um 21:35 schrieb Maarten Mulders: > > Although no formal standards, many cloud-based CI environments agreed > > upon setting CI=true, and I think also Jenkins does that. It might be a > > relatively simple way to detect most

Re: Automatic batch-mode activation in popular CI environments

2020-07-12 Thread Michael Osipov
Am 2020-07-12 um 21:35 schrieb Maarten Mulders: Although no formal standards, many cloud-based CI environments agreed upon setting CI=true, and I think also Jenkins does that. It might be a relatively simple way to detect most CI environments. The next question is what Maven should do with that

Re: Automatic batch-mode activation in popular CI environments

2020-07-12 Thread Maarten Mulders
Although no formal standards, many cloud-based CI environments agreed upon setting CI=true, and I think also Jenkins does that. It might be a relatively simple way to detect most CI environments. The next question is what Maven should do with that information. I feel like informing the user is mor

Re: Automatic batch-mode activation in popular CI environments

2020-07-12 Thread Martin Kanters
Thanks for all the replies! I agree that checking on environment variables is not desirable (because of the many different CI environments and also because the envs are not necessarily unique to the CI environment only). Using some kind of mechanism Michael is proposing seems a lot more generic a

Re: Automatic batch-mode activation in popular CI environments

2020-07-12 Thread Romain Manni-Bucau
Hi, Did you already do the work to list what it implies? For instance I know interactive mode can be needed on these platforms (for debug purposes mainly), that travis requires more work for logs (size + timeout "ping" log to not have the job killed) etc... So wonder what is the overlap (if it is

Re: Automatic batch-mode activation in popular CI environments

2020-07-12 Thread Michael Osipov
Am 2020-07-12 um 17:42 schrieb Martin Kanters: Hi all, When setting up GitHub Actions for Maven (core) two weeks ago, I initially forgot to enable the -B/--batch-mode flag. While this gave no issues and was easy to fix, it could be avoided by detecting if Maven is executed on popular CI environm

Re: Automatic batch-mode activation in popular CI environments

2020-07-12 Thread Gary Gregory
Don't forget Travis-CI. Gary On Sun, Jul 12, 2020, 11:42 Martin Kanters wrote: > Hi all, > > When setting up GitHub Actions for Maven (core) two weeks ago, I initially > forgot to enable the -B/--batch-mode flag. > While this gave no issues and was easy to fix, it could be avoided by > detectin

Re: Automatic batch-mode activation in popular CI environments

2020-07-12 Thread Tibor Digana
It is better if you control the Maven and not when the Maven controls you 😁 Dňa ne 12. 7. 2020, 17:42 Martin Kanters napísal(a): > Hi all, > > When setting up GitHub Actions for Maven (core) two weeks ago, I initially > forgot to enable the -B/--batch-mode flag. > While this gave no issues and

Automatic batch-mode activation in popular CI environments

2020-07-12 Thread Martin Kanters
Hi all, When setting up GitHub Actions for Maven (core) two weeks ago, I initially forgot to enable the -B/--batch-mode flag. While this gave no issues and was easy to fix, it could be avoided by detecting if Maven is executed on popular CI environments and in that case automatically enabling batc