[temurin-compliance] Adjust default group and umask for Temurin compliance users
Summary
We would like to set the default group for TC users on each of the machines to jck
and have the umask as 0002. We are using shared directories now and the automation, and other team members, need to be able to take over other people's work, and clean up at the end of a release cycle.
Steps to reproduce
Most directories under /home/jenkins/jck_run have the SGID bit set on the higher level ones so that gets set correctly, but without the umask they are not group writable unless the user remembers to change it when they log in - it would be preferable to have that as a default.
What is the current bug behavior?
Automation cannot clear up at the end of a release cycle once results are archived
What is the expected correct behavior?
Automation (run as the jenkins user) can clear up. I suspect adding the umask
into /etc/profile
would be a good option.
Relevant logs and/or screenshots
(Add a link to or paste any relevant logs - please use code blocks (```) to format console output, logs, and code, as it's very hard to read otherwise.)
Priority
-
Urgent -
High -
Medium -
Low
Severity
-
Blocker -
Major -
Normal -
Low
Impact
(What is the impact of this issue? Is it blocking a release? Are there any time constraints?, for example: "We have a release tomorrow")
Normal severity as it's not needed for this release but will make life easier.