Fix Sudo Log Ownership for non-'jenkins' users 51/66651/4
authorTrevor Bramwell <tbramwell@linuxfoundation.org>
Wed, 27 Jan 2021 22:37:51 +0000 (14:37 -0800)
committerAnil Belur <abelur@linuxfoundation.org>
Thu, 28 Jan 2021 04:26:00 +0000 (14:26 +1000)
commit16ef1e41bfc882abecc24d0c4c3feb54ed664764
treea3c9a62f3b75cc394b2eeef67784c80750239757
parent33873e8144656b47ec5025a1cae2a4878681d036
Fix Sudo Log Ownership for non-'jenkins' users

If builds are run with a user other than 'jenkins', chown'ing of the
sudoers log will fail. Switching the command to use the current
user (and user's default login group) fixes this.

Note: See chown(1) DESCRIPTION for an explanation of using a colon after
the username while omitting the group

Change-Id: Ia9b96e93a250fd22eb36c94471a06c2e211dc9e3
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
releasenotes/notes/sudo-log-owner-03e7cf690e867482.yaml [new file with mode: 0644]
shell/sudo-logs.sh