*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
when jenkins is installed, and a long-running jenkins-job is running,
apt-get install jenkins
This causes jenkins to abort currently running jobs and re-start.
Jenkins has an option to re-start as soon as it is idle. Using that
during upgrades would lead to less-intrusive update behavior.
* What outcome did you expect instead?
I expect system upgrades to not interfere with user processes.
Unfortunately at this time, upgrading jenkins cancels currently
running jenkins jobs when jenkins is re-started immediately.
*** End of the template - remove these template lines ***
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.14.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF-8), LANGUAGE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled